Skip to content

Create graphql-js.org announcement post #2004

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

Draft
wants to merge 1 commit into
base: source
Choose a base branch
from
Draft
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
39 changes: 39 additions & 0 deletions src/pages/blog/2025-06-12-graphql-js-org.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,39 @@
---
title: 🆕 Announcing graphql-js.org!
tags: ["blog"]
date: 2025-06-12
byline: GraphQL-js Maintainers
---

Dear Community,

We're excited to share a milestone in the GraphQL-JS journey, one that puts our community at the center of everything we do.

For years, GraphQL-JS documentation lived under the broader graphql.org umbrella at `/graphql-js`. While this made sense back then, we want to serve y'all better, we want upgrade guides and everything graphql-js specific to live in one easy to navigate place.

We're thrilled to announce that GraphQL-JS has moved to its dedicated home at [**graphql-js.org**](https://www.graphql-js.org).

This isn't simply a change of address, it's a commitment to the community that has made GraphQL-JS what it is today. This new home represents the first step in a larger mission: giving you the comprehensive documentation, clear upgrade paths, and responsive support that a project of this scale deserves.

What This Means for You

- **Easier discovery**: No more hunting through nested documentation structures
- **Focused experience**: Everything GraphQL-JS related in one dedicated space
- **Better navigation**: Documentation organized around your workflow, not our internal structure

Coming soon:

- **Comprehensive upgrade guides**: Clear, step-by-step paths between major versions, GraphQL V17 will be our first attempt at this
- **Enhanced reference documentation**: Every API documented with real-world examples

## An Inflection Point

We see this move as an inflection point, a moment where we recommit to being the reference implementation the community deserves. GraphQL-JS isn't just code; it's the foundation that teams around the world build upon. Whether you're implementing a new GraphQL server, debugging a complex schema, or upgrading between major versions, you deserve documentation and tooling that makes your job easier, not harder.

This is our promise: we're not just maintaining GraphQL-JS, we're investing in its future and yours.

---

_The GraphQL-JS Maintainers_

_Questions or feedback about the new site? We'd love to hear from you in our [GitHub discussions](https://github.com/graphql/graphql-js/discussions) or on the [GraphQL community Discord](https://discord.graphql.org) in channel `#graphql-js`._