Kayzart — AI Landing Page Builder with Real HTML

Kayzart turns a plain-language brief into real, editable HTML and CSS inside WordPress. Its live editor gives you direct access to HTML, CSS, and JavaScript, renders every change as you work, and publishes the result as a clean page independent from your active theme. It is not a drag-and-drop page builder — no blocks, and no builder markup left behind in your database. What you get is code you own, with AI built into the workflow.

New in 3.0: AI builds the page, you keep the code
Start from Kayzart > Add new: give the page a title, describe the page you want in plain language, and choose Generate with AI. Page type and CSS mode sit right below in Page settings, and Start with a blank page remains available whenever you want to write or paste the code yourself.

From there, keep going by prompt or by hand. Describe a change and the AI edits your page’s HTML and CSS directly — no copy-pasting between a chatbot and your editor. Select an element in the preview and tell the AI what to change about just that part. Each request runs as a background job with a running activity log you can watch or cancel, and the result is applied to your editor tabs for you to review before you save.

The AI is told which fonts your site can actually render — the families registered by your theme and the WordPress Font Library, plus system font stacks — so the type it picks renders on your visitors’ devices instead of silently falling back to the browser default.

For safety, the AI edits markup and styles only — your JavaScript is read-only context it can read but never change, so AI editing can’t inject or rewrite scripts on your page.

On WordPress 7.0 and later, Kayzart uses the WordPress AI Client and your configured Connector. On WordPress 5.9 through 6.9, it connects directly to OpenAI with the API key you configure in Kayzart and uses gpt-6-sol. WordPress 7.0 sites configure the provider in Connectors rather than in Kayzart; a direct key saved before the upgrade keeps working and stays manageable until you remove it. There is no per-edit fee to Kayzart and no Kayzart server in the loop. AI editing is available by default to administrators and editors.

Or bring the code yourself
Write the page by hand, start from a template, drop in code from a designer, or paste what an AI tool gave you — then ask the built-in AI to refine it. The source doesn’t matter — Kayzart is where that code becomes a page you can preview, keep editing, and ship in minutes, without a child theme and without fighting your theme’s header, footer, and styles.

Who this is for
Freelancers, agencies, and developers who need a clean landing page fast and want full control over the result — without a child theme, a drag-and-drop builder, or a build pipeline. If you don’t write code, you can still get a page: describe it and let the AI build it, ask for changes in plain language, and edit text, links, and images visually from the Elements panel. The difference is that when you do want the code, it is right there and it is yours.

What you can do
* Start with a bundled business service template in Japanese or English, each with its own Google Fonts typography and motion configured through HTML attributes, without an AI connection or template server
* Describe a page from Kayzart > Add new and have the AI build it as the editor opens
* Edit your page with AI in plain language — it changes the actual HTML and CSS, inside WordPress
* Keep JavaScript AI-safe: the AI reads your JS for context but never edits it
* Point the AI at a selected preview element to refine just that part
* Let the AI style with fonts your site actually has — your theme’s and Font Library families, plus system stacks
* Watch each AI edit run as a background job with a live activity log, and cancel any time
* Review AI changes in the editor before you save — nothing is published automatically
* Edit everything live with a CodeMirror 6 editor and instant iframe preview
* Click an element in the preview to jump to its code (real-time DOM selection)
* Keep the page theme-independent in Standalone mode, or render inside your theme in Theme mode
* Use plain CSS or TailwindCSS (auto-compiled) per page, and switch a page between the two later
* Run modern JavaScript (Classic script or ES Module)
* Bring a full HTML/CSS/JS page from anywhere and run it as-is
* Open Kayzart straight from the block or classic editor, which shows a Kayzart card instead of the usual content area
* Duplicate an existing landing page as a draft from the page list
* Write site-wide AI instructions once — text and background colors, fonts, tone of voice — and every AI request follows them
* Tune AI editing site-wide: default model, maximum turns per request, and maximum instruction length

Works great with
Bring HTML from anywhere — hand-written, a template, a designer, or an AI tool like ChatGPT, Claude, Gemini, or v0 — then keep editing it with the AI built into Kayzart. Whether the code starts as a paste from a chatbot or a hand-written draft, Kayzart is where it becomes a real, publishable WordPress page you can refine by hand or by prompt.

Development repository: https://github.com/ksartoffice/kayzart-live-code-editor

The admin editor bundle (assets/dist/) is compiled from the TypeScript/React sources in src/ with Vite. Building requires Node.js 20.19 or later. To reproduce the build from the repository: install dependencies with npm install and composer install, then run npm run build to generate the bundled assets. npm run plugin-zip produces the distributable package.

External services

Google Fonts (bundled Business Motion templates)

