Revamp Ambassador page

[jemgillam]

I have had feedback from TSC, community members, and end users that our Ambassador page isn't as useful as it potentially could be.

I have redesigned the cards shown on https://graphql.org/community/ambassadors/ to show the Ambassador's location, their strengths, and if they are a Locals organiser it also links to their events page.

I have only filled in the data for myself to show the concept! I have data ready to fill in for everyone else.

I suggest that for the list of "Ask me about" topics we keep it to a kind of normalized list, and also the name of the project the person maintains (if applicable)

Old:

New:

The current list I have is the following, but I will probably collapse some categories:

API architecture, API design, API integration, Code-first GraphQL, Community building, Data modelling, Developer advocacy, Developer experience, Developer tooling, Enterprise GraphQL, Error handling, Federation, GraphQL + AI, GraphQL at scale, GraphQL clients, GraphQL debugging, GraphQL documentation, GraphQL education, GraphQL governance, GraphQL specification, GraphQL testing, GraphQL at the edge, Nullability, Open source, Open source sustainability, Pagination, Production GraphQL, Schema design, Schema evolution, Schema tooling, Schema stitching, Trusted documents, Type safety

Plus the names of particular projects / technologies:

Apollo Client, Apollo Federation, gql.tada, GraphQL Code Generator, GraphQL Editor, GraphQL Hive, GraphQL Java, graphql-kotlin, GraphQL Mesh, GraphQL Network Inspector, GraphQL Voyager, GraphQL Yoga, GraphQL Zeus, GraphQL.js, Grats, Python, React, Relay, Spring for GraphQL, Strawberry GraphQL, TypeScript, urql

[vercel]

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

A member of the Team first needs to authorize it.