-
Notifications
You must be signed in to change notification settings - Fork 7
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
Introduction/Overview of WordPress Playground #198
Comments
Excited to start working on this :-) |
@ironnysh - Thanks for taking this on. I'm excited to see what you come up with. Feel free to ask me for any help or anyone from the Here's a list with important links for contributing:
The biggest thing is to put your draft (when you start it) in a Google Doc that has open comments/suggestions and leave the link to it here. The review process will happen within the doc. |
Awesome, thank you @justintadlock! |
There's no required/recommended word count. For reference, the average word count of all posts on the Dev Blog from 2023 was ~1,800 words. But, again, this is not something we really look at, so don't think of that as some sort of goal. I only share because I know it helps some folks outline or visualize their plans for a post. |
Yup, that's why I asked 😄 |
Just a quick note that if you run into any issues when using Here's how to turn it on: WordPress/block-theme-examples#9 (comment) |
Thanks for the heads-up, @justintadlock. I had a little adventure with the networking feature a few days ago :-) |
I’d just make sure the article mentions the Blueprints v2 proposal. It would be a really nice progression to have – here’s the existing API, here’s what it can do, go and play with it, and if you’ll struggle to do anything we are designing the next version right now and would really want to hear from you and shape it together. |
Also, I wanted to surface this Blueprint examples wiki page created by @bgrgicak |
I'm not happy with the format, but it's simple to add blueprints. Longterm we should invest some time in making it look better. |
Thanks for the links, @adamziel! @bgrgicak, is this wiki page meant to be used to showcase "community recipes"? I'm asking because I found a few more similar pages across the project, and it might be easier to consolidate them instead of maintaining another source.
|
@ironnysh these examples are all over the place right now. I'd love to consolidate them. The wiki page is there because we've noticed the friction involved in adding new doc pages using Pull Requests prevents us from opportunistic actions like "this Blueprint I've built is cool, let's quickly share it somewhere". Ideally, publishing those would be easy and encourage contributions. The upcoming Blueprints community space could be an opportunity to tie it all together. |
Right, got it. The community space sounds like a perfect fit, but I guess it'll take a while to build and launch. I was hoping to have a single source I can link to from the post 😀 Oh, and off-topic: I found this demo a few days ago |
BTW, if it helps, I'd be happy to open a quick PR:
|
Actually, v1 might be just a GitHub repository to launch it without months of design of development. I'm exploring one here and developer materials are the largest blocker there.
This is lovely, thank you so much for sharing!
Yes please! Thank you! |
PR ready here :-) |
- Adding the Blueprint recipes from the [wiki](https://github.com/WordPress/wordpress-playground/wiki/Blueprint-examples#load-php-code-on-every-request-mu-plugin) to the [examples](https://wordpress.github.io/wordpress-playground/blueprints-api/examples) page in the official docs. - Copying the [demos from the standalone page](https://playground.wordpress.net/demos/) to the [apps/demos page](https://wordpress.github.io/wordpress-playground/links-and-resources/#apps-built-with-wordpress-playground). ## What problem is it solving? Consolidate the examples and demos on the official docs site. [See the discussion here](WordPress/developer-blog-content#198 (comment)). --------- Co-authored-by: Adam Zieliński <[email protected]>
Draft ready for review: https://docs.google.com/document/d/135Y73OQE8qo60pBE6gAc4QIxNvpJ5MNynDg1-HgdHtI/edit |
@ironnysh First, I just want to say thank you for taking on this topic. What you have is written well, but I expected that after having read some of your other work. :) My biggest concern right now is that the tutorial tries to cover too much ground, which means that it never really dives deeply enough and focuses on a specific thing. The goal of this topic was supposed to walk theme authors through creating a theme demo with Playground. And I feel like we've missed that mark. Right now, this is a more general overview of what you can do with Playground. That does leave me questioning whether we should either:
Before moving forward with reviews, I'd want us to get some clarity around this to make sure we're all on the same page. I'd also like to hear your thoughts about which path you'd prefer. I believe either option is OK, but if we go with option 1, we should split these topics so that the original isn't closed. It'd still be great to have a step-by-step walkthrough of creating a theme demo. |
I reviewed the article and wanted to leave the same comment as @justintadlock above (luckily, I read all the comments as well). My thought is: keep this article as is (just change the title) - it's very informative and easy to follow. I think it's important to have this in our blog. Follow up with shorter article (that needs no explaining what the Playground is because we already have that) with specific usecase - building theme demo (link to previous article for more context). This way, we could have many followups concentrating on only specific usecases while broader explanations are already covered. |
I've been exploring some other interesting applications for blueprints that would be a good (shorter) follow-up to a more general article about Playground. |
👋🏼 Chiming in here to support a more general article about playground, along with different use cases in hopes that it might be something the broader dev community can start giving feedback on and using, along with meetup organizers as this could really be game changing. I was about to propose an article on the developer blog around using playground with the following in mind but it seems like this would cover it nicely.
|
For your reference.... Pre-publishing checklist: (updated 1/29/2024)
Post-publishing checklist
|
@bph, all done. Here's the link to the preview: https://developer.wordpress.org/news/?p=3309&preview=1&_ppp=6161ec285a. |
Sorry for just getting to this @ironnysh, but I made a comment in the Google Doc draft about using the |
Thanks, @flexseth, I added it to the post |
Social copy:
|
Working on the second review right now... |
@ironnysh - I left a few minor comments in the Google Doc, but everything looks good to me. Really great writing! |
Thanks, @justintadlock! :-) |
@bph, are there guidelines for the featured image? I uploaded a file, but wanted to double-check (dimensions, file size, format, etc.). |
@ironnysh Handling of the featured image has been quite fluid in the last couple of months. I create mine via Google Slides and you can see my examples there.. If it helps, feel free to make a copy. The purpose of the featured image is for visual support on sharing on the Social webs.
These are just my personal choices. We haven't settled on a standard format yet. |
Perfect :-) |
@ironnysh Seems we are really close to publishing your article! 🙌🏻 As this is your first article on the developer blog, I'll share the checklist with you: Pre-publishing checklist: (updated 1/29/2024)
Post-publishing checklist
Please notify me when you are through the pre-publish list or if you have questions. I'll double-check and will publish the article.. |
@bph, all done 🥳 The post is here: https://developer.wordpress.org/news/?p=3309&preview=1&_ppp=6161ec285a
Social copy:
|
@ironnysh one last note, I recently made the kitchen sink bundle the default to reduce general confusion around the PHP extensions: WordPress/wordpress-playground#1191 It's not a blocker for anything here, but I just wanted to note it. |
Good morning @ironnysh I made a few more modifications: "A new post: https://playground.wordpress.net/?theme=blue-note&url=/?page_id=2" There is still an external link, that needs to be removed: What's your reasoning for those examples URL not made as links? Changed the background color for your code details to a less alarming light blue The post feels a bit devoid of visuals. Screenshots would help visualize the UI: ExamplesI love the "trippy, M. C. Escher-like way of running WordPress inside WordPress. " image :-) This would be the screenshot for it. I am unsure about the other two examples. It might make your article feel like it needs to cover the other options/ settings as well. Just wanted to discuss this a bit. Maybe it just reveals a gap in the documentation we need to close. |
That's great news, @adamziel -- Thanks for letting me know :-) I updated the post. @bph, you're the best, THANK you! :-)
What do you think? I can quickly add an explanation and the 2-photos gallery if you think it's important. |
@ironnysh The Build a site part is really the mind-blowing 🤯 and seeing the Additional actions menu might make it more 'tangible' if you know what I mean. Go ahead if you want to add it. And if you would like to add other screenshots, just remember to add alt-text, too. |
@bph, I ended up rewriting this whole section :-) What say you?
Always! |
@bph, I can't close this issue or the accompanying discussion (#196) Post-publishing checklist
The post was published here: Introduction to Playground: running WordPress in the browser |
Thanks @ironnysh - Ah right. It's the same issue why you can check the checkboxes in my comments. Not enough privileges. Need to look into it. |
Social post schedule for April 24. |
Update: This topic has been updated to be more of an introduction or general overview of Playground.
Discussed in #196
Originally posted by justintadlock January 3, 2024
One of the most painful experiences (at least in my opinion) is managing live demos to showcase your new Wordpress theme to the world. You usually need to set up and maintain a multisite instance for multiple themes. And, it becomes more complex if you want to give potential users access to the admin to actually explore it. It's a headache and management nightmare.
What if you didn't need to do all of that?
That's where WordPress Playground comes in, especially its Blueprints API: https://wordpress.github.io/wordpress-playground/blueprints-api/index
You can easily provide a demo (even multiple demos with their own configurations) by simply providing a blueprint to Playground.
My proposal is to write a guide on using Playground to showcase your theme.
We have some working examples in the current Block Theme Examples repo (click the links in the README to see how this works): https://github.com/WordPress/block-theme-examples
The text was updated successfully, but these errors were encountered: