A brief becomes a real page.Change theme settings with your AI
Inspect the active theme and follow the matching Astra, Kadence, GeneratePress, or Blocksy route.
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
- A verified connection to a practice site.
- Permission to manage theme settings.
- The matching active theme; GeneratePress and Blocksy workflows require EMCP Pro.
Let’s do this, step by step.
Step 01
Check the integration tools
Open Setup → Tools → Themes. Find the active theme; Blocksy Companion features are on Plugins. Inspect dependencies and both read/write switches. Enable the actions for this task, choose Save changes, then reconnect.
Before starting, find this integration on the Tools screen. Check the required plugin and action switches. Save the changes and reconnect your app. Find the active theme; Blocksy Companion features are on Plugins.
Step 02
Identify the active theme
Read theme context, parent theme, and supported settings. Take a before screenshot on a practice site.
Theme settings can affect the whole website. Identify the theme before asking for a change, and use only the settings its integration reports.
Step 03
Astra: inspect then update
For Astra, read the colors, typography, layout, or header-footer group. Change one supported value and inspect skipped fields.
On an Astra site, start with one small change, such as content width. The integration refreshes Astra's dynamic styles after saving. Check more than one page.
Step 04
Kadence: preserve palette references
For Kadence, read the global palette and the returned setting shapes before updating a supported color, font, button, or width.
Kadence settings may point to palette slots rather than a color value. Preserve the complete setting shape the integration returns.
Step 05
GeneratePress: use its own controls
For GeneratePress, read its palette and supported layout settings. Apply one reviewed value using the returned format.
GeneratePress has a separate set of controls. A color can reference a palette variable, so read that palette before replacing anything.
Step 06
Blocksy: stay within supported widths
For Blocksy, inspect design settings and change only a supported width using the current settings version.
The documented writable controls cover site and content widths. Complex header, footer, palette, and typography settings are available for inspection, not arbitrary editing here.
Step 07
Blocksy Companion: keep features separate
If using Companion, inspect extensions before toggling one. Create Content Blocks as disabled drafts and review conditions in native controls.
Extensions, reusable Content Blocks, and Gutenberg embeds are separate tasks. Publishing a disabled Content Block does not automatically enable it.
Step 08
Check the result and recovery
Review representative pages at desktop and mobile widths. Restore the previous setting if the change is unsuitable.
Complete only the route matching your active theme. Do not switch themes to follow every chapter. Child-theme creation is an advanced operation that also changes the active theme.
You’re done when…
The chosen setting is verified across pages, with the prior value recorded.
Keep the reference handy.
The docs cover tool details and requirements for this lesson.