-
Couldn't load subscription status.
- Fork 0
landing — interactive editor on landing #48
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
Conversation
|
Issue: This blink is happening because we switch between the elements and the background (the blurry thing) that we use for the smooth gradient borders is visible. We should use a transition group or straight up position absolute the editor. Screen.Recording.2025-09-02.at.16.13.49.movIn this video you might also notice that the color of |
a7ae87a to
b600a58
Compare
99f2b2c to
2eed75f
Compare
Description
Martin proposed making the "How it Works" code samples interactive. We already had CodeMirror, and I already needed to restyle it for the docs, so it required just a new schema, some refactoring and shuffling things around.
I think the idea makes sense, and lets the user experience GraphQL immediately. Even if they're non-programmers, they can maybe get a feel how the data flows and what the experience is like.
I changed the section CTA to state "Try GraphiQL", because we're already trying it out live.
To-do
dynamic(importinstead ofdynamic(() => importinitially so it's good I double checked).