WP Enterprise FSE Starter
BLOCK THEME · AAA CONTRAST
Extracted so the theme layer is reusable without dragging business logic along. No build step, no external font CDN, and a dark style variation whose contrast ratios are stated rather than assumed.
- Maintainer
- Pixy Puala
- Vertical
- WordPress themes · FSE
- Year
- 2026
- Role
- Open source
- Stack
- WordPress block theme
- Status
- ● Public repo
- Verified
- Source on GitHub
Problem
Most FSE starters either ship empty or bundle opinionated business logic into the theme, which is exactly the coupling that makes a redesign expensive. And nearly all of them load fonts from a CDN, leaking every visitor's IP address to a third party for no functional gain.
Constraints
Decisions
Self-hosted fonts, always
Literata and Atkinson Hyperlegible Next ship with the theme under SIL OFL 1.1. No external CDN call means no visitor IP leaked to a third party on first paint.
Contrast is measured and published
The dark style variation states its ratios — body text 16.4:1, links 9.4:1 — comfortably past AAA. A claim with a number attached can be checked.
No build step
theme.json, templates and patterns only. A starter that needs a toolchain to produce a stylesheet is a maintenance liability for the team that inherits it.
Build
Stack
- ▸ WordPress block theme · theme.json
- ▸ Templates · template parts · patterns
- ▸ Self-hosted Literata + Atkinson Hyperlegible Next (OFL 1.1)
- ▸ Dark style variation · AAA contrast
- ▸ CI theme.json validation · PHP lint
- ▸ WordPress Playground one-command demo
Tooling
- ✓ kept GitHub Actions · Playground blueprint
Results · Measured
CI validates theme.json and lints PHP on every push. The Playground blueprint gives a one-command live demo without a local install.
Tradeoffs
This is the thinnest repository in the set by design — six theme files, no test suite, because there is no application logic to test. Its correctness is enforced by theme.json validation and lint rather than by unit tests, and pretending otherwise would be theatre.