The parts of the stack you can read tonight: the Voyager Block Theme, the Blocks pattern library, and the engineering playbook we run projects by. Public repos, real history, no cleaned-for-show branches. This demo site’s own theme joins them at first deploy.
We publish these because they’re better for being public — patterns get forked into other agencies’ themes, playbook pages get argued with, and WordPress core work flows back upstream. If you’re evaluating the platform as a developer, start with the theme repo: it’s the smallest honest sample of how everything here is built.
The boundary, so nobody has to guess: Orbit (the control plane) and the Portal stay commercial. Open where openness compounds, paid where the operational value lives. If that line moves, it’ll move in the changelog, not in a quiet license swap.
Open source
We build in the open
We contribute to WordPress core, publish engineering best practices, and open-source our tools. The WordPress ecosystem made us — we build it back.
💻
GitHub Repos
Voyager Block Theme, Voyager Blocks, and engineering documentation — all public. Fork it, learn from it, contribute to it.
📚
Engineering Playbook
How we build block themes, structure design tokens, write custom blocks, and integrate AI into WordPress. Published publicly.
👥
Community
Join our Discord for WordPress builders, AI enthusiasts, and business owners who want to build smarter. Free, no pitch.