BuilderBeta
Sign in

WordPress → Next.js

Bring the site over. Then describe what to change.

Builder rebuilds your WordPress site as a Next.js project, then hands you an editor where plain English becomes a real code change — proposed, previewed and approved before it ships.

Start a conversionOpen the dashboard

Builder is in beta and under active development. Every conversion is reviewed by a person before it goes anywhere near production.

Your instruction

Make the section heading bigger and hide the second call to action.

Proposed changes

3
  • update_styleel_12fontSize · 60px
  • update_styleel_12lineHeight · 1.05
  • set_visibilityel_47false
Affects 306 pages

Why an instruction never breaks the page

The model proposes typed operations, not rewritten files.

Every request comes back as a short list of operations aimed at specific elements — never a fresh draft of your component. Content bindings survive by construction, the change is legible before you accept it, and nothing reaches your site until you approve it.

  • Restyle

    Type, spacing, color, borders, shadows — anything expressed as a style on an element.

  • Show and hide

    Turn a section off on one page or across every page built from the same design.

  • Reorder

    Move a block above or below its siblings without touching the markup around it.

  • Reword

    Replace plain-text content in place, leaving the fields that feed it untouched.

It knows which pages share a design

519 pages. 49 designs behind them.

document 1990
306
document 2841
120
document 691
33
document 978
15
page-specific
45

Four designs account for 474 of these pages. Treat every URL as its own page and you get 519 components that drift apart the moment one is edited. Group them by the design that drew them and you get 49 — which is also why one instruction can update 306 pages at once, and why Builder tells you that before you approve it.

How Builder learns a site

  1. 01

    Read

    Builder walks the sitemap and content API to list every page the site actually serves.

  2. 02

    Capture

    Each page is opened in a real browser — lazy images, carousels and popups included — and recorded as it renders.

  3. 03

    Recognise

    WordPress names the design behind each page in its own markup. Builder reads that and groups pages that share one.

  4. 04

    Learn

    Color, type, spacing and effects are lifted into a theme you can edit in one place.

  5. 05

    Build

    One React component per design, bound to per-page content, with routes, redirects and metadata.

What survives the move

  • Popups and dialogs
  • Sticky headers
  • Carousels and sliders
  • Tables of contents, rebuilt
  • Fonts, self-hosted
  • Title, description, canonical
  • Redirects
  • GTM and Hotjar
  • Content fields, still dynamic

Point it at a URL and read the proof.

Builder shows you every page it found, which design drew each one, and what it built — before you export a thing.

Start a conversionSign in