Small Content Updates in Gradial

​

What Qualifies as a Small Content Update?

---

​

Fast Lane: Ticketing Integrations

​

The Business User Advantage

Small content updates are ideal candidates for ticketing system integrations, giving business users a streamlined path to request and execute simple changes without leaving their system of record.

​

How It Works

1. Create a ticket in your existing system (e.g., Jira, ServiceNow, Workfront)
2. Assign the ticket directly to Gradial using the integration
3. Gradial automatically interprets the request and generates the update
4. The change flows through standard review and approval workflows
5. Once approved, the update is applied to the CMS

​

Why This Matters

​

Best Fit for Ticketing Workflows

• Routine copy corrections (typos, outdated dates, legal disclaimers)
• Link updates and fixes
• High-volume, repetitive changes across multiple pages
• Time-sensitive updates that can’t wait for a full content cycle

​

Integration Requirements

Work with your Gradial administrator to configure:

• Ticket assignment rules (which ticket types route to Gradial)
• Field mappings (how ticket details translate to update instructions)
• Approval workflows (who reviews before CMS application)

---

​

General Workflow

All small content updates follow the same core workflow:

1. Start a content update task in Gradial
2. Select the page and component to modify
3. Provide update instructions
4. Generate revised content
5. Review and refine the proposed changes
6. Run QA and validation checks
7. Apply the update in the CMS

---

​

Update Type: Copy Changes

​

Purpose

Modify on-page text content—such as headlines, body copy, or CTA text—while preserving governance, review, and CMS versioning.

​

Step-by-Step Walkthrough

​

1. Start a Content Update Task

• Create a new task in Gradial
• Select Update Existing Content as the task type

Outcome: Gradial understands this is an edit, not new content creation.

​

2. Select the Page and Component

• Identify the target page where the update is needed
• Select the specific component (headline, paragraph, CTA, etc.)

Outcome: Gradial scopes the change precisely, avoiding unintended edits elsewhere on the page.

​

3. Provide Update Instructions

Provide guidance for the update, such as:

• Revised copy
• Directional feedback (tone, clarity, compliance-driven changes)
• References to approved language or source material

Outcome: Gradial has clear instructions for how the content should change.

​

4. Generate the Revised Content

Gradial proposes an updated version based on your instructions while maintaining alignment with:

• Existing page structure
• Component field constraints
• Brand and content rules

Outcome: A draft update is generated without manual CMS editing.

​

5. Review and Refinement

• Review the proposed update directly in Gradial
• Make adjustments before anything is applied to the CMS

Outcome: Human review ensures the update is accurate, intentional, and approved.

​

6. QA and Validation

Gradial runs automated checks, which may include:

• Required field validation
• Accessibility considerations (e.g., heading structure)
• Content formatting and length constraints

Outcome: Errors or issues are caught early, reducing rework.

​

7. Apply the Update in the CMS

Once approved, apply the change:

• Via a Launch: Creates a safe, isolated branch of the page
• Via direct authoring: Depending on workspace rules

Outcome: The updated content is ready for final review and publication.

---

​

Update Type: Screenshot-Guided Edits

​

Purpose

Use an annotated screenshot to visually communicate what needs to change, reducing ambiguity in update instructions.

​

How It Works

1. Capture a screenshot of the page or component
2. Annotate the image to highlight the specific area and describe the change
3. Upload the screenshot when creating your update task
4. Gradial interprets the visual context alongside any written instructions

​

Best Practices

• Circle or highlight the exact element to change
• Add text callouts describing the desired update
• Include both the screenshot and written instructions for clarity

---

​

Update Type: Hyperlink Updates

​

Purpose

Change link destinations or link text without editing the CMS directly.

​

Common Scenarios

• Updating a URL that has changed
• Fixing broken links
• Changing link text for clarity or compliance
• Redirecting CTAs to new landing pages

​

Instructions to Provide

• The current link text and/or URL
• The new link text and/or URL
• Any context (e.g., “This link should now point to the 2024 annual report”)

---

​

Update Type: Styling Adjustments

​

Purpose

Modify component-level styling options that are exposed in the AEM authoring interface.

​

Scope

This applies only to styles defined within the AEM component configuration, such as:

• Color variants
• Layout options
• Size or spacing presets
• Theme selections

​

Note

Styling changes outside of component-defined options require development work and are not covered by this workflow.

---

​

Key Takeaways

• Updates are scoped to a specific component, not the entire page
• Manual CMS editing is avoided
• Human-in-the-loop governance is preserved throughout
• Versioning, review, and rollback capabilities remain unchanged

---

​

When to Use Small Content Updates

• Frequent copy tweaks (headlines, CTAs, descriptions)
• Compliance- or legal-driven wording changes
• High-volume updates across similar pages
• Situations where speed matters but control is required
• Link maintenance and updates
• Minor styling adjustments within component options