List all blueprint node types the compiler supports, grouped by category. Use this to discover what you can place in a blueprint tree. Optionally filter by category.

Get the fields and a concrete blueprint example for one node type. Call before using an unfamiliar widget.

List all available entrance animations, hover animations, and interaction triggers/effects/easing options for use in the motion field of any node. Call before adding motion to a blueprint.

List all available dynamic tag names for use in the dynamic field of any blueprint node. Dynamic tags pull content from WordPress (post title, featured image, author, etc.). Use them in template-type documents (single, archive) to create dynamic content.

Return the design system and best-practice rules to follow when generating a site (theme tokens, spacing scale, type scale, layout, section patterns, accessibility). Read this before building.

Return the structured intake to run BEFORE designing: company facts, audience/goals, brand & design direction, content/structure, and SEO. Ask the client these, fill the returned brief skeleton, then feed brandColor+personality to generate_theme and the answers into the page copy. This is what makes each site specific instead of generic.

Turn a brand color (+ optional accent) and a design 'personality' into a complete, WCAG-checked Elementor theme (colors, font pairing, radii, shadow, spacing). Drop the returned theme straight into a blueprint/site. Run after intake so the palette is built around the client's brand, not a generic template.

Produce an SEO sidecar for a page: trimmed meta title/description, slug, robots, canonical, Open Graph + Twitter tags, JSON-LD business/page schema, and a ready-to-paste block. Returns warnings (missing description, no OG image, etc.). Keep page JSON clean — apply this at the WordPress/SEO-plugin level.

List ready-made, theme-aware section templates (hero, feature-grid, cta-band, testimonials, pricing, faq, contact, navbar, footer). Use them in a blueprint via a node: { type: "template", template: "", params: {…} }.

Get the parameters and a concrete example for one section template.

Compile a blueprint in-memory without writing a file. Returns the element count and any errors so you can fix issues before building. Supports keyframes (CSS @keyframes animations) and globals (named widget definitions for reuse). Set format: "classic" for flat settings output (recommended for maximum import compatibility) or format: "atomic" (default, v4 $$type-wrapped widgets).

Compile a blueprint into import-ready Elementor JSON and write it to a file. The file can be imported in Elementor (Site Settings → Import/Export, or paste into the page template import). Set format: "classic" for flat settings output (recommended for maximum import compatibility with all Elementor versions) or format: "atomic" (default, v4 $$type-wrapped widgets). Supports popup type with triggers/timing via the popup field, Theme Builder conditions via conditions, dynamic tags via dynamic on nodes, CSS custom properties via cssVars, native background/box-shadow props in style, @keyframes CSS animations via keyframes, and reusable widget definitions via globals.

Compile a popup blueprint into import-ready Elementor v4 JSON with popup triggers, entrance/exit animations, and timing rules in page_settings. Use type: 'popup' with a popup config. The popup content goes in the tree.

Compile a whole site to import-ready Elementor JSON: one file per page, all sharing a theme and an optional header/footer (e.g. navbar/footer templates). Supports site-level globals for reusable widget definitions across all pages. Set format: "classic" at site level for flat settings output (recommended for maximum import compatibility), or per-page format to override. Writes a site-manifest.json alongside the pages.

Ingest an Elementor JSON export and extract the settings schema of every widget it contains, merging into a persistent registry. Use this to teach the server the exact shape of widgets/settings not yet known (then get_widget_schema will show them). Provide a file path OR the JSON inline.