Skip to Content
✨ WP Bones v2.0.1 is out! Check the Release Notes →
DocumentationBoilerplatesOverview

Boilerplates

WP Bones ships four curated starter templates on GitHub. Each one builds on the same v2 infrastructure (webpack + yarn + TypeScript + Jest + Prettier) and differs only in what it demonstrates. Pick the one that matches the stack you want to learn or start from.

Try them in the browser

Every boilerplate has a WordPress Playground  blueprint. Click the Playground link on each boilerplate page to spin up a throwaway WordPress install with the plugin pre-activated.

How to start from one

Each boilerplate is a GitHub template repository. You have three options:

  1. Use as a template — click “Use this template” on GitHub and clone your new repo.
  2. Clone + rename — clone the repo locally and run php bones rename "My Plugin Name" to reset the namespace.
  3. Playground first — test-drive in Playground, then grab the .zip from wpbones.com .

All four boilerplates share the same bones CLI, the same yarn scripts (dev/build/test/format/lint), and the same webpack auto-discovery rules. Moving from one to another is mostly a matter of swapping dependencies in package.json.

What stays the same across all four

  • webpack.config.js with auto-discovery of entries
  • package.json scripts: dev, build, test, format, lint
  • tsconfig.json, .prettierrc, jest.config.js
  • The bones CLI (php bones --help) with make:* and migrate:to-v2
  • plugin/ folder (PSR-4 namespace root), config/, bootstrap/, resources/views/

What differs

  • dependencies in package.json — only the UI kit / libraries the boilerplate demoes.
  • resources/assets/apps/ — the demo app(s) specific to each boilerplate.
  • Dashboard Blade view — each shows its own sources inline so learners can read them.
Last updated on