Add resources vendors directory

[BrendanBondurant]

Closes #2458

Description

This PR adds a new resources/vendors page to the Resource Hub and places it in the Resources submenu below Tools & Libraries.

The new page creates a dedicated place for GraphQL vendors, instead of mixing vendor/company entries into other resource pages. Each vendor entry includes:

• Logo
• Vendor name
• Short description
• Website link
• Optional GitHub link

I also added the initial vendor dataset in resources/vendors/data.ts.

Implementation notes

• Vendor entries are modeled at the company/vendor level, not the product level.
• This is intentionally separate from the existing Tools & Libraries catalog, which is more product/library oriented.
• Descriptions are currently free-form, but kept short for consistency on the listing page.
• Vendor entries are sorted alphabetically.

Open questions

This PR implements the page, but there are still a few content/modeling decisions we may want to confirm:

• Should this page include only GraphQL-focused vendors, or also broader vendors with significant GraphQL support?
• Do we want a hard character limit for descriptions?
• Should new vendor entries require editorial/reviewer approval before being added?
• Should vendor data continue to use a dedicated structure, or should it be unified with existing resource entry types later?

Testing

• Verified the new page renders at /resources/vendors
• Verified the submenu link appears in the Resources navigation
• Verified vendor cards render logo, name, description, and links correctly
• Verified alphabetical sorting
• Verified optional GitHub links only show when present

Screenshots

--

[vercel]

@BrendanBondurant is attempting to deploy a commit to the The GraphQL Foundation Team on Vercel.

A member of the Team first needs to authorize it.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
graphql-github-io	Ready	Preview, Comment	Jul 28, 2026 7:09pm

[saihaj]

I wonder if we can source all the data from here https://landscape.graphql.org since that is actively maintained

source: https://github.com/graphql/graphql-landscape

[saihaj]

on resource page this page is not really discoverable

[Urigo]

Suggested change

"The Guild maintains a broad suite of GraphQL tooling and services, including GraphQL Code Generator, GraphQL Yoga, GraphQL Mesh, Hive for schema registry and federation, and the Stellate GraphQL CDN for edge caching.",

"Builds [[Hive](https://the-guild.dev/graphql/hive)](https://the-guild.dev/graphql/hive), the fully open-source (MIT) GraphQL federation platform — schema registry, gateway, router, and observability — run self-hosted and in the cloud at some of the world's largest enterprises, exposing GraphQL APIs as governed MCP tools for AI agents. Maintains many of the ecosystem's most-used libraries, including [[GraphQL Code Generator](https://the-guild.dev/graphql/codegen)](https://the-guild.dev/graphql/codegen), [[Yoga](https://the-guild.dev/graphql/yoga-server)](https://the-guild.dev/graphql/yoga-server), [[Mesh](https://the-guild.dev/graphql/mesh)](https://the-guild.dev/graphql/mesh), and [[GraphQL Tools](https://the-guild.dev/graphql/tools)](https://the-guild.dev/graphql/tools), with tens of millions of downloads every month. Also runs [[Stellate](https://stellate.co/)](https://stellate.co), the CDN for GraphQL.",

[martinbonnin]

I wonder if we can source all the data from here https://landscape.graphql.org/ since that is actively maintained

@saihaj I agree in principle but in practice, the graphql-landscape repo is out of the TSC control (at least I can't merge there) and maintaining it comes with some friction. I'll inquire about it but in the meantime, I'm fine keeping a less official but more active list here.