-
Notifications
You must be signed in to change notification settings - Fork 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
Add component playground to devdocs #8284
Conversation
This is a try. probably not the best way forward but more of a proof of concept Devdocs playgraund.
@stephanethomas You first need to add it to import it like this There a are a few other parts that needs to get added in order to make it work well it an example component.
hope that helps. |
Thanks for the clarification Enej! |
I like the idea to can edit properties on the fly. One concern is that we'll have to add an example.txt file for each component, which is ok for me but It will bring more work at the time to add an example. And the other thing I wonder if the |
@retrofox I think we should add the playground to the individual component view you showed above, but with some design tweaks. Something like:
|
Bumping since #10342 mentions it — if no activity next time it comes up in a scrub for older pull requests I'll probably close it. |
Yes would love to see this in Dev Docs but next week I will on a meet. :( |
Closing as this PR is stale - please reopen if necessary |
This is a try of a devdocs component playground. Probably not the best way forward but more of a proof of concept. In order to get some feedback
component-playground npm package does most of the heavy lifting. It also uses codemirror for the editor.
To try it out load up this branch and go to http://calypso.localhost:3000/devdocs/playground
This is what it looks like right now:

cc @MichaelArestad and @retrofox, @mcsf