Build with agents. Keep the source in view.

Build pages and design reusable islands locally with your coding agent. Manage content in WordPress, keep your custom theme and choose Platform sync, ZIP delivery or the Git deployment beta.

Explore documentationGit deployment · Beta
export default function Hero({ fields }) {
  return (
    <section>
      <h1>{fields.title}</h1>
    </section>
  );
}

Build the pattern once. Use it across pages.

An island combines a supported React template, editable fields and sample content. Reuse it across pages with separate values for each placement, then compose complete pages with Document Blueprints.

Explore documentation
version: 1

fields:
  title:
    type: string
    label: Heading
  description:
    type: richtext

Choose the behavior each section needs.

Start with server-rendered content and add browser interaction where it serves the page.

  • Server-rendered content

    WordPress renders islands with their page content.

    Explore the WordPress runtime

  • Selective interaction

    Supported interactive islands add browser behavior. Static islands can render without client JavaScript.

    Explore documentation

  • Dynamic content

    Use supported queries for WordPress posts or WooCommerce products, with fixtures for local previews.

    Explore documentation

Check each stage of delivery.

Build locally, deliver a complete release and manage content in WordPress. Use Studio review through Platform or ZIP, or opt into a Git deployment hook.

  1. Build and preview

    Compose pages and design reusable islands in Local, then inspect their content and behavior in the browser.

  2. Validate and compile

    Validate the source and package a complete release. For Git, build locally and commit the ZIP, or build during deployment.

  3. Deliver and activate

    Review and activate in Studio through Platform or ZIP. The Git deployment beta verifies and activates from an explicit deployment hook.

Questions from developers

Do I need a Platform account to start?

Local creation and preview work without Platform sign-in. Git deployment also works independently. You can still connect the same Local project to share islands through Platform; connected services keep their own access requirements.

Can I use arbitrary React packages?

Islands use a supported React subset and compilation rules. Check the island contracts before choosing a package.

Does syncing replace saved WordPress pages?

A compiled release supplies templates and assets. Saved page content and Document application use separate workflows.

Can I keep Bedrock and my own theme?

Yes. The opt-in Git deployment beta supports a custom theme and a Bedrock-style project layout. Local can live at the project root or inside the theme. Keep private release storage outside the public web root and protect theme-contained source from HTTP access.

Do I need Node on the deployment server?

For this beta, yes: Node.js 22+ prepares styles for saved CMS content in both build routes. You can build the release locally or during deployment. Normal frontend requests remain PHP-only.

Can a custom dashboard use Local design tokens?

Your theme owns the dashboard and its behavior. Import the authored Local tokens into the dashboard’s own Tailwind build and scan its own source files. The Git workflow includes a build example; the dashboard does not need to be an island.

Start with one reusable section.

Choose a supported coding agent, define the editable fields and follow one section through to WordPress.

Explore documentationRead the Git beta workflow