The same HTFlow builder, a different destination. The AI builds your site in real HTML, CSS and JavaScript, and the free htflow-for-kirki plugin imports it into your Kirki-powered WordPress site, section by section.
No shortcodes, no locked-in blocks
Shortcodes and proprietary blocks you can't read or take anywhere else.
Generic class names clash, and every new section needs fixing.
Anything beyond the theme's presets waits for a developer.
Six steps from the first sentence to a page you can publish. The tags show who does each one.
Start building freeTell the AI what the site is for, who it's for and the style you like.
HTFlow's AI writes the pages in real HTML, CSS and JavaScript — the same builder as for Webflow.
Change anything on the visual canvas, or ask the AI for it in plain words.
Add the free htflow-for-kirki plugin to your WordPress site running a Kirki-powered theme.
Bring each section into WordPress through the plugin — as ordinary HTML, CSS and JavaScript.
Wire sections to your posts, fields or Kirki settings. WordPress stays in charge of your content.
Design with HTFlow's agent and visual canvas, exactly as for Webflow. Only the export changes.
A free WordPress plugin that imports your HTFlow sections into a site running a Kirki-powered theme.
Class names are specific to each section, nothing loads from a CDN, and there's no framework to reconcile.
Once a section is in, it's yours: connect it to posts, custom fields or Kirki settings.
Plain HTML, CSS and JS — readable, portable and yours.
Use your own key or subscription — HTFlow adds no markup on AI.
Everything the section needs is imported with it.
Your posts, fields and settings keep working the way they do today.
Yes. HTFlow builds the site and the htflow-for-kirki plugin imports it into a WordPress install that is already running a Kirki-powered theme. The plugin is the bridge, not the theme.
Ordinary HTML, CSS and JavaScript, section by section. No shortcodes, no proprietary blobs — markup your theme can carry and you can read.
Yes. Once a section is in, it is yours: edit it in WordPress the way you edit anything else, and control what Kirki exposes through its own fields.
The same builder, a different destination. You describe the site once; the export decides whether it lands in WordPress, in Webflow, or as plain HTML and CSS.
No. You bring your own OpenRouter key, or drive the build from a ChatGPT or Claude subscription you already pay for over MCP. HTFlow takes no margin on AI usage.
Class names follow BEM, so they are specific to the section rather than generic names a theme is likely to be using. Nothing is loaded from a CDN and there is no framework to reconcile.
Yes. HTFlow's MCP server exposes the same tools to any MCP client — ChatGPT, Claude, Cursor, VS Code and others — so the build can happen wherever you already work.
Build the section, import it, then wire it to your posts, fields or Kirki settings in WordPress. HTFlow gets the design and the markup right; WordPress stays in charge of the data.
Start free — bring your own AI key or the AI subscription you already have.
