CrocoBuilder

What CrocoBuilder is and what problem it solves

Building complex interfaces in WordPress usually means choosing between layout speed and clean final code: visual builders that generate bloated markup, unnecessary wrappers and styles duplicated between an "additional CSS" panel and the editor's own controls. CrocoBuilder is a frontend builder plugin aimed at developers and agencies who need to build dynamic sites without giving up a clean DOM or real control over the code. Every element you place in the editor maps to a single DOM node, with no hidden markup layers or surprises when you inspect the HTML.

Unified style and CSS control

Instead of splitting styles between visual controls and a separate custom CSS box, CrocoBuilder centralizes everything in a single panel. The CSS Sync feature lets you switch between visual controls and raw CSS code while always editing the same underlying source, so there's never a mismatch between what you see and what gets generated. On top of this there's a CSS variables manager for defining colors, typography and spacing as reusable properties across the whole site, a class manager that generates real class names usable outside the builder (including in Gutenberg), and a customizable breakpoint system instead of fixed breakpoints.

Dynamic content without writing PHP

The Query Builder lets you create custom WordPress queries from the interface, filtering by content type, taxonomy, metadata or relationships without touching code. The Loop Builder builds loops from any query and lets you visually edit the template for each repeated item. The Theme Builder, in turn, gives you control over the site's full structure: header, footer, single posts, archives and product templates. These tools are complemented by visibility conditions (based on user role, device or data) and template conditions for assigning different layouts depending on page type.

Reusable components with full code access

CrocoBuilder includes a component creator built on HTML, CSS and JS, which you can edit manually or generate via AI prompts, with no abstraction layers hiding the resulting code. Components support configurable properties (text, images, colors, repeaters) and internal slots for nesting other blocks without breaking their structure. They can also be used as Web Components with props outside the builder, including in Gutenberg, acting as living pieces rather than static templates.

Supervised AI integration

The AI assistant can assemble pages from existing elements, components, classes and variables based on a prompt, and generate custom components that can then be refined manually without losing compatibility with the builder. Changes generated by AI are not applied directly to the database: they go through a review process that lets you inspect the differences before confirming them. CrocoBuilder also supports connection via MCP so that AI agents can manage structure, queries, styles and pages, plus GitHub versioning for real version control over frontend work.

Who it's for

• WordPress developers who need a visual editor without losing access to the underlying code.
• Agencies looking to standardize project delivery through reusable components and style systems.
• Product teams building dynamic sites with complex queries, conditional templates and repeatable content.
• Projects already using other plugins from the Jet ecosystem that want a builder that fits into that workflow.

Frequently asked questions

Does CrocoBuilder replace Gutenberg?

No. It works alongside Gutenberg: CrocoBuilder handles the frontend rendering of specific pages or global templates through WordPress's standard template APIs, while the rest of the site remains untouched.

Can AI-generated components be edited manually?

Yes. Each component is standard HTML, CSS and JS; you can edit the code directly, and those manual changes won't be overwritten by later AI-generated updates.

Can the generated styling and markup be exported or migrated?

Yes. Because it generates an atomic DOM and real CSS classes, the markup and styles work outside the builder and aren't tied to a proprietary format.

Can AI apply changes directly without review?

No. All AI-generated changes go through a prior verification process that lets you inspect the differences before confirming them on the site.