Setting the file. One moment.
Subchapter 2.1
references/decision-tree.mdMarkdown3 KBView on GitHub
This is a lightweight routing guide. It assumes you can run wp-project-triage first.
Use triage.project.kind and the strongest signals:
wp-core → treat as WordPress core checkout work (core patches, PHPUnit, build tools).wp-site → treat as a full site repo (wp-content present; changes might be theme + plugins).wp-block-theme → theme.json/templates/patterns workflows.wp-theme → classic theme workflows (templates PHP, functions.php, style.css).wp-block-plugin → Gutenberg block development in a plugin (block.json, build pipeline).wp-plugin / wp-mu-plugin → plugin workflows (hooks, admin, settings, cron, REST, security).gutenberg → Gutenberg monorepo workflows (packages, tooling, docs).If multiple kinds match, prefer the most specific:
gutenberg > wp-core > wp-site > wp-block-theme > wp-block-plugin > wp-theme > wp-plugin.
Route by intent even if repo kind is broad (like wp-site):
wp-interactivity-api.wp-abilities-api.wp-playground, then follow its routing wrapper.blueprint.wp-playground, then read references/cli.md or references/debugging.md.wp-playground, then read references/website.md.wp-block-development.wp-block-themes.wp-plugin-development.wp-rest-api.wp-wpcli-and-ops.wp-build-tooling (planned).wp-testing (planned).wp-phpstan.wp-performance.wp-security (planned).