new landing page #2078
new landing page #2078
Conversation
new landing — hero
new landing — navbar
new landing — trusted by
new landing — a graphql query
new landing — proven solution
new landing — five pillars
new landing — powered by community
new landing — graphql advantages
…ustry Add Quotes From Industry section
new landing — footer
new landing — data colocation
Add the wires / API gateway section
new landing — fixes
new landing — docs tweaks
|
@hasparus is attempting to deploy a commit to the The GraphQL Foundation Team on Vercel. A member of the Team first needs to authorize it. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Should the nextImageExportOptimizer folder be tracked under git or is it a build asset that can be removed?
There was a problem hiding this comment.
It predates my involvement, but I assumed it was tracked initially to make the builds on CI and deploys faster as it's idempotent.
To be fair, I'd love to have some architectural decision record on the choice of the optimizer. I think I can guess a few reasons (using output: export is one of them), but (as IMHO these placeholders and their transitions are subpar) in the future we could consider running an image proxy or generate placeholders with a different solution.
We can try to gitignore this directory and see if anything breaks on staging. cc @saihaj
| {[ | ||
| "Deliver high-performance user experience at scale", | ||
| "Secure and stabilize your API with a strongly typed schema and validated queries", | ||
| "Reduce dependencies through efficient, distributed development", |
There was a problem hiding this comment.
Can someone explain this one to me? What dependencies are we reducing?
There was a problem hiding this comment.
@saihaj is this a microservices argument? shall we swap it with sth else?
There was a problem hiding this comment.
yeah the idea is about how federated subgraphs let's smaller team and push features to prod. With a monolithic graph you have to schedule deployments and work across teams (that is what "dependency" is meant here) but with a federated subgraphs your team can deploy their subgraphs and the gateway automatically will update (composition and all the tooling around it make it possible).
cc @bignimbus @Urigo in case you have better copy for this use case
Co-authored-by: Benjie <benjie@jemjie.com>
Co-authored-by: Benjie <benjie@jemjie.com>
* Extract edges and boxes out from the components. * Make diagram boxes and edges responsive * Make the diagram less tall * Animate client edge on small screens * Animate server edges on small screens * Remove next step on background click per Uri's request * Rotate query sideways on small screens
Co-authored-by: Benjie <benjie@jemjie.com>
Description
Howdy. I updated the landing page according to the new designs discussed in graphql/community-wg#21.
If you're interested in reading it step by step in chunks bigger than one commit, you can find the PRs reviewed by @saihaj in my fork hasparus/graphql.github.io/pulls?q=is+new-landing+.