Blueprints sidebar section for single-click Playground presets #1759
Conversation
…of creating a new one)
…e site runtime configuration
It confused me to see a type like: true | 'not-available' | 'origin-mismatch' All values are truthy so you have to know to compare directly with true. And at that point, it's clearer to use the string literal "available" instead.
|
This is such a great idea.
Since #1731 is keeping multiple temporary sites in-memory, this sounds like a good compromise to me. Perhaps we could create a separate temporary site (and notify the user) whenever they start interacting with "Blueprint preview". At that point, they aren't merely clicking through options but have started "trying things on". |
Initially, we do this by writing one file at a time in Safari, but we can try doing Safari writes in batches in a subsequent commit.
adamziel
force-pushed
the
blueprints-apps
branch
from
7d97425
to
fce5346
Compare
rendering it once the Blueprint is resolved
|
I'm wondering if using the blueprint gallery will be the best thing in the long term. This section is technically Playground Apps. You go there and add a WordPress-based app to your Playground. The Blueprint gallery is more about showing the technical capabilities of Playground while this could be much more. Imagine going to Playground.WordPress.net or your locally installed PWA and seeing all your apps there. To get more apps you just go to the apps section and install more. |
|
Can someone inspect the underlying json? |
@asirota I'm happy to help, please open new issue and share the file with us. |
|
@bgrgicak sorry I wasn't more clear. I meant could there be a feature in this to inspect the json of the blueprint being previewed? Useful for learners. |
To me, showcasing technical capabilities is just a convenient starting point for the Blueprints gallery. It can be both a source of demos and a source of powerful apps. Both use-cases require a central location, contributing workflows, integrations, ways of forking and remixing the Blueprints. Why split that in two places? Once we have powerful app-like Blueprints, we can just add a Note all WordPress directories already work this way. There are demo themes like stacks, and there are powerful themes like TwentyTwentyFour. There are demo blocks and app-like block suites. There are demo plugins like hello-dolly or classic-editor, and there are app-like plugins such as WooCommerce. And in an even longer term, we can propose Blueprints for WordPress core and it will already have an extensive Blueprints directory on day 1. |
I agree, it's more about the naming, but I'm probably jumping 5 steps ahead. |
Motivation for the change, related issues
Adds a "Blueprints" tab to the sidebar for a single-click access to all the Blueprints from the Blueprints directory.
This PR builds on top of the redux integration and uses dataviews.
Implementation
This PR fetches the list of all Blueprints in the directory and displays it in the sidebar using WordPress data views.
Remaining work
Blocked by #1731
cc @brandonpayton @bgrgicak @mtias