Minimal native WordPress block theme for new sites; not a drop-in upgrade for Webactueel Universal. The installable theme has 12 files: six templates, three template parts, theme.json, stylesheet metadata and GPL license. No PHP/JS, ACF dependency, page builder or custom WooCommerce checkout code.
For agencies: start a new WordPress site from a small, understandable Gutenberg theme instead of inheriting a complex page-builder dependency. For developers: inspect how templates, template parts and design tokens fit together, then run the packaging and compatibility checks below.
This repository is source code for a starter, not a finished client site or a visual design demo. For examples of real responsive client-facing work, see my published website case studies. Those websites are not claimed to run this starter.
A quick code-review path: block templates → theme.json design tokens → runtime QA.
A new WordPress site should be able to start with native blocks and a small, reviewable theme rather than inherit a large page-builder or plugin stack. This starter keeps layout structure inside Gutenberg while making compatibility, packaging and staging decisions explicit.
For website owners: a lean WordPress foundation with editable native blocks instead of a compulsory page builder.
For reviewers: theme templates, reusable layout parts and design tokens that can be inspected independently from the test and package pipeline.
Try it safely: run the build and verification commands, install the generated theme ZIP on a new staging WordPress site, and inspect the editor, responsive templates and navigation before creating any client-specific variation. This repository is a starter, not a copy of an existing Webactueel client design.
Looking for actual design work? See Spring Architecten, RBMB and more independent website case studies. Those projects demonstrate design delivery; they are not presented as sites built with this exact starter.
| Engineering decision | Inspect |
|---|---|
| Native block templates and design tokens | Theme architecture and the installable theme source |
| Repeatable packaging and validation | Source workflow, runtime matrix and tests |
| Release limits and human checks | QA contract and staging acceptance |
Evidence boundary: This is a reproducible starter and testing example—not a public client website, a visual design case study or a production-ready upgrade for an existing theme.
- WordPress 6.6+ and PHP 8.3+ per theme header; verify the chosen target versions.
- Core/Gutenberg owns pages and layout. ACF is optional structured data; field groups must be created deliberately. WooCommerce owns products, cart and checkout.
- Architecture · QA · staging/GO decision · 77 scenarios.
python3 -m unittest discover -s tests -v
python3 scripts/package.py
(cd dist && sha256sum --check SHA256SUMS.txt)CI runs source checks and four isolated runtime profiles (WordPress 6.6/current; PHP 8.3/8.4; optional WooCommerce and ACF Free). It downloads one exact hashed ZIP into runtime jobs. Source checks, browser/editor tests, API/CLI tests and human tests are different evidence classes. Review the latest Actions and failures before using any result.
Installable ZIP: Webactueel-Block-Starter-1.0.5-STAGING.zip (only webactueel-starter/). Source ZIP additionally includes tests/docs. Neither CI nor the starter certifies a live shop, all plugins, WCAG 2.2 AA, real payment or hosting rollback. Production requires separate staging acceptance. Never commit real credentials or customer data.
For a client site, create a separate fork/copy with its own slug, text domain, design, templates, plugin inventory and tests. Keep this starter lean and independently reproducible.
Sources: WordPress themes · WooCommerce blocks · WCAG-EM.