// A HARNESS FOR WORDPRESS BUILDS

WordPress dev is fine a tangle. Wonderpress is the harness.

  • MEASURED: ~12 KB MIN
  • ~3 KB GZIP
  • 0 BROWSER DEPS
FIG. 1 — WORDPRESS DONE WRONG [ ✗ ] CHECKS FAILING
Six actors on elastic cables coupled to a free-floating WordPress while three hazards knock everything around.
With no system, everything yanks on everything else It's chaos.
FIG. 2 — AFTER $ WONDERPRESS INIT [ ✓ ] ALL CHECKS PASSING
The same six actors routed through the Wonderpress harness while the same three hazards bounce off and explode against it.
Apply a harness and achieve harmony hazards absorbed: 14

// wonderpress applies organization to the chaos.

01 — BENCHMARKS

BLOAT IS STUPID SO WE AVOIDED IT

12 KB
Zero runtime deps.

*we compiled static kit’s entire baseline and counted: 10.5 KB CSS + 1 KB JS, minified.

  • wonderpress 0 DEPS
    12 KB
  • typical builder 31 DEPS
    ~900 KB
  • premium theme 40 DEPS
    ~1.2 MB
// every dependency is a liability, which is why wonderpress is a complete jerk about them.

02 — PACKAGES

ONE HARNESS · FIVE PACKAGES

// A SUITE OF PACKAGES THAT WORK TOGETHER

Five small packages that form like Voltron.

  1. 01 wndrfl/wonderpress-cli

    The command line

    This is the tool... your daily driver. Scaffold the environment, build partials and blocks, lay out page templates, lint and enforce the standards, even detect drift. Humans get wizards, scripts run headless, and agents speak the same commands over MCP.

  2. 02 wndrfl/wonderpress-core

    The runtime

    The PHP package the theme leans on: partial base classes, manifest-driven ACF groups, the Image and Link primitives, and the token bridge into theme.json.

  3. 03 wndrfl/wonderpress-theme

    A blank theme

    No design opinions: a reset, a grid, and empty stubs. It even removes Gutenberg’s block CSS, so you build up from actual zero.

  4. 04 wndrfl/static-kit

    The front-end kit

    A front-end starter with a build and no aesthetics. Plain, fast, yours.

  5. 05 wndrfl/wonderpress-core

    The runtime

    Under the hood. The engine the other four bolt to: the CLI writes your blocks, core registers them. Installed by init, updated by Composer, never edited by hand.

03 — FAQ

READ BEFORE BUILDING

FAQ

Is this another page builder / site framework I have to buy into?

No. Wonderpress doesn’t touch WordPress core, ships zero styles, and has no dashboard configuration. It’s a development harness for people who write their own themes.

Does Wonderpress include WordPress core?

No, and that’s the point. Wonderpress ships zero core files. WordPress installs, runs, and updates around the harness with no special handling, which means no lock-in and no fork to maintain.

Can I use just one piece?

Not really. I mean you could, but that would be odd. Just use it like its supposed to be used.

What happens to my site if Wonderpress goes away?

Your site keeps running. A Wonderpress theme is plain WordPress code: PHP templates, hooks, and functions that any WordPress developer can read without ever having heard of us. WordPress core stays untouched, so updates, hosting, and plugins all work the way they always have. One dependency worth knowing about: generated partials extend a base class from wonderpress-core, a must-use plugin that lives in your install. It’s open source, it ships with your site, and it has no idea whether Wonderpress still exists. There’s no service to shut down, no API to deprecate, no license key to expire. If you ever wanted to remove it entirely, you’d be rewriting one thin base class, and any competent dev could do that in an afternoon.

What do I need installed?

Docker, WP-CLI, Composer, and Node. That’s the whole list, and the CLI checks for each one before it does anything. If something’s missing, it stops and tells you exactly what to install instead of failing forty steps deep with a stack trace. You probably have most of this already if you’ve built anything this decade.

Does it work with ACF and my existing plugins?

ACF gets first-class treatment: the partials system can ingest your ACF field groups directly, so your custom fields and your templates stay in sync without manual bookkeeping. Everything else is simply none of our business. Wonderpress never touches WordPress core and never sits between WordPress and your plugins, so whatever runs on a normal install runs here. If a plugin breaks, it broke on its own merits.

What’s the license?

Open source, as open as we can legally make it. The tooling (CLI, Static Kit) is MIT. Anything that runs inside WordPress (the theme, the core plugin) is GPL, because that’s how WordPress licensing works and we respect the inheritance. Use it on client work, fork it, sell sites built with it. There’s no commercial tier hiding behind a pricing page.

Is this production-ready?

Every client site at Wonderful ships on it. Wonderpress is the harness our whole agency builds on, which means it gets stress-tested by real deadlines, real clients, and real developers having bad days. This site runs on it too. We’d tell you if it were a weekend project, because we’re the ones who’d have to answer the support emails.

04 — INSTALL

ONE COMMAND, THEN IT GETS OUT OF THE WAY

// QUICKSTART

$ wonderpress init

// requires node 24+, wp-cli, php + composer, and mysql or docker. we print our requirements.