-
Notifications
You must be signed in to change notification settings - Fork 263
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
Docs: Guide "WordPress Playground for Plugin Developers" #1664
Comments
Some ideas/scenarios:
|
The Blueprint Gallery has a few blueprints that should be beneficial for above scenarios:
|
Here's a Playground-based plugin development workflow: Plugin.dev.-.GitHub.integration.pull.update.export.PR.mp4 |
Also the current Blueprints builder might be useful to mention until we have a block-based one: Blueprints.builder.mp4 |
Pull Request previews and GitHub proxy are also likely of interest here. |
@akirk built Blueprint building UI that makes building plugin previews easy. It would be great to showcase that, maybe have a video, and showcase how to put together a simple plugin preview. |
@adamziel, is this option currently enabled (or is it working)? |
@juanmaguitar Chrome may be the only browser that supports it today. I know Brave is Chrome based, but I think you need Chrome specifically. |
As both #1664 and #1663 require info about how to provide content for a demo in Playground I think it's best to create a separate guide with this topic that can be referenced from these guides This PR belong to a set of three guides that are meant to be published together - WordPress Playground for Theme Developers #1732 - WordPress Playground for Plugin Developers #1750 - Providing content for your demo #1747
This PR addresses #1664 This PR belong to a set of three guides that are meant to be published together - WordPress Playground for Theme Developers #1732 - WordPress Playground for Plugin Developers #1750 - Providing content for your demo #1747 _Note: There was an older version of this PR at #1745 that was closed_ --------- Co-authored-by: Birgit Pauli-Haack <[email protected]>
As part of #1602 there are plans to create a guides section where specific guides to tackle specific needs can be added to the docs.
I think a "WordPress Playground for Plugins Developers" guide could be a good candidate. These are some of the initial ideas that I think could be included as guidance for plugin developers to leverage WordPress Playground for their work.
Playground for Plugin Developers
see blueprint.json
Which key ideas should be reflected in this guide for Plugin Developers?
cc: @richtabor @ndiego @justintadlock @bph @ryanwelcher
The text was updated successfully, but these errors were encountered: