-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Make GraphQL Playground link more obvious in AdminUI #1190
Comments
Perhaps we just have a big button fixed to the bottom of the sidebar "Developer Resources", which takes users to a dedicated page detailing what's available and that it is strictly visible in development.
|
I'd prefer to avoid the extra click. The links go away in prod mode anyway, so it'll only be devs who see them (unless they're deploying in dev mode, but then they've got other issues :P ) |
It looks like you haven't had a response in over 3 months. Sorry about that! We've flagged this issue for special attention. It wil be manually reviewed by maintainers, not automatically closed. If you have any additional information please leave us a comment. It really helps! Thank you for you contributions. :) |
I politely disagree here :) Getting to the graphQL playground is something we are interested in and we know where it is. But I think we should be designing for people who use the admin interface to manage real world applications. I'd like to get a UX design opinion as well. |
Would love some UX help! Keep in mind my comment above too;
|
It looks like there hasn't been any activity here in over 6 months. Sorry about that! We've flagged this issue for special attention. It wil be manually reviewed by maintainers, not automatically closed. If you have any additional information please leave us a comment. It really helps! Thank you for you contribution. :) |
Since we only display the GraphQL Playground in dev mode, and it's a highly useful feature of the admin UI, we should surface it in a more obvious place for app developers to find.
Mockup:
The text was updated successfully, but these errors were encountered: