What this covers
General Workflow
These updates follow an extended version of the standard workflow:- Start a content update task in Gradial
- Define the scope (single component, multiple components, or fragment)
- Provide source material or instructions
- Generate revised content
- Review and refine across all affected areas
- Run QA and validation checks
- Apply updates in the CMS
Update Type: Component Swaps
Purpose
Replace an existing component with a different component type while preserving content intent and page structure.Common Scenarios
- Swapping a basic text component for a text-with-image component
- Replacing a static banner with an interactive carousel
- Upgrading a legacy component to a newer version
- Changing a CTA style (e.g., button to card)
How It Works
- Select the target page and component to be replaced
- Specify the new component type to use
- Provide mapping guidance for how existing content should transfer
- Gradial generates the new component with migrated content
- Review the swap to ensure content and layout integrity
- Apply the change via Launch or direct authoring
Considerations
- Field mappings between old and new components may require manual guidance
- Some content may not have a direct equivalent in the new component
- Visual review is recommended to catch layout shifts
Update Type: Multiple Discrete Changes (Batched Updates)
Purpose
Execute several unrelated updates across a page or site within a single ticket, improving efficiency for routine maintenance.Common Scenarios
- Quarterly compliance updates affecting multiple sections
- Campaign refreshes touching headlines, CTAs, and images
- Post-launch fixes addressing several small issues at once
How It Works
- Create a single task with multiple update instructions
- List each change clearly, specifying:
- Target page and component for each
- The specific update required
- Gradial processes each change independently
- Review all changes in a consolidated view
- Apply updates together or selectively
Best Practices
- Number or bullet each discrete change for clarity
- Group changes by page when possible
- Indicate priority if some changes are more urgent
Update Type: Find-and-Replace Edits
Purpose
Make consistent text changes across multiple components or pages in bulk.Common Scenarios
- Rebranding (company name, product names, taglines)
- Legal or compliance updates (disclaimer text, terms)
- Date or year updates (© 2024 → © 2025)
- Terminology standardization
How It Works
- Define the search term (exact text or pattern)
- Define the replacement text
- Set the scope (single page, section, or site-wide)
- Gradial identifies all instances and generates replacements
- Review the change list before applying
- Apply changes in bulk or selectively
Considerations
- Review matches carefully—context matters
- Some instances may require different handling
- Preserve formatting and links in replaced text
Update Type: Structured Content Items
Purpose
Create or update reusable, structured content blocks — Content Fragments in AEM, datasource items in Sitecore, entries in Contentful, and the equivalent in each other connected CMS. See Working with Fragments for how these map across platforms.Create a Content Fragment
- Specify the fragment model to use
- Provide the content for each field in the model
- Gradial generates the fragment according to the schema
- Review field mappings and content accuracy
- Create the fragment in your CMS
Update a Content Fragment
- Select the existing fragment to modify
- Provide update instructions for specific fields
- Gradial generates revised content for the targeted fields
- Review changes against the original
- Apply the update to the fragment
Key Benefits
- Fragment updates propagate everywhere the fragment is used
- Structured content ensures consistency
- Changes are versioned and auditable
Update Type: Layout-Based Blocks
Purpose
Update reusable page sections that bundle layout and components together — Experience Fragments in AEM, Partial Designs in Sitecore, Content Blocks in SFMC, and the equivalent in each other connected CMS. See Working with Fragments for how these map across platforms.Common Scenarios
- Updating shared headers or footers
- Modifying promotional banners used across pages
- Refreshing navigation elements
How It Works
- Select the experience fragment to update
- Identify the component(s) within the fragment to modify
- Provide update instructions
- Gradial generates the revised fragment content
- Review the changes in context
- Apply the update to the experience fragment
Considerations
- Changes affect all pages using the fragment
- Coordinate with stakeholders before updating shared elements
- Test across multiple page contexts
Update Type: Create a Version of a Page
Purpose
Generate a new version of an existing page—useful for A/B testing, seasonal variations, or campaign-specific messaging.Common Scenarios
- Creating a holiday version of a landing page
- Building an A/B test variant
- Developing a region-specific version
- Archiving current state before major updates
How It Works
- Select the source page to version
- Specify what should change in the new version
- Gradial generates the new page version with modifications
- Review the new version against the original
- Save as a new page or Launch branch
Best Practices
- Use clear naming conventions for versions
- Document the purpose of each version
- Set expiration or review dates for temporary versions
Update Type: Document-Driven Updates
Purpose
Update page content using an external source document—Word doc, PowerPoint, or PDF—as the input.Update Page from Copy Doc (Word)
Best for: Text-heavy updates with structured content- Upload the Word document containing approved copy
- Map document sections to page components
- Gradial extracts and applies content to the appropriate fields
- Review the mapping and generated content
- Apply updates to the page
Update Page from PowerPoint
Best for: Campaign or creative briefs with visual layout context- Upload the PowerPoint file
- Indicate which slides correspond to which page sections
- Gradial interprets slide content and maps to components
- Review extracted content and adjust as needed
- Apply updates to the page
Update Page from PDF
Best for: Approved final documents, legal content, or archived materials- Upload the PDF
- Identify the relevant sections for extraction
- Gradial extracts text and structure from the PDF
- Review and refine the extracted content
- Apply updates to the page
Tips for Document-Driven Updates
- Use clean, well-structured source documents
- Annotate or highlight sections that map to specific components
- Provide supplementary instructions for ambiguous areas
- PDFs with complex layouts may require additional guidance
Ticketing Integration for Medium Updates
Medium updates work well with ticketing integrations, though they may require:- Richer ticket descriptions with detailed instructions
- Attached source documents (for document-driven updates)
- Defined scope (pages, components, or fragments affected)
- Stakeholder review steps before final application
Key Takeaways
- Medium updates involve more scope or complexity than simple copy changes
- Multiple components, fragments, or pages may be affected
- Source documents can drive updates directly
- Human review remains essential given the broader impact
- Versioning and governance are preserved throughout
When to use this
- Component modernization or upgrades
- Batch maintenance across multiple page areas
- Rebranding or terminology standardization
- Fragment management (content and experience)
- Campaign versioning and A/B testing
- Processing approved documents into web content