Architecture
WordPress vs Our Pipeline
WordPress serves every page through 7 layers of server-side processing. Our pipeline eliminates all of them.
WordPress
Visitor Request
PHP Server
+200ms
MySQL
+150ms
WordPress Core
72 PHP files
Theme / Divi
+87KB jQuery, +79KB CSS
Plugin Layer
20+ plugins
Rendered Page
2,288KB, 21.3s
Our Pipeline
Visitor Request
Cloudflare CDN Edge
300+ locations
Static HTML
Pre-built
Rendered Page
90KB, 1.9s
0 server processing
96% smaller
11x faster
Orchestration
How the Orchestrator Works
A single natural-language command triggers the entire pipeline. The orchestrator classifies your intent, builds an execution plan, and dispatches parallel agents to get it done.
Inputs
User Intent
Natural language command
project.json
Domain configuration
Skills Registry
19 composable skills
Orchestrator
AI-powered coordination
Outputs
Execution Plan
Ordered task graph
Agent Dispatch
Parallel skill runners
Progress Tracking
Real-time status
End-to-end flow
Skill System
Skills Map
19 composable skills organized into 6 categories. Each skill is independently testable, versioned, and reusable across all 300+ domains.
Capture
3 skills
Discovers all URLs via sitemap
Playwright headless browser capture
Strips trackers, fixes carousels, rewrites URLs
Transform
4 skills
Parses HTML into structured content.json
Generates clean HTML from templates
Config-driven header, footer, CSS generation
Page-type-specific template engine
Optimize
3 skills
WebP conversion, lazy loading, srcset updates
Strips WP/Divi bloat, defers CSS
MP4 to WebM, poster extraction
Quality
4 skills
10-point audit with auto-fix
HSTS, CSP, X-Frame-Options
Catches frozen carousels, dead widgets
WCAG AA contrast, landmarks, aria
Deploy
2 skills
Wrangler CLI to Cloudflare Pages CDN
Security headers generation
Features
3 skills
Workers + D1 + Turnstile + SendGrid
Color palette, typography, component library
Reusable UI component library