Agent Composer: keep WordPress as the CMS for the AI-built web

The missing layer

Generating the frontend is only the first delivery

Prompt-to-site and Figma-to-code tools can turn a design into a working frontend remarkably quickly. That is useful, and for some projects it is exactly the right approach. But it mainly optimizes the first generation step. The result is often an application or a set of frontend components, while the long-term content model, editorial workflow and rules for future changes remain a separate problem.

A production website is changed far more often than it is created. Editors add campaigns, landing pages and knowledge content. Agencies introduce new content types and reusable components. Plugins evolve. Brand and accessibility rules must still apply six months later. If every change starts as another code-generation task, the organization may gain a fast frontend but lose the CMS as the shared, understandable source of truth.

• What content types, fields and relationships already exist?
• Which design patterns and real plugin components may the agent use?
• Which parts may it change, and what must a human approve?

Agent Composer addresses this second problem: not how to generate one attractive page, but how to let AI participate in the continued evolution of a real WordPress site without turning every update into an unrestricted coding exercise.

Controlled execution

Agent Composer governs change instead of generating an isolated page

Agent Composer is an execution and validation layer for AI-assisted WordPress work. The site declares its contract first: approved page blueprints, reusable patterns, allowed blocks, design rules, metadata requirements, content structures and writable boundaries. An agent works inside that declared environment instead of guessing how the site was built.

For each task, Agent Composer exposes only the capabilities allowed by the selected blueprint and the active Site Contract. It assembles the requested patterns, checks the resulting block tree and validates structural requirements before WordPress saves anything. A blog post can require one H1, a specific template, approved editorial sections and SEO metadata. A product page can use a different visual family and component set. The rules travel with the site rather than depending on the agent remembering a long prompt.

• Agents create editable, Agent Composer-owned drafts; they do not publish autonomously.
• Published content is outside the write boundary, and adopting an existing draft requires an explicit operation.
• Validation covers the complete block structure, not only the text returned by the model.

The current implementation also discovers registered product capabilities through the WordPress Abilities API. Gatey, AI-Kit and Flow already expose their own component schemas, materializers and validators. Agent Composer can therefore request a real supported component with validated settings instead of recreating an approximation in Custom HTML.

A different production model

WordPress can stay private while the public site scales independently

Keeping WordPress as the CMS does not mean that the public website must be served directly by the WordPress runtime. In a WP Suite architecture, WordPress can remain the editorial control plane: the place where structured content, Gutenberg layouts, revisions and publishing decisions live. The installation itself can stay behind a VPN or firewall rather than becoming the public production surface.

An authenticated connector tunnel can give an authorized AI client a narrow route to Agent Composer without exposing wp-admin or the whole WordPress server to the internet. Agent Composer still applies the Site Contract, blueprint and draft-only write boundary after the connection is established. The tunnel solves reachability; Agent Composer decides what the agent is actually allowed to do.

• Static Publisher can export the approved WordPress result for delivery from Amazon S3 and CloudFront.
• Static Site Guardian can add protected delivery where the exported site must not be public.
• Identity, APIs, AI and workflow services can run in customer-owned AWS infrastructure and scale independently of the WordPress authoring server.

This separates three concerns that are too often bundled together: WordPress remains the editable source, Agent Composer governs AI-assisted change, and AWS handles the public runtime where appropriate. Traffic growth no longer has to translate into more load on the editorial WordPress installation.

The architecture in one view

One website, three clear responsibilities

The supporting layers

Agent Composer is the center; Canvas and Starter make it reusable

Agent Composer does not require every website to look the same. Its role is to execute the contract defined for the current site. SmartCloud Agent Canvas is the reference block-theme layer that can provide a coherent design system, semantic patterns and layout rules which Agent Composer understands. It demonstrates how a theme can be designed for both human editing and governed agent execution.

SmartCloud Agent Starter is being prepared as a reusable commercial foundation for agencies. It can package site variants, design presets, optional plugins, blueprints, patterns and an initial Site Contract. A site-specific configuration candidate can then adapt that foundation to the actual project and be reviewed before adoption.

• Agent Composer executes and validates the approved site contract.
• Canvas provides an agent-readable design and structural foundation.
• Starter reduces the work needed to establish that foundation for a new project.

The distinction matters. Canvas and Starter make projects easier to begin, but Agent Composer is what keeps later AI-assisted changes controlled, native to WordPress and reviewable. The lasting product is not the first generated page. It is the governed ability to change the site again.

Agency value

The agency can deliver a system for future change

Agencies are increasingly compared with tools that can generate the first version of a website in minutes. Competing only on the speed of that first build is a narrowing position. Agent Composer creates a different proposition: deliver a WordPress site that the client can continue to expand with AI assistance, while the agency defines the design system, content model, approved capabilities and review boundaries.

A client can request a new article or landing page through a connected agent and receive a valid WordPress draft built from the site’s real patterns. The result stays editable. The agency does not need to repair a fresh collection of generated markup after every request, and the client does not need unrestricted administrative access for the agent.

• Faster client content work within boundaries defined by the agency.
• Fewer design and structural regressions than unconstrained page generation.
• An ongoing role for architecture, governance, component development and support.

This is not autonomous publishing, and it is not a claim that every frontend should be generated from WordPress. It is a practical third option: keep the CMS, make it agent-ready, and decouple public delivery when security or scale requires it.