> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gradial.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Content Updates

> Update existing pages and experiences across your connected systems using Gradial's AI agents.

Enterprise content teams are stuck in a cycle that doesn't scale. Every page update — a headline change, a link fix, a campaign refresh — means opening a ticket, waiting on a developer or web producer, manually entering content field by field in AEM or Sitecore, running QA, and submitting for approval. For a 50-page campaign launch, this can take weeks. When messaging or branding changes globally, coordinating updates across hundreds of pages is practically a project in itself.

Gradial's AI agents operate directly inside your CMS — authoring, updating, and staging content based on your instructions — so content teams can execute at the speed the business demands without burning out web producers or opening engineering tickets for routine changes.

***

## Who this is for

<CardGroup cols={3}>
  <Card title="Content Authors & Editors" icon="pen-to-square">
    Tired of repetitive field-by-field entry. Need to push updates faster without waiting on dev queues.
  </Card>

  <Card title="Web Producers" icon="display">
    Managing high volumes of page QA, publishing workflows, and manual CMS work daily. The most time-constrained people in the content supply chain.
  </Card>

  <Card title="Digital Marketing Managers" icon="bullhorn">
    Measured on campaign launch speed and on-time delivery. Blocked by the gap between brief approval and live page.
  </Card>
</CardGroup>

***

## What Is a Content Update?

A content update is any task where Gradial reads, modifies, and stages content in a connected system based on your instructions. This includes:

* Editing copy, headlines, or body text
* Swapping or updating images and media
* Modifying links, CTAs, or metadata
* Updating reusable content blocks (fragments, experience fragments)
* Replacing or reordering components on a page
* Bulk changes applied across many pages at once
* Site-wide audits, find-and-replace, and analytics property updates

You can initiate updates directly in Gradial, through the AI assistant, or via your existing ticketing system (Jira, Workfront, Wrike, Azure DevOps). Gradial never writes directly to production — all changes are staged for review first.

***

## Update Complexity

<CardGroup cols={3}>
  <Card title="Small Updates" icon="circle-small" href="/docs/updating-existing-experiences-i-e-content-updates/small-content-updates">
    Single-item changes with a clear, bounded scope — copy edits, link fixes, image swaps, styling adjustments. No cross-page impact.

    **Examples:** Headline change, CTA swap, typo fix, image replacement.
  </Card>

  <Card title="Medium Updates" icon="circle-half-stroke" href="/docs/updating-existing-experiences-i-e-content-updates/medium-content-updates-in-gradial">
    Changes spanning multiple components, touching reusable content, or driven by source documents. Higher risk because a change in one place may surface in others.

    **Examples:** Fragment updates, component swaps, document-driven updates, batched changes across sections.
  </Card>

  <Card title="Complex Updates" icon="circle" href="/docs/updating-existing-experiences-i-e-content-updates/complex-content-updates">
    Multi-page and site-wide operations requiring sequencing, pattern-matching, or systematic auditing across large content sets.

    **Examples:** Find-and-replace across a site, bulk page property updates, SEO/analytics audits, coordinated campaign launches.
  </Card>
</CardGroup>

***

*For creating net-new pages, see [New Page Workflow](/docs/creating-new-experiences/new-page). For platform connection setup, see [Integrations](/docs/integrations-administration-and-setup/integrations/get-started-with-integrations).*