Blueprints: Research how people use them

Open
#51 2 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
php, wordpress
Domain
documentation

Research direction

Start by reviewing the three linked Blueprint examples and the plugin-directory examples mentioned in the issue. Document how people use Blueprints, including perceived strengths, shortcomings, piping PHP, and inclusion of additional plugins. Done means the issue contains a useful collection of examples and usage patterns.

Written by the indexing model from the issue text.

Description

Do we think recipes are being used in the wild yet? Do we have examples of that to look at?

Plugin authors are starting to use Blueprints in the plugin directory, which provides some great examples. What other examples are out there? Understanding their perceived strengths and shortcomings would be greatly useful for building Blueprint builders and other experiences. Do people resort to piping PHP often? Do they mostly use it for including additional plugins? etc.

Here's a few examples I could think of, feel free to edit this issue and update the list:

cc @tellyworth @StevenDufresne @jdevalk @akirk

Dominant language
PHP
Stars
61
Forks
21
Avg merge
19h 34m
Merged PRs (30d)
7

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from WordPress/php-toolkit

All issues in WordPress/php-toolkit

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.