Docs: Explain all the Playground repositories

[adamziel]

Let's write a page that explains the structure of the larger Playground initiative, especially around GitHub repositories and what are they for.

Repos to cover:

• https://github.com/WordPress/wordpress-playground/
• https://github.com/WordPress/playground-tools/
• https://github.com/WordPress/blueprints-library/
• https://github.com/adamziel/blueprints/
• https://github.com/adamziel/playground-docs-workflow (an exploration for a new and improved documentation contribution workflow)

Done is

• A Pull Request for this repository proposing a new documentation page at packages/docs/site/docs/01-start-here/04-wordpress-playground-ecosystem.md. Note there's a lot of overlap with Docs: Explain Playground vs wp-now vs VS Code extension #1256 and it might (or might not) make sense to merge the two.

Related resources

• Introduction to Playground
• Blueprints 101
• Existing Playground documentation
• Contributing to Playground documentation.

[flexseth]

Welp, I got excited and worked on it and missed the

A Pull Request for this repository proposing a new documentation page at packages/docs/site/docs/01-start-here/04-wordpress-playground-ecosystem.md

FWIW: I've been having some issues picking up on using Git with PRs, so maybe this was my lowered barrier-of-entry way to go.

• Playground repositories overview #1270

Note

There's no info on the docs-workflow repo - I'm trying to get done what I can before people get online shortly.

[flexseth]

@adamziel I will add the playground-docs-workflow repo and request review again

[adamziel]

@flexseth actually this is a good repo to target, let's stay here for now, I'm happy to help remove the extra files from this PR – the playground-docs-workflow needs a bit more love before it can power the documentation.

[flexseth]

I went in the wp-cli room twice today to try to talk to Alain about a trick to bring in Markdown files in bulk. Pretty sure I can get it working either way, but he could probably give a one-liner right off the top of his head. Anyways- think I figured out how to programmatically convert Markdown to Block Markup...

[adamziel]

Related adamziel/playground-docs-workflow#51

[flexseth]

Playground Repositories overview PR

• Playground repositories overview #1270

Build passed, reviewed by @ironnysh 🏁

merge at your leisure, comment, etc!

[ironnysh]

reviewed by @ironnysh

Not necessarily a blocker, but I haven't reviewed the text yet.

@flexseth, see #1270 (comment)

Update: Done now. It's quite a change, so I provided some (hopefully compelling) reasoning :-) dc8302c