Agent Canvas for WordPress
A native WordPress canvas for people and assisted editing
Start with an independent Gutenberg block theme whose templates, patterns, style variations, and stable design tokens remain editable in the Site Editor and understandable to compatible tools.
Theme boundary
Presentation, not runtime
Canvas owns visual tokens, templates, template parts, core-block patterns, and rendering. It does not run an AI model or store workflow policy.
Plugin independence
Canvas works without Composer, Starter, or any WP Suite plugin.
Why Canvas
Keep the editing surface native while making presentation predictable
Canvas gives editors a complete block-theme foundation and gives compatible tools stable, read-only presentation roles without adding a proprietary content runtime.
01
Native WordPress editing
Customize templates, navigation, styles, and patterns in Appearance → Editor with core Gutenberg blocks and normal block-theme files.
02
Stable design tokens
Semantic color, type, spacing, radius, shadow, and gradient roles stay consistent across the default design and compatible style variations.
03
Reusable page structures
A broad library of templates, template parts, and core-block patterns covers common pages, sections, navigation, and editorial layouts.
04
Portable content
Canvas patterns avoid custom content blocks and shortcodes, so authored content remains readable after a theme switch even when Canvas presentation is no longer applied.
Theme capabilities
A presentation system built for human and tool-assisted workflows
Token-compatible style variations
The included visual styles reuse the same semantic token slugs, so changing the site’s look does not rewrite authored content.
Accessible interaction foundations
Visible keyboard focus, reduced-motion handling, responsive layouts, RTL compatibility, editor parity, and core Details patterns form the baseline.
Read-only discovery manifest
A schema-validated manifest maps semantic components and editable slots for compatible tools without adding prompts, credentials, callbacks, or executable policy.
No hidden application layer
Canvas adds no frontend theme JavaScript, remote fonts, telemetry, tracking, demo importer, custom block, shortcode, content type, role, or automatic plugin installation.
Responsibilities
Canvas renders the site; optional companion products govern other jobs
The theme remains useful on its own. Add Starter for curated initial content or Composer for governed draft execution only when the project needs those separate capabilities.
WORDPRESS SITE EDITOR
templates + navigation + styles
│
▼
AGENT CANVAS
tokens + patterns + template parts
│
├── OPTIONAL STARTER
│ initial content + recipes
│
└── OPTIONAL COMPOSER
discovery + contracts + drafts
Canvas owns presentation and theme rendering. Starter owns portable initial content and recipes. Composer owns configuration, validation, audit, and agent-owned drafts. Provider plugins own their blocks, actions, services, and business logic.
Evaluation questions
What teams usually need to know
Does Agent Canvas require Composer or another AI plugin?
No. Canvas is a complete WordPress block theme on its own. Composer integration is optional and uses a static, read-only presentation manifest as discovery input.
Does Canvas send site data to an external service?
No. The theme makes no external API request, loads no remote font or frontend script, and includes no telemetry or tracking.
Will Canvas import demo pages automatically?
No. Pattern insertion and Site Editor changes are initiated by the user. Starter is the separate product responsible for optional curated initial content and recipes.
What happens if the site switches themes?
Content built from core blocks remains readable. Canvas-specific wrapper classes can lose their Canvas styling, but the content is not locked into a proprietary block or shortcode.
Use the native foundation
Build the visual system in WordPress, then add workflow layers deliberately
Install Canvas as the theme, customize it in the Site Editor, and introduce Starter, Composer, or provider plugins only for the separate responsibilities the site actually needs.