Export
WordPress
The same build also targets WordPress. Nothing about the section source changes — only what the conversion step produces.
Two routes
| Route | Produces | Suits |
|---|---|---|
| Kirki | Theme customiser fields and templates. | A custom theme where the design is the theme. |
| Elementor | Elementor sections you can keep editing in the page builder. | Sites already being maintained in Elementor. |
The source does not change
A Flow site is Webflow-compatible HTML, CSS and JavaScript. The Webflow rulebook happens to produce markup that converts cleanly almost anywhere — semantic elements, real class names, no framework dependencies, no external files.
So you do not build a WordPress version. You build once and convert twice, if you need both.
What differs from the Webflow route
- WordPress has no direct equivalent of Webflow Components. Repeated blocks become template parts or Elementor templates instead.
- Dynamic content is bound with WordPress' own tools rather than a Webflow CMS collection.
- Form handling is whatever your WordPress plugin provides; the Webflow form attributes are inert there and harmless.