Block Library Export

wp0 generates pages as structured sequences of sections — heroes, trust strips, service grids, FAQ accordions, and conversion CTAs. Block Library Export — wp0's WordPress block export AI — converts each of those sections into a registered Gutenberg block pattern that works in any block-compatible theme. The output is standard WordPress markup. No proprietary shortcodes, no plugin dependencies, no lock-in.

If you disconnect wp0 tomorrow, every pattern you exported still works in your editor.

Turning Page Layouts Into Gutenberg Patterns

Every page you build inside wp0 — whether from an AI Theme Brief or a Service Business Template — stores its layout as a sequence of named sections. Block Library Export reads that sequence and produces a self-contained block pattern for each one.

The input is any approved page in your wp0 workspace. The output is a downloadable .zip containing:

• Pattern registration PHP files organized into categories you define (Hero Sections, Trust Elements, Conversion Blocks)
• A theme.json partial with spacing, typography, and color tokens pulled from your brand configuration
• An asset folder with images and icons referenced by your sections, using relative paths ready for the WordPress media library

Upload the contents to your theme directory, and every exported pattern appears in the WordPress block inserter immediately. No build tools, no compilation step.

Section-by-Section Conversion Process

When you trigger an export, wp0 runs through four steps:

1. Section identification. The system parses every section in your page layout — hero banner, social proof strip, service feature grid, testimonial block, FAQ accordion, and CTA footer.
2. Markup generation. Each section becomes valid wp:group block markup composed entirely of core Gutenberg blocks: paragraphs, headings, columns, buttons, images, and group containers.
3. Pattern registration. The exported file includes the PHP snippet that registers each block pattern under your theme's namespace, slotted into the categories you specified during export setup.
4. Asset bundling. Images, icons, and other media referenced by sections are packaged alongside the markup with paths structured for your WordPress media library.

The result is ready to drop into a theme directory without any additional processing.

What You Can Export

You can select individual sections or export an entire page as a pattern collection:

• Hero patterns — headline, subhead, primary CTA button, optional background image. Designed to match the messaging hierarchy from your Page Structure Copilot outline.
• Trust strips — client logos, review counts, and certification badges. Pulls from the proof data you entered during site brief setup.
• Service cards — icon, title, short description, and link. Built for two-, three-, or four-column grid layouts.
• FAQ accordions — question-and-answer pairs using the core details block, structured for FAQ schema output by the Schema Markup Generator.
• CTA sections — single-action conversion blocks with headline, supporting copy, and one form or button.

Each pattern preserves your brand's spacing, font sizing, and color tokens. When you insert a pattern into the WordPress editor, it inherits the destination theme's theme.json design tokens automatically.

Example Exported Block Pattern

Here is what a typical export looks like for a service page hero section:

Pattern name: wp0/hero-service-primary Category: Hero Sections Sections included: Heading (H1), subheading paragraph, primary CTA button, background image container

The exported block markup is a nested wp:group container holding a wp:heading block for the page title, a wp:paragraph for the subheading, and a wp:buttons group wrapping a single wp:button element. The entire group is wrapped in a wp:cover block that references the background image from your asset bundle. Spacing, font size, and color values are defined as theme.json presets rather than hard-coded CSS, so the pattern adapts to any destination theme's design tokens.

A full service page export typically produces five to eight patterns: wp0/hero-service-primary, wp0/trust-strip-logos, wp0/service-grid-three-col, wp0/faq-accordion-schema, and wp0/cta-single-action — each registered under its own category in the WordPress block inserter. Inserting any pattern into a page gives your editor team a fully structured section ready for copy customization, with all brand spacing and typography tokens inherited from the active theme.

Teams following the approach in the Block-First Theme Creation Guide maintain a master pattern library in wp0, export updated versions on a quarterly cadence, and push them to client sites through their deployment pipeline. Because the markup uses only core Gutenberg blocks, the same exported library works across agency client sites running different themes — no rewriting for each builder ecosystem.

Editing Patterns After Import

Exported patterns are starting points, not rigid templates. Once imported into WordPress, your team can:

• Edit copy directly in Gutenberg without breaking the pattern's structural integrity
• Swap images and adjust colors using the theme's global styles panel
• Duplicate a pattern, modify it for a specific service or location page, and save the result as a new variation
• Reorder or remove sections within a page without affecting other pages that use the same patterns

Because each pattern is a registered PHP file, developers can version-control pattern files in Git alongside the rest of the theme. This keeps the design system auditable and rollback-friendly across your entire WordPress network.

Scaling With a Shared Pattern Library

Block Library Export is designed for teams shipping pages at volume. A typical production workflow:

1. Generate pages using wp0's brief-to-layout pipeline
2. Review and approve content inside wp0
3. Export approved sections as block patterns
4. Import patterns into your staging WordPress environment
5. Assemble pages in Gutenberg using the imported patterns
6. Push to production through One-Click WordPress Publish

For teams publishing local service pages at scale, this means you define a section library once and reuse it across dozens of city pages — each with localized copy but identical structural quality. The pattern library becomes the single source of truth for how your pages are built.

Ready to turn your generated layouts into a production block library? Join wp0 early access and export your first pattern set.

FAQ

Does the export work with Full Site Editing themes?

Yes. Exported block patterns register through the standard WordPress pattern API, which FSE themes support natively. You can use them in template parts, page templates, and the site editor without modification. Patterns appear in the site editor's pattern library alongside built-in theme patterns, so your team can insert them into any template part — headers, footers, page content areas — using the same workflow they already use. This makes wp0 exports a natural fit for teams building Full Site Editing themes from scratch or customizing starter themes like Twenty Twenty-Five.

Can I re-export pages after updating content in wp0?

Any page stored in wp0 can be re-exported at any time. If you update content and re-export, you get a fresh pattern file to drop into your theme. Pages that already use the old pattern in WordPress keep their current content — the new export does not overwrite live pages. The re-export generates a new version of the pattern registration file, which you upload to your theme directory to make the updated version available in the block inserter. This approach lets you iterate on your pattern library without disrupting pages already using earlier versions of the same pattern.

What happens to patterns if I switch WordPress themes?

Because exports use only core Gutenberg blocks, patterns render correctly in any block-compatible theme. Visual details like spacing and colors adjust to the new theme's theme.json tokens automatically. No markup changes are needed. If the new theme defines different spacing scales or font families, your patterns inherit those values through the design token system rather than breaking with hard-coded styles. This means agencies can reuse the same exported pattern library across client sites running different themes without maintaining separate markup versions for each one.

Are there limits on how many patterns I can export?

No hard limits. Each section becomes one pattern. A typical page generates five to eight patterns. Teams running large-scale programs with dozens of service and location pages commonly maintain libraries of 40 to 60 patterns without performance issues in the WordPress inserter. If your library grows beyond that, you can organize patterns into categories — such as Hero Sections, Trust Elements, and Conversion Blocks — so editors find what they need without scrolling through an unstructured list.