From 376ae42d379da2224fe7a5164bc1e2db9303a437 Mon Sep 17 00:00:00 2001 From: Sarthak Pandey Date: Mon, 28 Oct 2024 00:02:38 +0530 Subject: [PATCH 1/3] Update references from Twitter to X in documentation and links. --- CONTRIBUTING.md | 2 +- README.md | 2 +- components/Layout.tsx | 4 ++-- pages/blog/generateRssFeed.tsx | 2 +- pages/blog/posts/6-river-systems-case-study.md | 4 ++-- pages/blog/posts/[slug].page.tsx | 2 +- .../applicability-json-schema-fundamentals-part-1.md | 6 +++--- .../blog/posts/bundling-json-schema-compound-documents.md | 2 +- pages/blog/posts/code-of-conduct-for-json-schema.md | 2 +- .../blog/posts/hello-2023--hello-json-schema-community.md | 4 ++-- pages/blog/posts/hello-world-hello-postman.md | 2 +- pages/blog/posts/hyperborea.md | 2 +- pages/blog/posts/json-schema-ambassadors.md | 2 +- pages/blog/posts/json-schema-joins-the-openjsf.md | 8 ++++---- pages/blog/posts/new-website.md | 2 +- pages/blog/posts/remote-case-study.md | 2 +- pages/blog/posts/website-analytics-snapshot-2023.md | 2 +- 17 files changed, 25 insertions(+), 25 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 1354a6cd3..73e7a8ff6 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -6,7 +6,7 @@ All types of contributions are encouraged and valued. See the [Table of Contents If you don't have time to contribute, that's fine. There are other easy ways to support the project and show your appreciation: - Star the project on Github -- Post on Twitter or Linkedin about JSON Schema `#jsonschema +- Post on X or Linkedin about JSON Schema `#jsonschema ## Table of Contents diff --git a/README.md b/README.md index 70f9e6cff..bd735eebf 100644 --- a/README.md +++ b/README.md @@ -89,7 +89,7 @@ Thanks goes to these wonderful people who contributed to this website:

JSON Schema Slack - JSON Schema Twitter + JSON Schema Twitter JSON Schema LinkedIn JSON Schema YouTube

diff --git a/components/Layout.tsx b/components/Layout.tsx index 612cf6c12..bdc8e4f03 100644 --- a/components/Layout.tsx +++ b/components/Layout.tsx @@ -345,11 +345,11 @@ const Footer = () => (
- Twitter + X
diff --git a/pages/blog/generateRssFeed.tsx b/pages/blog/generateRssFeed.tsx index f93c9ea24..46b0991f7 100644 --- a/pages/blog/generateRssFeed.tsx +++ b/pages/blog/generateRssFeed.tsx @@ -27,7 +27,7 @@ export default async function generateRssFeed(blogPosts: any) { const authors: Author[] = post.frontmatter.authors.map( (author: any): Author => { const link = author.twitter - ? `https://twitter.com/${author.twitter}` + ? `https://x.com/${author.twitter}` : undefined; return { name: author.name, diff --git a/pages/blog/posts/6-river-systems-case-study.md b/pages/blog/posts/6-river-systems-case-study.md index dee3c1145..23f60c2bc 100644 --- a/pages/blog/posts/6-river-systems-case-study.md +++ b/pages/blog/posts/6-river-systems-case-study.md @@ -6,10 +6,10 @@ cover: /img/posts/2023/6-river-systems-case-study/cover.webp authors: - name: Melinda Gutermuth photo: /img/avatars/melinda.webp - link: https://www.twitter.com/shelikeswords + link: https://www.x.com/shelikeswords - name: Ben Hutton photo: /img/avatars/benhutton.webp - link: https://www.twitter.com/relequestual + link: https://www.x.com/relequestual excerpt: "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." --- diff --git a/pages/blog/posts/[slug].page.tsx b/pages/blog/posts/[slug].page.tsx index 514a95de3..5f9615ffd 100644 --- a/pages/blog/posts/[slug].page.tsx +++ b/pages/blog/posts/[slug].page.tsx @@ -82,7 +82,7 @@ export default function StaticMarkdownPage({ {author.twitter && ( @{author.twitter} diff --git a/pages/blog/posts/applicability-json-schema-fundamentals-part-1.md b/pages/blog/posts/applicability-json-schema-fundamentals-part-1.md index 729ac9c2e..ece4b13ae 100644 --- a/pages/blog/posts/applicability-json-schema-fundamentals-part-1.md +++ b/pages/blog/posts/applicability-json-schema-fundamentals-part-1.md @@ -8,7 +8,7 @@ cover: /img/posts/2022/fundamentals-part-1/cover.webp authors: - name: Ben Hutton photo: /img/avatars/benhutton.webp - link: https://www.twitter.com/relequestual + link: https://www.x.com/relequestual byline: JSON Schema Specification Lead @Postman excerpt: "We explore the fundamental JSON Schema concepts: Applicability, Subschemas, and Assertion Boolean Logic - Everyone needs good fundamentals." --- @@ -394,7 +394,7 @@ When you apply the second subschema in `oneOf` to the instance, there are no con We can use the same approach as before to make sure our subschemas have sufficient constraints. Give it a try, and see if you can manage to make the validation work as expected. -The link is pre-loaded with your starting Schema and instance. Let me know if you get stuck via Slack or Twitter. +The link is pre-loaded with your starting Schema and instance. Let me know if you get stuck via Slack or X. # In summary @@ -412,7 +412,7 @@ I've really enjoyed being able to share the first of our fundamentals series wit You can find all of the example instances and schemas in the JSON Schema Fundamentals repo. -All feedback is welcome. If you have questions or comments, you can find me on the JSON Schema Slack or reach out to me on Twitter @relequestual. +All feedback is welcome. If you have questions or comments, you can find me on the JSON Schema Slack or reach out to me on X@relequestual. # Useful links and further reading diff --git a/pages/blog/posts/bundling-json-schema-compound-documents.md b/pages/blog/posts/bundling-json-schema-compound-documents.md index 11d8a4986..bec12ba0b 100644 --- a/pages/blog/posts/bundling-json-schema-compound-documents.md +++ b/pages/blog/posts/bundling-json-schema-compound-documents.md @@ -269,7 +269,7 @@ The astute among you might have noticed that Compound Documents may not be corre If you’d like a more in-depth look at edge case situations, please do let us know. -You can reach out to us [@jsonschema](https://www.twitter.com/jsonschema) or our [Slack server](/slack). +You can reach out to us [@jsonschema](https://www.x.com/jsonschema) or our [Slack server](/slack). *I hope you’ll agree, Ben has clarified the process for us all here, and we can use this example to fully meet JSON Schema’s bundling expectations when writing tools which bundle multiple resources into compound OpenAPI documents. Thanks, Ben!* - Mike diff --git a/pages/blog/posts/code-of-conduct-for-json-schema.md b/pages/blog/posts/code-of-conduct-for-json-schema.md index 3042bf872..1ac0b759e 100644 --- a/pages/blog/posts/code-of-conduct-for-json-schema.md +++ b/pages/blog/posts/code-of-conduct-for-json-schema.md @@ -97,7 +97,7 @@ Second is our [Open Community Working Meetings](https://github.com/json-schema-o Both sets of calls are open for anyone to join. Both are recorded, but only the Open Community Working Meeting is shared publicly. The Office Hours session is not shared, hopefully allowing people to speak more freely. -Besides Slack, GitHub Discussions, and regular meetings, we do make use of Twitter. You can find me running the [@jsonschema account](https://www.twitter.com/jsonschema). Any mention of "JSON Schema" feeds into a channel on Slack, so we see most of the discussion, and can lend a hand or point people in a direction as appropriate. +Besides Slack, GitHub Discussions, and regular meetings, we do make use of X. You can find me running the [@jsonschema account](https://www.x.com/jsonschema). Any mention of "JSON Schema" feeds into a channel on Slack, so we see most of the discussion, and can lend a hand or point people in a direction as appropriate. Hopefully, this has been a helpful look at why JSON Schema specifically needs a Code of Conduct. Maybe you're considering if your project needs a Code of Conduct. If you have any questions, thoughts, or comments as a result of this article, please feel free to use any of the above methods to make contact. diff --git a/pages/blog/posts/hello-2023--hello-json-schema-community.md b/pages/blog/posts/hello-2023--hello-json-schema-community.md index 5ce908a36..10db4bf0b 100644 --- a/pages/blog/posts/hello-2023--hello-json-schema-community.md +++ b/pages/blog/posts/hello-2023--hello-json-schema-community.md @@ -14,7 +14,7 @@ authors: excerpt: "I am excited to announce that I am joining as Developer Advocate with a focus on serving the Community" --- -Since Ben Hutton joined Postman to work full-time on JSON Schema [the past year](https://blog.postman.com/ben-hutton-joins-postman-to-lead-json-schema-strategy/), other top contributors like Jason Desrosiers, Julian Berman, and Greg Dennis have joined, and now all are full-time supporting JSON Schema. So today, I am excited to announce that I am joining as Developer Advocate with a focus on serving the Community, nurturing relationships with other organizations, launching programs to support and grow the Community, and increasing awareness through content, public speaking, and discussions in Twitter, Linkedin, Stackoverflow or Reddit. +Since Ben Hutton joined Postman to work full-time on JSON Schema [the past year](https://blog.postman.com/ben-hutton-joins-postman-to-lead-json-schema-strategy/), other top contributors like Jason Desrosiers, Julian Berman, and Greg Dennis have joined, and now all are full-time supporting JSON Schema. So today, I am excited to announce that I am joining as Developer Advocate with a focus on serving the Community, nurturing relationships with other organizations, launching programs to support and grow the Community, and increasing awareness through content, public speaking, and discussions in X, Linkedin, Stackoverflow or Reddit. ## Who is this guy? @@ -35,7 +35,7 @@ If you like to know more about me, check out [this intro post](https://www.twili 2023 will be a fantastic year for JSON Schema, and I am excited to be part of this journey with all of you! I can't wait to start connecting with you in the upcoming [working meetings](https://github.com/json-schema-org/community/discussions/35), in [Slack](https://json-schema.org/slack), and [Github](https://github.com/orgs/json-schema-org/discussions). >* Email: benjamin.granados@postman.com ->* Twitter: [@benjagm](https://www.twitter.com/benjagm) +>* Twitter: [@benjagm](https://www.x.com/benjagm) >* Linkedin: [benjagranados](https://www.linkedin.com/in/benjagranados/) >* Github: [benjagm](https://github.com/benjagm) diff --git a/pages/blog/posts/hello-world-hello-postman.md b/pages/blog/posts/hello-world-hello-postman.md index 5fcbff5c2..300be7a58 100644 --- a/pages/blog/posts/hello-world-hello-postman.md +++ b/pages/blog/posts/hello-world-hello-postman.md @@ -20,7 +20,7 @@ If you're a user of JSON Schema, you may know me as the author of [a popular Pyt I'd love to share some good news with the JSON Schema community. -In short: I've joined [Postman's](https://www.postman.com/) Open Technology team to work on JSON Schema full-time. In doing so I'm joining a growing existing group of folks from the ecosystem, including amongst them [Ben Hutton](https://www.twitter.com/relequestual), JSON Schema's specification lead. This brings the number of people working on JSON Schema full-time up to 2 (and counting!). +In short: I've joined [Postman's](https://www.postman.com/) Open Technology team to work on JSON Schema full-time. In doing so I'm joining a growing existing group of folks from the ecosystem, including amongst them [Ben Hutton](https://www.x.com/relequestual), JSON Schema's specification lead. This brings the number of people working on JSON Schema full-time up to 2 (and counting!). What does this mean? Primarily, on my part, more mindspace dedicated to JSON Schema, and hopefully thereby some long-needed improvements to the test suite, to my implementation, to new implementations, and beyond. We hope to grow the community even further, and to connect more strongly with it. diff --git a/pages/blog/posts/hyperborea.md b/pages/blog/posts/hyperborea.md index ba18ac3b1..db8e4acb4 100644 --- a/pages/blog/posts/hyperborea.md +++ b/pages/blog/posts/hyperborea.md @@ -743,5 +743,5 @@ it's all JSON, and we know darn well how to munge that. [repo]: https://git.babyl.ca/yanick/hyperborea-character-sheet [jsonschema]: https://json-schema.org/ [ASSH]: https://www.hyperborea.tv/ -[gizmo]: https://www.twitter.com/gizmomathboy +[gizmo]: https://www.x.com/gizmomathboy [yaml]: https://yaml.org/ diff --git a/pages/blog/posts/json-schema-ambassadors.md b/pages/blog/posts/json-schema-ambassadors.md index 092684898..3b84f8492 100644 --- a/pages/blog/posts/json-schema-ambassadors.md +++ b/pages/blog/posts/json-schema-ambassadors.md @@ -8,7 +8,7 @@ cover: /img/posts/2024/json-schema-ambassadors/cover.webp authors: - name: Ben Hutton photo: /img/avatars/benhutton.webp - link: https://www.twitter.com/relequestual + link: https://www.x.com/relequestual byline: JSON Schema Specification Lead @Postman excerpt: 'Just what is a JSON Schema Ambassador? And how can I help? Keep reading!' --- diff --git a/pages/blog/posts/json-schema-joins-the-openjsf.md b/pages/blog/posts/json-schema-joins-the-openjsf.md index d278756c9..ef6251a02 100644 --- a/pages/blog/posts/json-schema-joins-the-openjsf.md +++ b/pages/blog/posts/json-schema-joins-the-openjsf.md @@ -9,7 +9,7 @@ cover: /img/posts/2022/json-schema-joins-the-openjsf/cover.webp authors: - name: Ben Hutton photo: /img/avatars/benhutton.webp - link: https://www.twitter.com/relequestual + link: https://www.x.com/relequestual byline: JSON Schema Specification Lead @Postman excerpt: "Find out what we've been doing in 2021 and read about our biggest development yet... joining the OpenJS Foundation. Oh, and WE'RE HIRING!" --- @@ -60,7 +60,7 @@ On joining Postman, one thing we discussed is the potential to bring on more peo In the immediate future, we're looking to hire for Software Engineer and for Technical Community Manager / Developer Relations roles. -Feel free to reach out to me directly via [Twitter](https://www.twitter.com/jsonschema) or [Slack](https://json-schema.org/slack) should you have any questions. +Feel free to reach out to me directly via [X](https://www.x.com/jsonschema) or [Slack](https://json-schema.org/slack) should you have any questions. # Regular calls @@ -95,7 +95,7 @@ Currently there are only a handful of articles, but several more case studies ar The blog has an RSS feed, so if you're still using an RSS reader you can catch every new update. -There were long time plans to rebuild the website as a whole, but our need for a blog escalated after some discussion around referencing on Twitter. Our first article was a joint post between myself and Mike Ralphson on the new JSON Schema bundling process. +There were long time plans to rebuild the website as a whole, but our need for a blog escalated after some discussion around referencing on X. Our first article was a joint post between myself and Mike Ralphson on the new JSON Schema bundling process. We've published one case study in two languages, English and Japanese. @@ -124,7 +124,7 @@ Here's the [Issue which lists all the Key Results as individual tasks](https://g If you've read this far, you must be interested in what we're doing at JSON Schema and our plans for the future. -The most effective way to keep up to date is to join our Slack server. We're also using Twitter, which is our primary way to reach out to our community when we have questions. +The most effective way to keep up to date is to join our Slack server. We're also using X, which is our primary way to reach out to our community when we have questions. There are lots more things we want to bring you, including essential tooling to enable a modern JSON Schema ecosystem. diff --git a/pages/blog/posts/new-website.md b/pages/blog/posts/new-website.md index ce557a937..26d3400d3 100644 --- a/pages/blog/posts/new-website.md +++ b/pages/blog/posts/new-website.md @@ -6,7 +6,7 @@ cover: /img/posts/2023/new-website/cover.webp authors: - name: Benjamin Granados photo: /img/avatars/benjagm.webp - link: https://www.twitter.com/benjagm + link: https://www.x.com/benjagm excerpt: "We are so pleased to announce the launch of our new website!" --- diff --git a/pages/blog/posts/remote-case-study.md b/pages/blog/posts/remote-case-study.md index c38c4788a..ba6d107fe 100644 --- a/pages/blog/posts/remote-case-study.md +++ b/pages/blog/posts/remote-case-study.md @@ -6,7 +6,7 @@ cover: /img/posts/2023/remote-case-study/cover.webp authors: - name: Ben Hutton photo: /img/avatars/benhutton.webp - link: https://www.twitter.com/relequestual + link: https://www.x.com/relequestual excerpt: "Using JSON Schema at Remote was the first step to solving data validation and form generation problems across all levels at Remote." --- diff --git a/pages/blog/posts/website-analytics-snapshot-2023.md b/pages/blog/posts/website-analytics-snapshot-2023.md index 957668e63..4409f4e06 100644 --- a/pages/blog/posts/website-analytics-snapshot-2023.md +++ b/pages/blog/posts/website-analytics-snapshot-2023.md @@ -6,7 +6,7 @@ cover: /img/posts/2023/website-analytics-snapshot-2023/cover.webp authors: - name: Ben Hutton photo: /img/avatars/benhutton.webp - link: https://www.twitter.com/relequestual + link: https://www.x.com/relequestual excerpt: "See what we discovered when looking at over 50 million requests to the JSON Schema org domain from the last 7 days" --- From 7f0614f6b90087f698935e7906d5f2fc0aedb481 Mon Sep 17 00:00:00 2001 From: Sarthak Pandey <145528240+SarthakPaandey@users.noreply.github.com> Date: Mon, 28 Oct 2024 09:37:54 +0530 Subject: [PATCH 2/3] Update Layout.tsx From 498a75ccf8d961963ef24d73baa1d7838ee26b97 Mon Sep 17 00:00:00 2001 From: Sarthak Pandey <145528240+SarthakPaandey@users.noreply.github.com> Date: Mon, 28 Oct 2024 09:40:40 +0530 Subject: [PATCH 3/3] Update Layout.tsx --- components/Layout.tsx | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/components/Layout.tsx b/components/Layout.tsx index bdc8e4f03..d2e5287d7 100644 --- a/components/Layout.tsx +++ b/components/Layout.tsx @@ -348,8 +348,7 @@ const Footer = () => ( href='https://x.com/jsonschema' className='flex items-center text-white' > - - X + X