Build with Avada Builder
Build a native Avada draft using available content and elements.

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.
- Active Avada theme with Avada Builder 3.16.1–3.16.x; Avada Core for its display elements.
- 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 Avada 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 → Avada. 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 Avada Builder'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
Inspect Core content
If Avada Core is active, list existing Portfolio, FAQ, and Slider records before choosing a display element.
We can reuse existing published content in the page. This discovery step does not create new portfolio items or slides.
Step 05
Create the draft
Create an Avada draft with supported containers, rows, columns, and content elements.
Use the supported element list. Some installed elements are visible for inspection only; the AI should not force them into an unsupported write.
Step 06
Add one existing content display
Use an existing FAQ or portfolio source in a supported display element, leaving the source records unchanged.
Check that the right source items appear. The page layout and the records feeding it are separate parts of the site.
Step 07
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 Avada Builder 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.