The Business Motion templates use fonts from Google Fonts. The Japanese template uses Noto Sans JP (weights 400, 500, 700, and 900); the English template uses Instrument Sans (weights 400, 500, 600, and 700) and Instrument Serif (italic). Only these families can be declared by a bundled template. Each card identifies its fonts and explains the external connection before the Preview template and Create from this template buttons. There is no separate opt-in checkbox, confirmation dialog, account, or site-wide font setting. Opening the template list, installing, activating, or updating Kayzart does not contact Google Fonts or preconnect to Google.

After you choose to preview a template, your browser requests a stylesheet from https://fonts.googleapis.com/ and font files from https://fonts.gstatic.com/. Pages you create from these templates make the same browser requests when displayed, including in the editor preview and on the published site. These requests expose normal connection information, such as the visitor’s IP address and browser HTTP headers, to Google. The stylesheet link uses a no-referrer policy. Kayzart does not add tracking parameters, send the page text through the Google Fonts text parameter, or contact Google from the WordPress server for this feature. JavaScript for the template is bundled locally; no JavaScript library or analytics service is loaded. If fonts cannot load, the page uses system fallback fonts and remains usable. To remove Google Fonts from a created page, remove its Google Fonts stylesheet link from the custom head; the font stack will fall back to local fonts.

Google Fonts: https://fonts.google.com/ — API documentation and terms: https://developers.google.com/fonts/docs/css2 and https://developers.google.com/terms — privacy policy: https://policies.google.com/privacy

Kayzart sends AI requests only after a site administrator configures an AI connection and a permitted user requests an AI operation. Requests can include the user’s instruction, page title, HTML, custom head markup, CSS, read-only JavaScript context, selected element context, available font names, and recent Kayzart AI edit context.

On WordPress 5.9–6.9, and as a fallback on newer versions, requests are sent directly to the OpenAI Responses API using the site’s API key and gpt-6-sol (or the model set with the kayzart_ai_openai_model filter). OpenAI terms: https://openai.com/policies/terms-of-use/ — privacy policy: https://openai.com/policies/privacy-policy/

On WordPress 7.0+, a configured WordPress Connector is preferred. Data handling and terms are determined by the provider selected in WordPress Connectors.

When an AI instruction contains URLs, Kayzart fetches the first three of those pages from the site’s server before calling the AI provider, so the AI can use what they actually say. Only URLs the user typed into that instruction are requested, each once; no links on the fetched pages are followed, and addresses on private or local networks are refused. The text, title, description and image addresses extracted from each page are sent to the AI provider as part of the request. Administrators can turn this off with the “Linked pages” setting under Kayzart > Settings > AI editing.

Kayzart also offers administrators an optional product feedback survey. Every question in it is optional. No request is made merely by installing, activating, updating, or viewing the plugin or survey. When an administrator explicitly submits the form, the selected answers, optional free-text comments, survey version, plugin version, WordPress version, and administrator interface locale are sent to https://feedback.kayzart.com/ and retained for two years. An administrator can review what they sent and send a correction, which replaces the earlier answer. The survey does not send the site URL, administrator name or email address, page content, installed plugin list, or a persistent installation identifier. The receiving server may process IP addresses in short-lived security and abuse-prevention logs. The survey stops being offered after 31 August 2027, or earlier if the service reports that it has closed.

Kayzart privacy policy: https://kayzart.com/en/privacy/ — terms: https://kayzart.com/en/terms-of-use/

The independent deactivation survey sends a selected reason and/or optional comment (up to 1,000 characters), a random answer UUID, survey version, Kayzart and WordPress versions, and admin language to https://feedback.kayzart.com/v1/deactivation-responses only when you choose Send answer and deactivate. Answers are retained for two years. It does not send API keys, site URLs, email addresses, page content, usage history, or persistent installation identifiers. Please do not include private information in comments. The receiving server may retain IP addresses in security logs. Showing, cancelling, or skipping the survey sends nothing. It is not shown for bulk, CLI, or network-admin deactivations. Delivery failure does not prevent deactivation. This survey is separate from the product survey campaign and its end date.

Credits

This plugin bundles third-party libraries:
* CodeMirror – MIT License – https://github.com/codemirror
* Emmet CodeMirror 6 Plugin – MIT License – https://github.com/emmetio/codemirror6-plugin
* js-beautify – MIT License – https://github.com/beautify-web/js-beautify
* Lucide – ISC License – https://github.com/lucide-icons/lucide
* parse5 – MIT License – https://github.com/inikulin/parse5
* TailwindPHP – MIT License – https://github.com/ksartoffice/tailwindphp
* Action Scheduler – GPL-3.0-or-later – https://actionscheduler.org