-
Notifications
You must be signed in to change notification settings - Fork 226
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
(Meetup use case) Create a 'filtered' version for use in Meetups #1536
Comments
Yes, you could do that with a blueprint. There isn't one today, but I'm sure it's possible to do it with CSS and some WordPress hooks. If you end up doing something like this, please consider submitting it to the blueprint gallery to help others. https://github.com/WordPress/blueprints/ |
Hi @IoanaAMuresan, There are a lot of possibilities using playground and custom code. see implementation detailsIt uses this
and the following plugin code (installed from a gist)
What else would you like to see cleaned for a first-time explorer? |
@IoanaAMuresan .. and the welcome page will just not be displayed. If you want to clear all WordPress content of the site and refill it with your demo content, you could run a wp-cli step with the comment wp site empty --yes
|
A few weeks ago, I did a presentation on Playground and blueprints: Developer Hours: Creating WordPress Playground Blueprints for Testing and Demos. The examples repo is available on GitHub, too A great resource is also the Blueprint Gallery with examples that might inspire you to think through other scenarios for your meetup demo site. |
In exploring the possibility of using Playground in introducing non-WP users to the tool, I noticed that the interface is not super beginner friendly.
For instance:
(neither of which are reassuring to a beginner)
I am just getting started with the product, and have not yet explored all the facets of blueprints, but wondering if it might be possible to have a blueprint that cleans up everything that's not really valuable for a first time explorer.
The text was updated successfully, but these errors were encountered: