| Work type | Request example |
|---|---|
| Single page | Create a landing page for the spring webinar on the events site, with our standard hero and a registration block. |
| Small multi-page build | Create a three-page microsite for the product launch: overview, specifications, and contact. |
| New component | Add a testimonial component to the campaign site and place it on the home page below the hero. |
| Structural change | Add a case-study content type with fields for client, sector, and outcome, and add it to the main navigation. |
| Content update | Update the pricing page to match the copy in the attached document. |
To delegate site tasks:
Open Acquia AI and set the mode toggle to Work mode
Add required context groups, such as brand guidelines, approved copy, or component inventories
Name the site, describe the intended outcome, and state applicable constraints, including the content type, navigation placement, and existing pattern to follow
Submit the request and answer clarifying questions from the agent
Review the plan proposed by the agent, then approve, request changes, or reject the plan
Review the generated draft and approve publication when the result is correct
Reference existing patterns: Specify references such as such as the summer campaign page to provide context rather than relying solely on layout descriptions
Specify the site name directly: Name the target site directly to avoid ambiguous matches among assigned sites
Define static elements: State elements that must not change, such as existing navigation items, locked templates, or published URLs
Start with small requests: Submit a single page for initial approval to learn agent output patterns before you request a microsite
To review a draft before publication approval:
Compare the draft against the specified pattern
Verify navigation placement and page URLs
Run a governance check on the new page before publication
Acquia AI operates with Acquia Source CMS sites only
The agent processes one site per task without multi-site capabilities, which prevents single-task changes across site sets
The agent does not modify application code
For additional details, visit Governance and control management
If this content did not answer your questions, try searching or contacting our support team for further assistance.
If this content did not answer your questions, try searching or contacting our support team for further assistance.