⚡ Executive Summary: The Evolution of WP Rig
Following our major shift to a modern stack powered by Bun, TypeScript, and Lightning CSS (completely removing Gulp for 10x faster build cycles) , and the introduction of our v3.3 Agentic foundation , WP Rig v3.4 officially moves us from a static starter theme to a composable development platform.
WP Rig v3.4 is one of our most foundational releases yet. If you build custom WordPress themes professionally, this release is engineered to make your day-to-day workflow faster, safer, and remarkably easy to maintain.
This version zeros in on three pillars that matter to modern engineering teams:
- Performance as a Built-In System: Out-of-the-box optimization, not an afterthought.
- The “A La Carte” Component Lifecycle: Reusable, shareable features powered by the new Open Component Registry (OCR).
- Automation-Hardened Tooling: Enterprise-grade security and reliability for CI/CD and AI-assisted workflows.
The Strategic Objectives Behind v3.4
1. Performance as Core Architecture
WP Rig has always been a developer’s secret weapon for speed. With v3.4, performance moves directly into the core runtime via manifest-driven loading, smarter caching behavior, and cutting-edge font delivery techniques.
2. The Open Component Registry (OCR) Foundation
The headline feature of v3.4 is the Open Component Registry. Instead of regenerating common theme features or wrestling with monolithic starter themes, developers can now download or contribute “bolt-on” features a la carte.
Crucially, this supercharges AI-assisted development. Because OCR components contain predictable structural data, AI agents can effortlessly discover, pull in, and compose complex themes using proven building blocks.
3. Secure Tooling for Teams and AI Agents
As engineering workflows increasingly rely on automation, our CLI tools require stronger defaults. Building on the AI groundwork laid out in v3.3 (including MCP-oriented docs and agent setup scripting), v3.4 hardens command execution, sanitizes external data, and provides non-interactive flags designed specifically for AI-driven pipelines.
Detailed Breakdown: What’s New in v3.4
🚀 Performance & Asset Delivery Improvements
- Cookie-Based Critical Asset Strategy: Delivers the absolute best of both worlds. The first page view inlines critical CSS above the fold, while subsequent views automatically serve cached external files.
- Transient-Based Caching: Added deep caching for configuration retrieval and asset loading logic within
inc/Theme.php. - FOUT Elimination: Reduced font flashing by defaulting localized fonts to
font-display: blockalongside automated preloading. - Manifest-Driven Navigation: Extended the
Asset_Providersystem to handle custom loading strategies, automatically delaying non-critical interaction JavaScript.
🧩 Open Component Registry (OCR) Built for Humans & Agents
- Automated Discovery: Refactored core theme files to instantly scan, discover, and register independent components sitting in the
inc/directory. - Registry Scaffolding: New component generation automatically creates the necessary
manifest.json,SPEC.md, andSKILL.mdfiles. - Zero-PAT Workflows: Integrated public GitHub repository registry workflows so common fetches no longer require a Personal Access Token.
- AI-Readable Knowledge Layer: The inclusion of
SPEC.mdandSKILL.mdensures that AI coding partners (like Claude, Copilot, or ChatGPT) understand exactly how to implement and wire up the component without “hallucinations”.
The new component registry is completely open-source. If you are interested in contributed a new component, you can find the repo here.
🛠 CLI Developer Experience (DX) Upgrades
Manage your entire workspace using the brand new npm run rig:* command suite:
| Command | Purpose |
npm run rig:list | Lists all currently active and available components. |
npm run rig:search <keyword> | Searches the Open Component Registry for reusable features. |
npm run rig:test-component <slug> | Runs the built-in diagnostic suite to validate namespaces and integrity. |
npm run rig:prepare <slug> | Replaces brittle automated submissions with a clear, manual contribution prep path. |
- The Automation Flag: Added a global
--yesflag across all commands to unlock seamless, non-interactive CI/CD runs and flawless execution by AI marketing and development agents.
🔒 Security & Integrity Hardening
- Shell-Injection Mitigation: Refactored CLI install execution to utilize
spawnSyncargument arrays. - Path Traversal Protection: The CLI now strictly sanitizes incoming manifest data including slugs, filenames, and asset paths.
- Built-in Security Scanning: Integrated security validation directly into
rig:test-componentand provided OWASP-oriented GitHub Action templates.
How v3.4 Impacts Your Workflow
If you build client sites professionally…
You get perfect baseline performance out of the box—no heavy optimization plugins required. Your builds remain instantaneous thanks to our Bun and Lightning CSS core , and your initial loading states are highly optimized via native critical CSS generation.
If you are scaling with AI and Automation…
The combination of v3.3 agentic readability and v3.4 component structure means your AI pairing sessions will be highly efficient. You can prompt an agent to build a custom feature, and it will output an engineered, registry-ready component that integrates perfectly without breaking your site architecture.
Getting Started with v3.4
Ready to experience the composable era? Upgrade your repository and run through this quick checklist to benchmark your new workflow:
- Audit your components:
npm run rig:list - Test for registry compliance:
npm run rig:test-component <your-component-slug> - Check your performance scores:
npm run test:perf
Want to dive deeper into the technical architecture? Check out our updated, AI-optimized documentation platform over at wprig.io (now featuring an llms.txt file mapping for your custom AI workflows!).