A brief becomes a real page.Build with Blocksy Blocks
Embed a reusable Blocksy Content Block in a Gutenberg draft.
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 Blocksy theme and Companion; Content Blocks need Companion Pro.
- A Gutenberg draft.
Let’s do this, step by step.
Step 01
Enable and save the pack
Open Setup → Page Builders. Switch on Blocksy Blocks under 2. Gutenberg block plugins. Choose Save changes. A Not detected card lists missing requirements.
Start with the required plugin or theme active. Switch on this block pack and click Save changes. This does not convert existing content.
Step 02
Enable the actions and reconnect
Open Setup → Tools → Blocksy Blocks. 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
Read the current blocks
Ask the AI to inspect Blocksy Blocks's context, installed block schemas, and the draft's mixed block tree.
Read the draft before making changes. Keep its latest content version and block positions so edits do not overwrite newer work.
Step 04
Choose an existing reusable block
Find an existing published Companion Pro Content Block and inspect its intended content.
Create and publish reusable documents through the Companion workflow. This lesson starts with one that already exists.
Step 05
Insert its native embed
Add the supported Blocksy embed to the draft and preserve its saved placeholder markup.
The frontend renders the referenced document, but Gutenberg still needs the native saved placeholder. Replacing it with arbitrary HTML can break editing.
Step 06
Check the native editor
Read the saved blocks and open Gutenberg. Check for invalid-content warnings, then inspect desktop and phone previews.
A working frontend does not prove the blocks remain editable. Check the native editor, spacing, links, and images before publishing. Saves on published pages can take effect immediately.
You’re done when…
The Blocksy Blocks section is editable in Gutenberg, has no invalid-block warnings, and displays correctly.
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.