Build with Flatsome
Validate native blocks, save a draft and keep the page editable in Flatsome Builder.

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.
- Flatsome Site Builder and the Flatsome Block Theme 1.0.0-beta.7 or later, or a child of that theme.
- 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 Flatsome under 1. Standalone builder. Choose Save changes. A Not detected card lists missing requirements.
In WordPress, open EMCP Tools, then Page Builders. Under Standalone builder, select Flatsome and choose Save changes. If the card says Not detected, read what it needs before going on.
Step 02
Enable the actions and reconnect
Open Setup → Tools → Flatsome. Enable the read tools and the writes this practice task needs, then Save changes and reconnect your AI client.
Open Tools and select the Flatsome tab. All seven page and pattern writes start off, and so does the theme write tool. Turn on only what this lesson needs.
Step 03
Inspect before building
Ask the AI to read Flatsome's context, the block list, and the schema and supports for the blocks it plans to use.
Ask what this installed version can actually build. A block can have a schema and still be unavailable, so the list matters as much as the schema.
Step 04
Validate, then save a draft
Have the AI validate the block tree without saving, create a draft, then save the tree with a full replacement.
Validation shows the problems before anything is stored. The page stays a draft until you publish it separately.
Step 05
Patch with a fresh read
For later changes, read the page, then patch it with the expected hash from that read.
If someone else edited the page in between, the hash no longer matches and the write is refused. Read again rather than forcing it.
Step 06
Read back and preview
Open the page in Flatsome Builder, make a small native edit and save. Then inspect the frontend at desktop, tablet and phone widths.
The page should open with no invalid block warnings. A native save followed by a read through EMCP proves both sides agree.
You’re done when…
The Flatsome draft opens in the native builder without block recovery, and a native save reads back through EMCP.
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.