Access: Must be enabled for your organization. Contact your Gradial team to get access.
What ACI provides
Structured, versioned content
Pages, shared fragments, site configuration, and personalization overlays use a consistent file-based model with a reviewable history.
A contract with your frontend
Component and layout contracts define which content your site accepts. ACI validates content against those contracts before release.
Safe review workflows
Branches isolate work in progress. Each branch can be previewed with its linked code before changes are approved.
Controlled delivery
Approved changes are promoted deliberately, staged as a release, and activated as one consistent site version.
How ACI fits into your stack
Your frontend remains in your repository and continues to use your design system. ACI connects content to that code through a small project configuration and typed component and layout contracts. Current starter projects support:- Astro for the standard ACI site setup
- Next.js when your site needs the Next.js ecosystem or ACI’s supported server-rendered delivery mode
One workflow, regardless of where work starts
A change may begin with a content team in Gradial, a developer editing project files, or a compatible coding agent. The path to live stays the same:- Make the change on an isolated branch.
- Validate it against the site’s contracts.
- Preview the branch with the intended code build.
- Land approved work on
main. - Promote selected content to
live. - Stage and activate a release.
ACI and the Gradial platform
ACI provides content structure, validation, preview, personalization, and delivery. Gradial is the marketing execution platform that works through those capabilities to help your team plan and complete content operations. The same content model and validation rules apply whether a person, Gradial, or developer tooling makes the change. That keeps governance attached to the work instead of the interface used to create it.Next: Why Gradial ACI →