Blueprints 101 guide #5
Conversation
|
I love the buttons to preview the changes. That helps so much. 👏 I’m curious to hear more about the “Community Space”. Is there discussion already around where and what this might look like? 🤔 Would it be a WP.org forum? A developer.wordpress.org area? Or something else? |
|
Hey @adamziel, thanks for the ping! Gonna take a deeper look later today—I got a few suggestions :-) |
minor changes, It might just be a change of simple to basic... Shouldn't we use one of the themes from the Community Theme project as examples, instead of an A8C theme? I found: - https://wordpress.org/themes/blue-note/ - https://wordpress.org/themes/stacks/ - https://wordpress.org/themes/tt1-blocks/
Replace the 'easiest' way, as easy is in the eye of the learner, and it is only easy for someone who already knows.
I add the word Playground a few times so that is clear that blueprints are the configuration files for Playground. I switch the order around and made some minor tweaks to the text.
@colorful-tones it would be this repository :-) We'd have to transfer it to the WordPress organization first, of course. See the main readme at https://github.com/adamziel/blueprints |
Description
Click here to read the content :-)
Launching this Blueprint community space hinges on good materials to explain what Blueprints are and how developers can work with them.
This PR proposes a few pages to cover:
It's a loose interpretation of the previously proposed outline that covers roughly the same topics in a lean way.
Reviewing
Preview proposed documentation
cc @flexseth @bph @jonathanbossenger @ironnysh @westnz @justintadlock @annezazu @bgrgicak @brandonpayton @dmsnell for your opinions. I'd love to learn:
Documentation format
This PR uses Markdown because it's easy to write and can be readily previewed on GitHub.
In parallel, we're exploring a Playground-based documentation writing workflow. It's not ready for production use yet and I didn't want to block the community space on these explorations. Once it's finished, these docs should be easy to migrate.
Closes #2