Build with Kirki 6
Stage a Kirki canvas and publish only the reviewed version.

Video coming soon
Your next step is ready.
Follow the complete written guide below.
The video will join it here when it’s ready.
Before you start
- EMCP Pro and a verified AI connection.
- Kirki 6.3.1–6.3.x visual builder with full native access.
- A practice site and a draft page.
Let’s do this, step by step.
Step 01
Select and save the builder
Open Setup → Page Builders. Select Kirki under 1. Standalone builder. Choose Save changes. A Not detected card lists missing requirements.
Start with the required plugin or theme active. Select this builder and click Save changes. This does not convert existing content.
Step 02
Enable the actions and reconnect
Open Setup → Tools → Kirki. Inspect read and write switches; enable the actions needed for this practice task, then Save changes and reconnect your AI app.
Open this integration’s Tools tab. Check both read and write actions; Pro read tools can also start off on a fresh install. Save your choices and reconnect the app so it reads the updated list.
Step 03
Inspect before building
Ask the AI to read Kirki 6's context, supported element controls, and existing design settings.
Ask what this installed version can actually edit. Seeing an element in the catalog does not always mean EMCP can create or change it.
Step 04
Create a canvas draft
Inspect starter elements and installed viewports, then create a native canvas draft.
This lesson uses Kirki's visual builder, not an older Customizer-only installation. Start with the native canvas and available elements.
Step 05
Stage content and local styles
Add a feature section and its page-local responsive styles, then read the latest staged version.
Staging saves the work for review. It does not publish the page. Keep shared library items and global assignments unchanged.
Step 06
Inspect library and page options
Read any library item you want to reference and check whether the page should use full canvas or the theme template.
Symbols and pages have different formats. Discovery does not mean you can edit every library item as a page.
Step 07
Publish deliberately
Check the staged preview and, when ready on the practice site, publish the latest version. Inspect the version restore option.
Publication is its own step. Restoring an older version creates another unpublished stage, which still needs review.
Step 08
Read back and preview
Read the saved page again. Open the native editor, then inspect the frontend at desktop and phone widths.
Check the saved content, editing controls, images, and links. If a newer edit is detected, read it before trying again. A save response alone does not prove the page looks right.
You’re done when…
The Kirki 6 result remains natively editable and the intended save/publication state is verified.
Keep the reference handy.
The docs cover tool details and requirements for this lesson.
You only need the guide for the app or builder you use. Ready to build? Try an Elementor draft or use Gutenberg.
A brief becomes a real page.