From the first scrappy prototype to the platform you use today — a full timeline of how WPCursor evolved into the AI-native WordPress workflow.
The biggest leap yet — Claude Opus 4.7 reasoning powers the whole platform, with end-to-end site generation from a single prompt.
Click any element in the live preview panel to attach its CSS path, computed styles, and widget reference straight into chat.
Reusable primitives — buttons, cards, badges, inputs — composable inside any widget through the new component() Twig helper.
Brand extraction, moodboards, contrast checking, and an automated synthesizer that turns inspiration into a full design system.
Native image and video generation with character consistency, marketing studio, and one-click upload to the WordPress media library.
Every EWB widget compiles to a real Gutenberg block. Full-width templates, alignfull support, and a unified block-first authoring model.
Sandboxed PHP/JS/CSS snippet engine with hook bindings, plus first-class Advanced Custom Fields management.
WPCursor became MCP-native. Claude could now read pages, edit widgets, manage themes, and ship sites end-to-end through one open protocol.
Scoped CSS variable system with token presets, automatic component theming, and one-token-changes-everything cascade updates.
EWB widget engine goes public. Visual editor, datasource bindings, Twig templates, and live preview — shipped together.
Custom widget engine matures. Twig templates, control schemas, and the first iteration of the workspace sync workflow.
First scrappy prototype: a WordPress plugin that lets an LLM build pages by talking to it. The seed of everything that followed.