Blocksy theme and Companion

In EMCP 3.17.0, Blocksy tools are separated by ownership. Theme configuration stays in Themes, Companion features live in Plugins, and Blocksy Blocks has an independent Gutenberg integration.

Requires EMCP Pro and the relevant native products. Verified with Blocksy and Companion Pro 2.1.57.

Theme layout and design

emcp-tools/blocksy-theme-read and emcp-tools/blocksy-theme-write expose context, design discovery and curated updates. Writable layout keys are maxSiteWidth, narrowContainerWidth and wideOffset, using native ranges. Palette, typography, responsive spacing and header/footer configuration can be inspected; complex placement graphs are read-only. Writes clear native settings caches before refreshing CSS.

Read the current schema and hash first. Theme changes affect site-wide output, so inspect more than the page that prompted the request.

Companion extensions

emcp-tools/blocksy-extensions-read supports list-extensions, returning descriptions, Pro flags and activation state. The write dispatcher supports activate-extension and deactivate-extension by slug, enforcing native manager permissions.

This manages activation, not arbitrary extension configuration. Premium extensions still require the vendor license.

Companion Pro Content Blocks

emcp-tools/blocksy-content-read and emcp-tools/blocksy-content-write cover context, available types, document listing and reading, native hooks, draft creation/editing and explicit publish/unpublish operations. Omit operation to discover the current dispatcher catalog; inspect schemas before writing.

Types include hook, header, footer, single, archive, 404, nothing_found, popup and maintenance. Creation produces a disabled draft with no conditions. Updates preserve unknown native settings, require a current hash and refuse published documents.

Publication does not silently enable a disabled block. Unpublish before draft-only edits. Ordinary Gutenberg tools keep their normal immediate-save behavior; they do not provide the same isolation as template tools.

Use native controls for advanced conditions, popup configuration and code-mode documents. Font/account configuration, white-label changes, remote starter-site imports and code execution are outside this integration.

Embed a reusable document

Use Blocksy Blocks to insert an existing Content Block. Preserve its saved placeholder markup even though PHP renders it dynamically. Open the page in Gutenberg to check for validation warnings.

Permissions and verification

Theme operations require theme-management access. Extension toggles enforce site and native manager capabilities. Content Blocks use native post-type permissions and current-state checks. New writes start disabled.

Live checks covered width updates, cache refresh, stale writes, draft publication and a reusable embed. Desktop output and Gutenberg validation passed; a separate mobile visual pass remains outstanding for the recorded fixture.

See the Blocksy overview and builder setup guide.