-
-
Notifications
You must be signed in to change notification settings - Fork 52
Add initial ADOPTERS.md file #477
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 2 commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,37 @@ | ||
# Adopters | ||
|
||
**📢 If you're using JSON Schema in your organization, please add your company name to this list.** | ||
**🙏 It really helps the project to gain momentum and credibility. It's a small contribution back to the project with a big impact.** | ||
|
||
Why add your company name? | ||
|
||
- Demonstrates the real-world usage of JSON Schema. | ||
- Provides visibility to organizations that have successfully adopted JSON Schema. | ||
- Encourages other organizations to adopt JSON Schema. | ||
- Builds trust in the JSON Schema ecosystem. | ||
|
||
This document also lists the organizations that use JSON Schema based on public information available in blog posts, events, and videos. If any organization would like to be added or get removed please make a Pull Request. | ||
|
||
Guidelines: | ||
- Please don't include your organization's logo or other trademarked material | ||
- Add a reference (link to a public blog post, video, slides, etc) mentioning that JSON Schema is used | ||
- Please include a contact link for maintainers | ||
|
||
Looking for extra credit? We also do [case studies](https://github.com/orgs/json-schema-org/projects/8/views/2) and accept sponsorship via [Open Collective](https://opencollective.com/json-schema). | ||
<details> | ||
<summary>Find out more about case studies</summary> | ||
If your company would like to share more about what you're doing in public, there's a good chance we'd love to collaborate on a case study. | ||
|
||
Please reach out to us via [our Slack](https://json-schema.org/slack) or creating a new Issue in this repo. | ||
|
||
From exerience, these case studies can take some time to develop, write, get approved, and published. It's best if you can find out for sure if you can publish a case study with us as early as possible. If you're at a big organization, you'll likely have to get approval from people who have no idea what you're talking about. Here's some context you can share with them. | ||
|
||
JSON Schema is an [OpenJS Foundation](https://openjsf.org/about) Project, under [The Linux Foundation](https://www.linuxfoundation.org/). Both the OpenJS Foundation and The Linux Foundation are registered non-profit organizations (501(c)(6)). | ||
|
||
By supporting JSON Schema with a case study, you are documenting its success and your smarts in picking it as a solution. You'll join the ranks of organizations like GitHub, Postman, Microsoft, and Zapier. JSON Schema case studies help justify the ongoing financial support required to mature, develop, and support the JSON Schema ecosystem. Case studies also demonstrate the strength of the JSON Schema ecosystem in production today. The next case study could be you. | ||
Relequestual marked this conversation as resolved.
Show resolved
Hide resolved
|
||
</details> | ||
|
||
| Organization | Contact | Description of Use / Reference | | ||
| --- | --- | --- | | ||
| GitHub | [Rachael Sewell](https://github.com/rachmari)<br/>[Robert Sese](https://github.com/rsese) | Github JSON Schema case study - [Validating documentation at GitHub](https://json-schema.org/blog/posts/github-case-study) | | ||
Relequestual marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
Relequestual marked this conversation as resolved.
Show resolved
Hide resolved
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it'd be slightly prettier to link to the subset of the blog rather than a project board (i.e. published ones rather than project management).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I totally agree... but currently there's no such link or filter 😅
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh bizarre. As in the next.js thing takes post types (which I know we set to Case Study) but does nothing with that (i.e. doesn't generate pages per-type??) Whatever I won't think too hard, I know this is changing soon.