|
| 1 | +[ |
| 2 | + { |
| 3 | + "title": "How JSON Schema Was an Obvious Choice at GitHub", |
| 4 | + "summary": "At GitHub's Docs Engineering team, while shipping releases to production 20 times per day or more, JSON Schema is critical in increasing confidence in changes to data, content and APIs.", |
| 5 | + "logo": "/img/logos/github-logo.png", |
| 6 | + "links": { |
| 7 | + "lang": "URL1", |
| 8 | + "url": "/blog/posts/github-case-study" |
| 9 | + } |
| 10 | + }, |
| 11 | + { |
| 12 | + "title": "How 6 River Systems saves time and boosts collaboration with JSON Schema", |
| 13 | + "summary": "Explore the powerful impact of JSON Schema on 6 River Systems' fulfillment operations. Discover how they enabled enhanced collaboration, time savings, and data quality assurance, propelling their successful scaling journey.", |
| 14 | + "logo": "/img/logos/6river-logo.svg", |
| 15 | + "links": { |
| 16 | + "lang": "URL1", |
| 17 | + "url": "/blog/posts/6-river-systems-case-study" |
| 18 | + } |
| 19 | + }, |
| 20 | + { |
| 21 | + "title": "Transforming the technical recruiting industry with JSON Schema", |
| 22 | + "summary": "Learn how Manfred used JSON Schema to transform the technical recruiting industry.", |
| 23 | + "logo": "/img/logos/manfred-color.svg", |
| 24 | + "links": { |
| 25 | + "lang": "URL1", |
| 26 | + "url": "/blog/posts/manfred-case-study" |
| 27 | + } |
| 28 | + }, |
| 29 | + { |
| 30 | + "title": "How Postman uses JSON Schema", |
| 31 | + "summary": "Learn how JSON Schema continues to be a crucial component of the Postman API Platform and the API ecosystem.", |
| 32 | + "logo": "/img/logos/sponsors/postman_logo-orange.svg", |
| 33 | + "links": { |
| 34 | + "lang": "URL1", |
| 35 | + "url": "/blog/posts/postman-case-study" |
| 36 | + } |
| 37 | + }, |
| 38 | + { |
| 39 | + "title": "Using JSON Schema at Remote to scale forms and data validations", |
| 40 | + "summary": "Using JSON Schema at Remote was the first step to solving data validation and form generation problems across all levels at Remote.", |
| 41 | + "logo": "/img/logos/remote-logo.png", |
| 42 | + "links": { |
| 43 | + "lang": "URL1", |
| 44 | + "url": "/blog/posts/remote-case-study" |
| 45 | + } |
| 46 | + }, |
| 47 | + { |
| 48 | + "title": "How Tyler Technologies reduced its client feedback loop with JSON Schema", |
| 49 | + "summary": "Using JSON Schema at Tyler Technologies meant showing added value to clients could take minutes rather than days or in some cases weeks.", |
| 50 | + "logo": "/img/logos/tyler-tech-logo.svg", |
| 51 | + "links": { |
| 52 | + "lang": "URL1", |
| 53 | + "url": "/blog/posts/tyler-technologies-case-study" |
| 54 | + } |
| 55 | + }, |
| 56 | + { |
| 57 | + "title": "How the W3C Web of Things brings JSON Schema to the Internet of Things", |
| 58 | + "summary": "Using JSON Schema at the W3C Web of Things to create an interoperability layer so that different IoT platforms, protocols and standards can operate together.", |
| 59 | + "logo": "/img/logos/wot-logo.png", |
| 60 | + "links": { |
| 61 | + "lang": "URL1", |
| 62 | + "url": "/blog/posts/w3c-wot-case-study" |
| 63 | + } |
| 64 | + } |
| 65 | +] |
0 commit comments