This is the platform map: six pieces — Block Theme, Blocks, Core, Orbit, the WordPress AI Client with the Anthropic provider, and the MCP server — and the lines between them. It’s not an aspirational architecture slide; it’s the literal stack serving the page you’re reading.
The division of labor is strict. The theme owns presentation — patterns and theme.json tokens, nothing else. Blocks ships the reusable pattern library and custom blocks. Core is shared plumbing. Orbit is the control plane: registered abilities, REST surface, and the MCP endpoint that lets AI agents operate the site with the same permissions model as a logged-in user. The AI Client handles model calls so no plugin talks to a provider directly.
Honest footnote: those boundaries are enforced by contract and code review, not by tooling that makes violations impossible — and a few seams are still moving. This diagram tracks what’s on main, not a frozen spec.
The Voyager platform
Six tools. One ecosystem.
Everything we build for clients runs on the same platform we use ourselves. Open architecture, not a black box.
Foundation
Voyager Block Theme
Parent theme with a full pattern library, design tokens, native scroll-reveal motion, and Full Site Editing. The base layer every client site inherits.
Pattern library
Design tokens
Native scroll reveal
FSE
Components
Voyager Blocks
22 custom Gutenberg blocks — animated sections, text reveals, stats counters, testimonial carousels, portfolio grids, and more.
Custom blocks
React + PHP
Block bindings
Data
Voyager Core
Custom post types, taxonomies, and meta fields. Service areas, portfolios, team members, and testimonials — structured data WordPress can query.
CPTs
Meta fields
REST API
Intelligence
Voyager Orbit
AI abilities engine, lead tracking, chat widget, and client dashboards. 32+ abilities that run inside WordPress — content generation, SEO analysis, lead scoring, and more.
32+ AI abilities
Lead tracking
AI chat
Dashboards
AI Infrastructure
WordPress AI Client + Anthropic Provider
Built on WordPress’s official AI infrastructure. AI Client handles routing, the Anthropic Provider connects to Claude, and the Abilities API lets any plugin register AI capabilities.
Claude API
Abilities API
WP Official
Connectivity
MCP Server + Content Pipeline
Model Context Protocol connects WordPress to external AI agents. Content flows from Notion through Claude to WordPress automatically — drafted, reviewed, and published without manual handoff.
MCP protocol
Notion → WP
Auto-publish