WordPress devhub blueprint about blueprints HOT 9 OPEN

@carstingaxion I haven't pushed that any further along, but would love some help!

from blueprints.

Luckily this came already to my attention and is even more cool as it could help preparing a playground with the goal to create and manage demo content for a plugin or theme, that will be saved back to a given repo. I guess @ndiego is working on something similar and me too.

I imagine a world where most WordPress developers have their own little collection of blueprints that suit their specific needs.

from blueprints.

Hello @dmsnell ,

did you explore this dmsnell/phpdoc-parser@bda7e06 any further?

I would like to know, how things went.
I’m sorry for pinging you like this and would appreciate if you could take a minute.

Thanks Carsten

from blueprints.

This would be lovely! I've heard a local setup can be quite challenging. Although that doesn't address the devhub issue, I have some early explorations going for a GitHub-based documentation site workflow: https://github.com/adamziel/playground-docs-workflow

from blueprints.

There is a GitHub token required - for Composer - to make the DevHub local setup work properly, otherwise this seems feasible and helpful!

question: What happens if there are manual steps needed for a blueprint to function? 🤯

from blueprints.

This would be lovely! I've heard a local setup can be quite challenging.

You heard right. It’s not my first attempt and it is … challenging.

Although that doesn't address the devhub issue, I have some early explorations going for a GitHub-based documentation site workflow: https://github.com/adamziel/playground-docs-workflow

Yes this is indeed cool and could help, thank you @adamziel

Luckily this came already to my attention and is even more cool as it could help preparing a playground with the goal to create and manage demo content for a plugin or theme, that will be saved back to a given repo. I guess @ndiego is working on something similar and me too.

from blueprints.

@carstingaxion I haven't pushed that any further along, but would love some help!

Thank you for stopping by @dmsnell and sorry for being that late with my reaction.

I started exploring the idea at https://github.com/carstingaxion/gatherpress-devhub, which currently has 2 branches. Getting the parser to run on the GatherPress code and within the playground worked … somehow and was the first branch.

The second branch houses the absolutely not pleasing experiments or hacks to get the theme running, which didn’t worked yet. Also, but not exclusively because of the composer token @flexseth mentioned. I struggled with that too.

from blueprints.

I imagine a world where most WordPress developers have their own little collection of blueprints that suit their specific needs.

I imagine a world where most WordPress developers share a common collection of blueprints that suits typical needs.

from blueprints.

Making a well-known, nice designed and well structured documentation (website) available to every plugin author with the help of playground could be our take on number 5 of @m|s birthday opinions.

Every plugin and theme should have all the infrastructure that we use to build WordPress itself—version control, bug trackers, forums, documentation, internationalization, chat rooms, P2, and easy pathways for contribution and community. We shouldn’t be uploading ZIPs in 2024!

from blueprints.