> ## 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.

# Customer Use Cases

> Ideas and examples for what to ask Grady, organized by where you are in the marketing lifecycle.

## What can I ask Grady?

A lot. The examples below are organized around the marketing lifecycle — from setting strategy through to analyzing results. The goal is to spark ideas based on where you are right now, not to prescribe a fixed workflow.

You don't need to use these word-for-word. Describe what you need in plain language and Grady will work out the steps. These are starting points.

<Info>
  Where your environment has specific paths configured (e.g., a known AEM content root or DAM path), substitute your actual paths in place of the generic placeholders shown here.
</Info>

***

<CardGroup cols={3}>
  <Card title="01 — Strategy" icon="chess" href="#strategy">
    Campaign goals, messaging frameworks, market planning
  </Card>

  <Card title="02 — Planning" icon="list-check" href="#planning">
    Briefs, task breakdowns, timelines, localization scope
  </Card>

  <Card title="03 — Creative" icon="pen-nib" href="#creative">
    Copy generation, image creation, smart cropping
  </Card>

  <Card title="04 — Assets (DAM)" icon="images" href="#assets-dam">
    Tagging, metadata, brand compliance, asset organization
  </Card>

  <Card title="05 — Channel Orchestration" icon="envelope" href="#channel-orchestration">
    Email campaigns, journeys, newsletters, multi-channel publishing
  </Card>

  <Card title="06 — Authoring" icon="pencil" href="#authoring">
    Page updates, new pages, fragments, bulk edits
  </Card>

  <Card title="07 — Review & QA" icon="circle-check" href="#review--qa">
    QA checks, accessibility, brand audits, compliance
  </Card>

  <Card title="08 — Launch" icon="rocket" href="#launch">
    Publishing, bulk rollouts, find-and-replace, scheduled sends
  </Card>

  <Card title="09 — Analyze & Optimize" icon="chart-line" href="#analyze--optimize">
    Performance reporting, SEO, GEO, A/B testing, CX
  </Card>
</CardGroup>

***

<Tabs>
  <Tab title="01 Strategy">
    Setting direction — what to build, who to target, and how to position it. Grady can help you turn raw thinking into structured campaign plans and messaging frameworks.

    <AccordionGroup>
      <Accordion title="1.01 — Plan a product launch campaign across web, email, and social">
        **Complexity:** Complex | **Scope:** Multi-platform | **Platform:** All

        Build a full campaign plan with a timeline, asset list, and task breakdown — ready to execute or hand off to the team.

        **Sample Prompt**

        ```
        Plan a launch campaign for [product name] across web, email, and social. Target launch date: [date]. Include: a messaging framework, channel-by-channel asset list, go-live timeline, and a task breakdown I can execute in Gradial.
        ```
      </Accordion>

      <Accordion title="1.02 — Build a Q3 content calendar across all channels">
        **Complexity:** Complex | **Scope:** Multi-platform | **Platform:** All

        Generate a structured content calendar for the quarter, mapped to campaigns, channels, and owners.

        **Sample Prompt**

        ```
        Build a Q3 content calendar for [team / brand]. Include web pages, emails, and social posts mapped to our campaign themes: [theme 1], [theme 2], [theme 3]. Align to key dates: [list of dates or events]. Format it so I can use it to kick off tasks in Gradial.
        ```
      </Accordion>

      <Accordion title="1.03 — Take last year's best-performing campaign and adapt it for this year">
        **Complexity:** Complex | **Scope:** Multi-platform | **Platform:** All

        Use a proven campaign as the foundation — updating messaging, assets, and dates for the new cycle without rebuilding from scratch.

        **Sample Prompt**

        ```
        Take our [campaign name] campaign from [year] and adapt it for [this year / new product / new market]. Update the messaging for [new context], refresh the assets, and rebuild the task list. Reference the original brief here: [link or attached file].
        ```
      </Accordion>

      <Accordion title="1.04 — Draft the messaging framework for a product launch">
        **Complexity:** Medium | **Scope:** Single deliverable | **Platform:** All

        Turn a product brief into a structured messaging framework — positioning statement, key messages by audience, and proof points.

        **Sample Prompt**

        ```
        Draft a messaging framework for the launch of [product name]. Include: a one-sentence positioning statement, three key messages for each of these audiences: [audience 1], [audience 2], [audience 3], and two proof points per message. Reference the attached product brief.
        ```
      </Accordion>

      <Accordion title="1.05 — What would it take to launch this campaign in 5 new markets?">
        **Complexity:** Medium | **Scope:** Multi-market | **Platform:** All

        Scope out what localization, asset adaptation, and compliance work is needed to expand an existing campaign into new regions.

        **Sample Prompt**

        ```
        We want to launch [campaign name] in these 5 new markets: [market 1], [market 2], [market 3], [market 4], [market 5]. For each, outline what needs to be localized (copy, assets, compliance), what can be reused, and what net-new work is required.
        ```
      </Accordion>

      <Accordion title="1.06 — Build a competitive analysis and surface gaps in our positioning">
        **Complexity:** Medium | **Scope:** Research | **Platform:** All

        Research how key competitors are positioning themselves on a topic or product area, then identify where your messaging is weaker, stronger, or missing entirely.

        **Sample Prompt**

        ```
        Research how [competitor 1], [competitor 2], and [competitor 3] are positioning themselves on [topic / product category]. Compare their messaging to ours at [our page URL or attached doc]. Identify: where we're stronger, where we're weaker, and any positioning angles they're using that we're not addressing.
        ```
      </Accordion>

      <Accordion title="1.07 — Track competitor messaging changes and alert me when they reposition">
        **Complexity:** Medium | **Scope:** Ongoing monitoring | **Platform:** All

        Set up a recurring check on competitor pages so you know whenever a rival updates their positioning, pricing, or key claims.

        **Sample Prompt**

        ```
        Monitor the following competitor pages on a [weekly / monthly] basis: [URL 1], [URL 2], [URL 3]. Alert me whenever copy, pricing, or key messaging changes significantly. Summarize what changed and flag anything that affects our positioning.
        ```
      </Accordion>

      <Accordion title="1.08 — Which competitors get cited in AI answers where we're invisible?">
        **Complexity:** Medium | **Scope:** Research | **Platform:** All

        Identify the AI search queries where competitors are being cited but your brand isn't — so you know where to close the gap.

        **Sample Prompt**

        ```
        Run a set of AI search queries for [topic / product category] on [ChatGPT / Perplexity / Google AI Overviews]. For each query, note which competitors are cited and whether we appear. Identify the 5 queries where we're most absent and competitors are most present, and recommend what content changes would improve our visibility.
        ```
      </Accordion>

      <Accordion title="1.09 — Summarize what our best-performing content has in common">
        **Complexity:** Medium | **Scope:** Research | **Platform:** All

        Look across your top-performing pages and identify patterns in topic, format, length, and structure — so you can replicate what works.

        **Sample Prompt**

        ```
        Analyze our top [N] performing pages by [metric: organic traffic / conversions / engagement] over the last [time period]. Identify what they have in common: topic type, content length, heading structure, use of visuals, and CTAs. Summarize the patterns and recommend how to apply them to new content.
        ```
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="02 Planning">
    Breaking strategy into executable work — briefs, task lists, timelines, and scoping. This includes working with your connected ticketing systems (Jira, Workfront, Wrike, Azure DevOps) to query what's in flight, intake new requests, and turn planning decisions into tracked work.

    <AccordionGroup>
      <Accordion title="2.01 — Execute this campaign brief end-to-end">
        **Complexity:** Complex | **Scope:** Multi-platform | **Platform:** All

        Upload a campaign brief and have Grady decompose and execute it across channels — web, email, and assets — following your configured Campaign Execution Guidance.

        **Sample Prompt**

        ```
        Run this campaign end-to-end per the attached brief and workflow diagram, following the Campaign Execution Guidance.
        ```
      </Accordion>

      <Accordion title="2.02 — Re-plan this campaign now that the launch date moved">
        **Complexity:** Medium | **Scope:** Multi-platform | **Platform:** All

        Adjust an in-flight campaign plan when the timeline shifts — re-sequencing tasks, updating deadlines, and flagging what needs to change.

        **Sample Prompt**

        ```
        Our campaign launch date has moved from [original date] to [new date]. Review the current plan and re-sequence all tasks, asset deadlines, and go-live dates accordingly. Flag anything that can no longer be completed in time.
        ```
      </Accordion>

      <Accordion title="2.03 — Turn a creative concept into a multi-channel campaign brief and task list">
        **Complexity:** Complex | **Scope:** Multi-platform | **Platform:** All

        Take a high-level creative idea and flesh it out into an actionable brief with channel assignments, dependencies, and a task breakdown.

        **Sample Prompt**

        ```
        Turn this creative concept into a full campaign brief: [describe concept]. Include: campaign goal, target audience, channel plan (web, email, social, paid), asset list, key messages, and a task breakdown I can use to kick off work in Gradial.
        ```
      </Accordion>

      <Accordion title="2.04 — Spin up 100 custom landing pages for top CRM prospects">
        **Complexity:** Complex | **Scope:** Multi-page | **Platform:** All

        Generate personalized landing pages at scale using CRM data — one per prospect, each customized with their name, company, and relevant content.

        **Sample Prompt**

        ```
        Using this page as a template: [reference page URL], create personalized landing pages for each row in the attached CSV. Substitute [first name], [company], and [use case] into the hero and body copy for each.
        ```
      </Accordion>

      <Accordion title="2.05 — Clone our site structure for a new market">
        **Complexity:** Complex | **Scope:** Multi-page | **Platform:** All

        Duplicate an existing site section into a new locale or region, then prepare it for localized content.

        **Sample Prompt**

        ```
        Clone the page structure under [source folder path] into the [target locale/region path, e.g., /content/site/en-gb/]. Carry over the templates and components, then flag which pages need content localization before they can go live.
        ```
      </Accordion>

      <Accordion title="2.06 — What's the status of every active campaign and what's blocked?">
        **Complexity:** Small | **Scope:** Ticketing | **Platform:** Jira / Workfront / Wrike

        Query your connected ticketing system for a live status summary across all in-flight campaigns — without opening the board.

        **Sample Prompt**

        ```
        In [Jira / Workfront / Wrike], give me a status summary of all active campaign tasks. Show: what's in progress, what's overdue, what's blocked and why, and what's ready for review. Group by campaign.
        ```
      </Accordion>

      <Accordion title="2.07 — Intake this stakeholder request and turn it into tracked tasks">
        **Complexity:** Medium | **Scope:** Ticketing | **Platform:** Jira / Workfront / Wrike

        Take an unstructured request — a Slack message, email, or brief — scope it, and create properly structured tickets in your connected system.

        **Sample Prompt**

        ```
        Intake this request: [paste or attach the request]. Scope it into discrete tasks, estimate complexity for each, and create tickets in [Jira / Workfront / Wrike] under [project / board name]. Assign to [team / person] and set the target date to [date].
        ```
      </Accordion>

      <Accordion title="2.08 — Automate every Jira ticket I get asking for website updates">
        **Complexity:** Complex | **Scope:** Ticketing | **Platform:** Jira

        Set up a routing rule so that web update tickets in Jira automatically trigger Gradial tasks — no manual handoff required.

        **Sample Prompt**

        ```
        Set up automation so that any Jira ticket in [project key] with label [label name] or request type [type] automatically creates a corresponding Gradial task. Map the ticket fields [summary, description, URL, assignee] to the Gradial task fields.
        ```
      </Accordion>

      <Accordion title="2.09 — Show me all tickets waiting on web content changes this sprint">
        **Complexity:** Small | **Scope:** Ticketing | **Platform:** Jira / Workfront / Wrike

        Pull a focused view of the tickets in your current sprint that are blocked on or waiting for a content or web change.

        **Sample Prompt**

        ```
        In [Jira / Workfront / Wrike], show me all tickets in the current sprint that are waiting on a web content change. Include: ticket ID, title, who owns it, how long it's been waiting, and any linked pages or assets.
        ```
      </Accordion>

      <Accordion title="2.10 — Notify me in Slack when a page is ready for my review">
        **Complexity:** Small | **Scope:** Workflow | **Platform:** All

        Wire up a notification so you're pinged automatically when Grady completes a task and the page is staged for review — no manual checking required.

        **Sample Prompt**

        ```
        When this task is complete and the page is ready for review, send me a Slack notification in [channel name] with a link to the staged page and a summary of what changed.
        ```
      </Accordion>

      <Accordion title="2.11 — Set up an approval flow so legal signs off before anything publishes">
        **Complexity:** Medium | **Scope:** Workflow | **Platform:** All

        Configure a review gate that routes completed tasks to a specific approver before they can go live — applied to a page type, folder, or tag.

        **Sample Prompt**

        ```
        Set up an approval workflow so that any task affecting pages in [folder path / tagged as compliance] requires sign-off from [legal reviewer role / person] before publishing. Route the review notification to [email / Slack channel].
        ```
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="03 Creative">
    Generating the content and imagery — copy, pages, product descriptions, hero images, and creative variants. Split into editorial and image work.

    **Editorial**

    <AccordionGroup>
      <Accordion title="3.01 — Turn a product one-pager into a full web page with FAQ and CTA">
        **Complexity:** Complex | **Scope:** Single Page | **Platform:** All

        Take a short source document and expand it into a fully structured web page — adding supporting sections, FAQs drawn from the source, and a clear call to action.

        **Sample Prompt**

        ```
        Using this attached one-pager as the source, create a full web page at [target path] using [reference page URL] as the structural template. Add an FAQ section based on the most likely customer questions from the content, and include a CTA to [desired action / URL].
        ```
      </Accordion>

      <Accordion title="3.02 — Build a new landing page for a product launch">
        **Complexity:** Complex | **Scope:** Single Page | **Platform:** All

        Generate a complete landing page — copy, structure, and imagery — for a new product or campaign, staying within brand guidelines.

        **Sample Prompt**

        ```
        Build a new landing page for [product / campaign name] at [target path]. Use this page as a structural reference: [reference URL]. Write the headline, subhead, body copy, and CTA based on these key messages: [message 1], [message 2], [message 3]. Source on-brand hero and supporting images from the DAM at [folder path] or suggest alternatives.
        ```
      </Accordion>

      <Accordion title="3.03 — Refresh older blog posts with current stats and re-publish">
        **Complexity:** Complex | **Scope:** Multi-page | **Platform:** All

        Update a set of older posts with current data, references, and on-page SEO improvements — then publish the refreshed versions.

        **Sample Prompt**

        ```
        Review all blog posts under [folder path] published in [year]. For each one: update outdated statistics with current figures, refresh any references to products or features that have since changed, and improve the meta description. Re-publish each post with today's date once updated.
        ```
      </Accordion>

      <Accordion title="3.04 — Build an FAQ section on this page from our support docs">
        **Complexity:** Medium | **Scope:** Single Page | **Platform:** All

        Generate a relevant FAQ by mining your existing support documentation, then add it to the page as a structured component.

        **Sample Prompt**

        ```
        Add an FAQ section to this page: [page URL]. Source the questions and answers from our support docs at [URL or folder path]. Select the 5–8 questions most relevant to the page topic and add them using the [FAQ component name] component.
        ```
      </Accordion>

      <Accordion title="3.05 — Create a PDP for a new SKU from a spec sheet">
        **Complexity:** Complex | **Scope:** Single Page | **Platform:** All

        Build a fully populated product detail page from a spec sheet — mapping content to the right components automatically.

        **Sample Prompt**

        ```
        Create a new product detail page for [product name / SKU] at [target path]. Use this PDP as a structural reference: [reference URL]. Populate it with content from the attached spec sheet. Use the DAM at [folder path] for product images.
        ```
      </Accordion>

      <Accordion title="3.06 — Create localized versions of this content for priority markets">
        **Complexity:** Complex | **Scope:** Multi-page | **Platform:** All

        Translate and locally adapt a page or content set for multiple markets — adjusting not just language but regional messaging, offers, and compliance.

        **Sample Prompt**

        ```
        Create localized versions of this page: [source page URL] for the following markets: [market 1 / language], [market 2 / language], [market 3 / language]. Translate the copy, adapt any region-specific pricing or offers, and ensure compliance text is included for each market. Place each at [target path structure].
        ```
      </Accordion>

      <Accordion title="3.07 — Rewrite thin-content pages to answer the query behind them">
        **Complexity:** Medium | **Scope:** Multi-page | **Platform:** All

        Identify low-quality pages that rank but deliver little value, and rewrite them with substantive, query-matching content.

        **Sample Prompt**

        ```
        Review these pages: [list of URLs]. For each one, identify the primary search query it's targeting, assess whether the current content adequately answers it, and rewrite any page that falls short. Prioritize factual depth, clear structure, and direct answers.
        ```
      </Accordion>
    </AccordionGroup>

    **Image Creation**

    <AccordionGroup>
      <Accordion title="3.08 — Generate on-brand hero images for a campaign page">
        **Complexity:** Medium | **Scope:** Single Page | **Platform:** All

        Produce AI-generated hero imagery that matches your brand guidelines and campaign brief, ready to drop into a page or store in the DAM.

        **Sample Prompt**

        ```
        Generate a hero image for this campaign page: [page URL or campaign name]. Style: [describe visual style, e.g., clean product shot on white, lifestyle photography, abstract gradient]. Brand colors: [primary / secondary]. Dimensions: [e.g., 1440×600]. Save the output to [DAM folder path].
        ```
      </Accordion>

      <Accordion title="3.09 — Smart-crop the hero image for web, mobile, and social">
        **Complexity:** Small | **Scope:** Multi-asset | **Platform:** All

        Take a single source image and produce correctly cropped variants for every breakpoint and channel — no manual editing required.

        **Sample Prompt**

        ```
        Smart-crop this image: [DAM path] for the following breakpoints and placements:
        - Desktop hero: 1440×600 (keep subject centered)
        - Mobile hero: 390×520 (keep subject in upper third)
        - Social share: 1200×630 (square-safe zone)
        - Instagram square: 1080×1080
        Save all outputs to [DAM folder path].
        ```
      </Accordion>

      <Accordion title="3.10 — Generate product lifestyle images from a brief">
        **Complexity:** Complex | **Scope:** Multi-asset | **Platform:** All

        Create a set of AI-generated lifestyle images showing the product in context — for use across PDPs, campaigns, and social.

        **Sample Prompt**

        ```
        Generate [number] lifestyle images for [product name] based on this brief: [describe scene, setting, target audience, mood]. Reference our brand style guide at [URL or attached file]. Output at [dimensions] and save to [DAM folder path]. Flag any outputs that don't meet brand standards for review.
        ```
      </Accordion>

      <Accordion title="3.11 — Create image variants from a source asset for different audiences">
        **Complexity:** Medium | **Scope:** Multi-asset | **Platform:** All

        Produce audience-specific variants of a single creative — adjusting copy overlays, color treatment, or composition to suit each segment.

        **Sample Prompt**

        ```
        Take this source image: [DAM path] and create variants for the following audience segments: [segment 1 — describe], [segment 2 — describe], [segment 3 — describe]. Adjust [copy overlay / color treatment / background] per segment while keeping the core composition. Save each variant to [DAM folder path] with segment name in the filename.
        ```
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="04 Assets (DAM)">
    Getting assets organized, tagged, and compliant before they're used. The cleaner your DAM, the faster Grady can find and use the right asset.

    <AccordionGroup>
      <Accordion title="4.01 — Add tags to tagging taxonomy">
        **Complexity:** Small | **Scope:** DAM | **Platform:** DAM

        Add new tags to the tagging taxonomy for organizing and classifying content, pages, or other assets.

        **Sample Prompt**

        ```
        Add the following tags to the tagging taxonomy: [tag1] under [category, e.g., Content Type], [tag2] under [category, e.g., Page Classification], and [tag3] under [category, e.g., Campaign Theme]. Apply them to [content type, e.g., Campaign Theme, blog posts].
        ```
      </Accordion>

      <Accordion title="4.02 — Update tags in tagging taxonomy">
        **Complexity:** Small | **Scope:** DAM | **Platform:** DAM

        Modify or update existing tags within the tagging taxonomy to reflect revised naming, categorization, or structure.

        **Sample Prompt**

        ```
        In the tagging taxonomy, rename the tag [old tag name] under [category] to [new tag name]. Also, move the tag [tag name] from [old parent category] to [new parent category] to reflect the updated classification structure.
        ```
      </Accordion>

      <Accordion title="4.03 — Update asset metadata">
        **Complexity:** Small | **Scope:** Single asset | **Platform:** All

        Update the metadata associated with an asset — description, tags, and other attributes.

        **Sample Prompt**

        ```
        For this asset: [asset path or name], update the description to [new description] and add the following tags: [tag1, tag2, tag3].
        ```
      </Accordion>

      <Accordion title="4.04 — Tag and organize 1,000 untagged assets in the DAM">
        **Complexity:** Complex | **Scope:** Multi-asset | **Platform:** DAM

        Bulk-classify a backlog of untagged assets using content recognition — applying consistent taxonomy without manual review of each file.

        **Sample Prompt**

        ```
        Review all untagged assets in [DAM folder path] and apply appropriate tags from our taxonomy. Use the asset content and filename to infer type, campaign, region, and subject matter. Flag any assets you're uncertain about for manual review.
        ```
      </Accordion>

      <Accordion title="4.05 — Find pages and campaigns still using the old logo">
        **Complexity:** Medium | **Scope:** Multi-page | **Platform:** All

        Locate every instance of a deprecated asset across the site and in active campaigns, then replace them with the updated version.

        **Sample Prompt**

        ```
        Find every page and active email campaign using the old logo at [old DAM path] and replace it with the updated version at [new DAM path]. Report a list of everything changed.
        ```
      </Accordion>

      <Accordion title="4.06 — Find all pages using expired-license images and flag them">
        **Complexity:** Medium | **Scope:** Multi-page | **Platform:** All

        Audit live pages against a list of assets with expired or restricted licenses and surface anything that needs to be replaced.

        **Sample Prompt**

        ```
        Cross-reference the assets used on our live pages against this list of expired-license images: [attached CSV or list of DAM paths]. Flag every page that contains one and queue them for image replacement.
        ```
      </Accordion>

      <Accordion title="4.07 — Generate on-brand social cards for our next 10 blog posts">
        **Complexity:** Medium | **Scope:** Multi-asset | **Platform:** DAM

        Auto-generate a set of social share images from blog post content, applying brand templates and storing the outputs in the DAM.

        **Sample Prompt**

        ```
        Create social share cards for these 10 blog posts: [list of URLs]. Use the [social card template name] template, pull the headline and hero image from each post, and save the outputs to [DAM folder path].
        ```
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="05 Channel Orchestration">
    Getting the right content to the right audiences across email, web, and other channels. Grady can build, schedule, and personalize campaigns end-to-end.

    <AccordionGroup>
      <Accordion title="5.01 — Add and delete modules within emails">
        **Complexity:** Medium | **Scope:** Single email | **Platform:** Email

        Add or remove content modules within an existing Marketo or SFMC email to adjust its layout and structure.

        **Sample Prompt**

        ```
        In this Marketo email: [email name or ID], add a [module name, e.g., Text + Image] module below the [existing module name or position]. Then delete the [module name or description] module that is no longer needed.
        ```
      </Accordion>

      <Accordion title="5.02 — Clone existing campaign with all settings">
        **Complexity:** Medium | **Scope:** Single campaign | **Platform:** Email

        Duplicate an existing Marketo or SFMC campaign with all its settings — smart list filters, flow steps, and schedule configuration.

        **Sample Prompt**

        ```
        In Marketo, clone this campaign: [campaign name or ID] with all of its current settings, including smart list filters, flow steps, and schedule. Name the cloned campaign [new campaign name] and place it in [folder or program path].
        ```
      </Accordion>

      <Accordion title="5.03 — Schedule batch campaign">
        **Complexity:** Medium | **Scope:** Single campaign | **Platform:** Email

        Schedule a Marketo or SFMC batch campaign to run at a specified date and time with defined person qualification rules.

        **Sample Prompt**

        ```
        In Marketo, schedule a batch campaign: [campaign name or ID] to run on [date and time, e.g., 2025-04-15 at 9:00 AM EST]. Use the existing smart list and flow settings. Set the person qualification rules to [run each person once / allow re-entry].
        ```
      </Accordion>

      <Accordion title="5.04 — Create emails from templates">
        **Complexity:** Complex | **Scope:** Single email | **Platform:** Email

        Create a new email in Marketo or SFMC using a predefined template, populated with provided subject line, header, body copy, CTA, and image content.

        **Sample Prompt**

        ```
        In Marketo, create a new email using the [template name] template. Populate it with the following content:
        Subject line: [subject line]
        Header: [header text]
        Body: [body copy]
        CTA: [CTA text and link]
        Image: [image path or description]
        ```
      </Accordion>

      <Accordion title="5.05 — Build a 5-email welcome journey for new trial signups">
        **Complexity:** Complex | **Scope:** Multi-email | **Platform:** Email

        Design and build a complete onboarding email series — sequenced, timed, and loaded into your MAP — without writing each email from scratch.

        **Sample Prompt**

        ```
        Build a 5-email welcome journey in [Marketo / SFMC] for new trial signups. Use our brand voice guidelines and the following content themes:
        Email 1 (Day 0): Welcome + getting started
        Email 2 (Day 2): Key feature highlight
        Email 3 (Day 5): Use case spotlight
        Email 4 (Day 10): Community / resources
        Email 5 (Day 14): Upgrade nudge
        Reference this existing email for tone and structure: [example email name or URL].
        ```
      </Accordion>

      <Accordion title="5.06 — Localize an email campaign for priority markets">
        **Complexity:** Complex | **Scope:** Multi-email | **Platform:** Email

        Translate and adapt an email campaign for multiple regional markets, applying locale-specific copy, imagery, and compliance requirements.

        **Sample Prompt**

        ```
        Localize this email campaign: [campaign name or ID] for the following markets: [market 1], [market 2], [market 3]. Translate copy, adapt CTAs for regional offers, and ensure each version includes the required footer compliance text for that region.
        ```
      </Accordion>

      <Accordion title="5.07 — Re-engage subscribers who haven't opened in 90 days">
        **Complexity:** Medium | **Scope:** Segment | **Platform:** Email

        Build and launch a win-back campaign targeting a lapsed segment with a tailored offer, automatically suppressing anyone who re-engages.

        **Sample Prompt**

        ```
        In [Marketo / SFMC], build a re-engagement campaign targeting contacts who haven't opened any email in the last 90 days. Use a subject line that acknowledges the gap, offer [incentive or value prop], and suppress anyone who opens or clicks from future re-engagement sends.
        ```
      </Accordion>

      <Accordion title="5.08 — Write and schedule this month's newsletter">
        **Complexity:** Medium | **Scope:** Single email | **Platform:** Email

        Draft, build, and schedule the monthly newsletter to segmented lists — from content assembly to send.

        **Sample Prompt**

        ```
        Write and schedule this month's newsletter in [Marketo / SFMC]. Pull the top 3 blog posts from [URL or feed], include a spotlight on [product / campaign / event], and send to [list name] on [date] at [time, timezone]. Use the [newsletter template name] template.
        ```
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="06 Authoring">
    The hands-on CMS work — updating existing pages, creating new ones, and managing fragments. This is where Grady does the heavy lifting inside your content system.

    **Content Updates**

    <AccordionGroup>
      <Accordion title="6.01 — Single copy update">
        **Complexity:** Small | **Scope:** Single Page | **Platform:** All

        Update a single content element on the page — e.g., a hero headline, section title, or CTA label.

        **Sample Prompt**

        ```
        On this page: [page URL], update the hero headline to [new headline text].
        ```
      </Accordion>

      <Accordion title="6.02 — Multi copy update">
        **Complexity:** Small | **Scope:** Single Page | **Platform:** All

        Change multiple copy elements on a single page in one pass.

        **Sample Prompt**

        ```
        On this page: [page URL], update the hero headline to [new headline] and change the body text in the second section to [new body copy].
        ```
      </Accordion>

      <Accordion title="6.03 — Swap image(s) (upload asset)">
        **Complexity:** Small | **Scope:** Single Page | **Platform:** All

        Replace images on a single page using files attached directly to the task.

        **Sample Prompt**

        ```
        On this page: [page URL], replace the hero image with the attached file [filename.jpg] and swap the banner image in the promo section with [filename2.png].
        ```
      </Accordion>

      <Accordion title="6.04 — Swap image(s) (use DAM path)">
        **Complexity:** Small | **Scope:** Single Page | **Platform:** All

        Replace images on a single page by referencing existing assets via their CMS/DAM path.

        **Sample Prompt**

        ```
        On this page: [page URL], replace the hero image with the asset located at DAM path [e.g., /content/dam/images/hero-new.jpg].
        ```
      </Accordion>

      <Accordion title="6.05 — Update page with annotated screenshot">
        **Complexity:** Small | **Scope:** Single Page | **Platform:** All

        Attach an annotated screenshot to the task and have Grady apply the edits described in the annotations.

        **Sample Prompt**

        ```
        On this page: [page URL], make the edits shown in the attached annotated screenshot.
        ```
      </Accordion>

      <Accordion title="6.06 — Update element style(s)">
        **Complexity:** Small | **Scope:** Single Page | **Platform:** All

        Update the defined style on a given page element — e.g., button style, hero style, or theme variant.

        **Sample Prompt**

        ```
        On this page: [page URL], change the hero banner style from [current style] to [new style] and update the CTA button style to [new button style].
        ```
      </Accordion>

      <Accordion title="6.07 — Update page metadata">
        **Complexity:** Small | **Scope:** Single Page | **Platform:** All

        Update hidden page metadata — page title, meta description, SEO description, and keywords.

        **Sample Prompt**

        ```
        On this page: [page URL], update the page title to [new title], the meta description to [new description], and the SEO keywords to [new keywords].
        ```
      </Accordion>

      <Accordion title="6.08 — Create page variant">
        **Complexity:** Small | **Scope:** Single Page | **Platform:** All

        Create a new version of an existing page with specific content changes — e.g., a localized or campaign-specific variant.

        **Sample Prompt**

        ```
        Using this page as a reference: [source page URL], create a new variant with the following content changes: [list of localized/updated content].
        ```
      </Accordion>

      <Accordion title="6.09 — Multiple changes in one ticket">
        **Complexity:** Medium | **Scope:** Single Page | **Platform:** All

        Execute several discrete changes from a single task — updating copy, swapping assets, removing/adding components, and updating links.

        **Sample Prompt**

        ```
        On this page: [page URL], make the following changes:
        (1) Update the hero headline to [new headline].
        (2) Swap the hero image with [DAM path or attached file].
        (3) Remove the [component name] section.
        (4) Update the CTA link to [new URL].
        ```
      </Accordion>

      <Accordion title="6.10 — Insert component(s)">
        **Complexity:** Complex | **Scope:** Single Page | **Platform:** All

        Add a component to an existing page by specifying the component type and where it should be placed.

        **Sample Prompt**

        ```
        On this page: [page URL], add a [component name, e.g., Text + Image] component below the [existing component name or position] with the following content: [content details].
        ```
      </Accordion>

      <Accordion title="6.11 — Remove component(s)">
        **Complexity:** Complex | **Scope:** Single Page | **Platform:** All

        Remove a component from an existing page, identified either by name or by description of its position.

        **Sample Prompt**

        ```
        On this page: [page URL], remove the [component name or description, e.g., the promotional banner below the hero section].
        ```
      </Accordion>
    </AccordionGroup>

    **New Page**

    <AccordionGroup>
      <Accordion title="6.12 — Create new page (Word doc)">
        **Complexity:** Complex | **Scope:** Single Page | **Platform:** All

        Create a new CMS page using a Word document as the content source, with an existing page as the structural reference.

        **Sample Prompt**

        ```
        Create a new [page type, e.g., Article] page using this page as a reference: [reference page URL]. Populate it with the content from the attached Word document [filename.docx].
        ```
      </Accordion>

      <Accordion title="6.13 — Create new page (Figma)">
        **Complexity:** Complex | **Scope:** Single Page | **Platform:** All

        Create a new CMS page using a Figma design file as the content and layout source.

        **Sample Prompt**

        ```
        Create a new [page type, e.g., Landing Page] page using this page as a reference: [reference page URL]. Use the content and layout from this Figma link: [Figma URL].
        ```
      </Accordion>

      <Accordion title="6.14 — Create new page (URL)">
        **Complexity:** Complex | **Scope:** Single Page | **Platform:** All

        Create a new CMS page by pulling content from a public URL, with an existing page as the structural reference.

        **Sample Prompt**

        ```
        Create a new [page type, e.g., Product Page] page using this page as a reference: [reference page URL]. Pull the content from this public URL: [source URL].
        ```
      </Accordion>

      <Accordion title="6.15 — Create new page (Prompt)">
        **Complexity:** Complex | **Scope:** Single Page | **Platform:** All

        Create a new CMS page using only a text prompt for content, with an existing page as the structural reference.

        **Sample Prompt**

        ```
        Create a new [page type, e.g., Campaign Page] page using this page as a reference: [reference page URL]. Use the following content:
        Headline: [headline]
        Body: [body text]
        CTA: [CTA text and link]
        Image: [image description or DAM path]
        ```
      </Accordion>
    </AccordionGroup>

    **Fragments** *(AEM)*

    <AccordionGroup>
      <Accordion title="6.16 — Single copy update (content fragment)">
        **Complexity:** Small | **Scope:** Single fragment | **Platform:** AEM

        Update a single field on an existing content fragment.

        **Sample Prompt**

        ```
        On this content fragment: [content fragment path], update the [field name] to [new value].
        ```
      </Accordion>

      <Accordion title="6.17 — Single copy update (experience fragment)">
        **Complexity:** Small | **Scope:** Single fragment | **Platform:** AEM

        Update a single content element on an existing experience fragment.

        **Sample Prompt**

        ```
        On this experience fragment: [experience fragment path], update the [element name] to [new text].
        ```
      </Accordion>

      <Accordion title="6.18 — Create content fragment">
        **Complexity:** Medium | **Scope:** Single fragment | **Platform:** AEM

        Create a new content fragment with specified field values.

        **Sample Prompt**

        ```
        Create a new content fragment at [path] with the following fields:
        [field1]: [value1]
        [field2]: [value2]
        [field3]: [value3]
        ```
      </Accordion>

      <Accordion title="6.19 — Create experience fragment">
        **Complexity:** Medium | **Scope:** Single fragment | **Platform:** AEM

        Create a new experience fragment based on an existing reference fragment.

        **Sample Prompt**

        ```
        Create a new experience fragment at [path] using this reference: [reference XF path]. Update the content to: [new content details].
        ```
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="07 Review & QA">
    Checking work before it ships — QA, accessibility, brand compliance, and legal review. Grady can run these checks automatically so nothing goes live with issues.

    <AccordionGroup>
      <Accordion title="7.01 — Run a QA report on this page before it goes live">
        **Complexity:** Small | **Scope:** Single Page | **Platform:** All

        Check a page for broken links, rendering issues, missing metadata, and component errors before publishing.

        **Sample Prompt**

        ```
        Run a QA check on this page before it goes live: [page URL or staging URL]. Check for: broken links, missing images, metadata completeness, component rendering errors, and mobile display issues. Return a pass/fail summary with details on anything that needs fixing.
        ```
      </Accordion>

      <Accordion title="7.02 — Run an accessibility audit and queue the fixes">
        **Complexity:** Complex | **Scope:** Multi-page | **Platform:** All

        Audit pages against WCAG standards, surface violations, and create a remediation task list.

        **Sample Prompt**

        ```
        Run an accessibility audit on [page URL / site section]. Check against WCAG 2.1 AA standards. Return a list of violations organized by severity, and create tasks in Gradial for each fix.
        ```
      </Accordion>

      <Accordion title="7.03 — Find everywhere the brand guideline was violated and fix it">
        **Complexity:** Complex | **Scope:** Multi-page | **Platform:** All

        Audit the site against an updated brand guideline and apply corrections across all affected pages in a single pass.

        **Sample Prompt**

        ```
        Find every page where we're using [old brand element, e.g., the old logo / deprecated color / outdated typeface] and replace it with the updated version per our brand guidelines at [guidelines URL or attached doc].
        ```
      </Accordion>

      <Accordion title="7.04 — Monthly brand-consistency audit">
        **Complexity:** Medium | **Scope:** Multi-page | **Platform:** All | **Suggested cadence:** Monthly

        Audit a set of key pages against brand guidelines and flag anything off-brand for review.

        **Sample Prompt**

        ```
        Audit the following pages against our brand guidelines: [page URL 1], [page URL 2], [page URL 3]. Flag any copy, imagery, or styling that is off-brand and summarize the issues found.
        ```
      </Accordion>

      <Accordion title="7.05 — Standardize formatting on all legal and policy pages">
        **Complexity:** Medium | **Scope:** Multi-page | **Platform:** All

        Apply consistent structure, heading hierarchy, and formatting to a set of policy pages that have drifted from the standard.

        **Sample Prompt**

        ```
        Standardize the formatting on all pages in [folder path, e.g., /legal/]. Apply consistent H1/H2/H3 hierarchy, paragraph spacing, and link styling per our style guide. Flag any pages with content that needs human review before changes are applied.
        ```
      </Accordion>

      <Accordion title="7.06 — Add a compliance disclaimer to every product page in a region">
        **Complexity:** Medium | **Scope:** Multi-page | **Platform:** All

        Bulk-insert a required legal element across a regional page set without touching each page individually.

        **Sample Prompt**

        ```
        Add the following EU compliance disclaimer to the footer of every product page under [regional folder path]: "[disclaimer text]". Apply only to pages that don't already include it.
        ```
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="08 Launch">
    Getting content live — bulk publishing, find-and-replace across pages, scheduled sends, and rollout operations.

    <AccordionGroup>
      <Accordion title="8.01 — Find and replace (single page)">
        **Complexity:** Medium | **Scope:** Single Page | **Platform:** All

        Find specific terms within a single page and replace all instances with a new term.

        **Sample Prompt**

        ```
        On this page: [page URL], find all instances of [old term] and replace them with [new term].
        ```
      </Accordion>

      <Accordion title="8.02 — Find and replace (multi-page)">
        **Complexity:** Medium | **Scope:** Multi-page | **Platform:** All

        Find specific terms across multiple pages and replace all instances with a new term.

        **Sample Prompt**

        ```
        Across the following pages: [page URL 1], [page URL 2], [page URL 3] — find all instances of [old term] and replace them with [new term].
        ```
      </Accordion>

      <Accordion title="8.03 — Bulk update (copy)">
        **Complexity:** Medium | **Scope:** Multi-page | **Platform:** All

        Update copy across multiple pages. Can be run via prompt with a page list or as a Batch Task — batch is preferred for large sets.

        **Sample Prompt**

        ```
        Across the following pages: [page URL 1], [page URL 2], [page URL 3] — update [content element, e.g., component name] from [old value] to [new value]. Apply this as a batch task.
        ```
      </Accordion>

      <Accordion title="8.04 — Bulk update (assets)">
        **Complexity:** Medium | **Scope:** Multi-page | **Platform:** All

        Update asset references across multiple pages. Can use attached uploaded assets or existing DAM paths. Preferred as a batch task for large sets.

        **Sample Prompt**

        ```
        Across the following pages: [page URL 1], [page URL 2], [page URL 3] — replace the [component name] image with the asset at [DAM path or attached file]. Apply this as a batch task.
        ```
      </Accordion>

      <Accordion title="8.05 — Swap the seasonal banner across all regional homepages">
        **Complexity:** Medium | **Scope:** Multi-page | **Platform:** All

        Push a new promotional banner to every regional homepage simultaneously.

        **Sample Prompt**

        ```
        Swap the hero banner on all regional homepages to the [holiday/seasonal] promo using the asset at [DAM path]. Apply to: [list of locale URLs or folder path].
        ```
      </Accordion>

      <Accordion title="8.06 — Recurring find-and-replace check">
        **Complexity:** Medium | **Scope:** Multi-page | **Platform:** All | **Suggested cadence:** Weekly or monthly

        Periodically catch outdated terms — a deprecated product name, old legal phrasing, or a rebranded term — across a page set.

        **Sample Prompt**

        ```
        Across the following pages: [page URL 1], [page URL 2], [page URL 3] — find any instances of [outdated term] and replace them with [approved term]. Report which pages were changed.
        ```
      </Accordion>

      <Accordion title="8.07 — Scheduled batch email send">
        **Complexity:** Medium | **Scope:** Single campaign | **Platform:** Email | **Suggested cadence:** Weekly

        Run a recurring Marketo or SFMC batch campaign on a fixed weekly schedule using existing list and flow settings.

        **Sample Prompt**

        ```
        In Marketo, run the batch campaign [campaign name or ID] using the existing smart list and flow settings. Confirm the number of people who qualified and the send status.
        ```
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="09 Analyze & Optimize">
    Understanding what worked, fixing what didn't, and continuously improving — from performance reports to SEO, GEO, and A/B testing.

    **Insights & Analytics**

    <AccordionGroup>
      <Accordion title="9.01 — Show me content decay: which pages are losing traffic">
        **Complexity:** Medium | **Scope:** Site-wide | **Platform:** All

        Identify pages where organic traffic is declining and surface the likely causes.

        **Sample Prompt**

        ```
        Analyze traffic trends across our site over the last 6 months and identify pages where month-over-month organic traffic has declined by more than [X]%. For each, note the probable cause and recommend whether to update, consolidate, or retire the page.
        ```
      </Accordion>

      <Accordion title="9.02 — Summarize this quarter's web performance for the board">
        **Complexity:** Medium | **Scope:** Site-wide | **Platform:** All

        Pull the key performance metrics for the quarter and package them into a concise, exec-ready summary.

        **Sample Prompt**

        ```
        Summarize web marketing performance for [Q / date range]. Include: total traffic and trend, top-performing pages, conversion rates, and the top 3 initiatives that drove results. Format it as a one-page board summary.
        ```
      </Accordion>

      <Accordion title="9.03 — Which marketing channel is driving the highest-quality pipeline?">
        **Complexity:** Medium | **Scope:** Multi-channel | **Platform:** All

        Analyze pipeline attribution across channels and surface which ones are delivering the best-quality leads.

        **Sample Prompt**

        ```
        Analyze pipeline attribution for [time period]. Compare channels by: lead volume, opportunity conversion rate, average deal size, and time to close. Identify which channel is driving the highest-quality pipeline and recommend where to shift investment.
        ```
      </Accordion>

      <Accordion title="9.04 — Weekly GEO visibility report">
        **Complexity:** Medium | **Scope:** Multi-page | **Platform:** All | **Suggested cadence:** Weekly

        Run a recurring GEO visibility report so the team sees brand and competitor movement on a regular rhythm.

        **Sample Prompt**

        ```
        Run a GEO report on [yourwebsite.com] and summarize how our brand visibility has changed since the last report.
        ```
      </Accordion>
    </AccordionGroup>

    **SEO & GEO**

    <AccordionGroup>
      <Accordion title="9.05 — Is my site set up correctly for SEO?">
        **Complexity:** Medium | **Scope:** Site-wide | **Platform:** All

        Run a full technical SEO audit and get a prioritized list of issues — from crawlability and indexing to metadata gaps and redirect chains.

        **Sample Prompt**

        ```
        Run a technical SEO audit on [domain URL]. Check for: crawlability issues, missing or duplicate meta titles and descriptions, broken internal links, redirect chains, pages blocked from indexing, and missing schema markup. Return a prioritized list of issues to fix.
        ```
      </Accordion>

      <Accordion title="9.06 — Write meta titles and descriptions for every page missing them">
        **Complexity:** Medium | **Scope:** Multi-page | **Platform:** All

        Identify pages with missing or duplicate metadata and generate on-brand, keyword-relevant replacements in bulk.

        **Sample Prompt**

        ```
        Find every page in [folder path or site section] that is missing a meta title or meta description. Write SEO-optimized versions for each, using our brand voice and targeting the primary keyword for each page. Apply the updates.
        ```
      </Accordion>

      <Accordion title="9.07 — Fix all broken internal links and redirect chains">
        **Complexity:** Medium | **Scope:** Site-wide | **Platform:** All

        Crawl the site, identify broken links and unnecessary redirect hops, and resolve them.

        **Sample Prompt**

        ```
        Crawl [domain URL] and identify all broken internal links (404s) and redirect chains (3+ hops). Fix broken links by pointing them to the correct current destination. Simplify redirect chains to a single hop where possible.
        ```
      </Accordion>

      <Accordion title="9.08 — Make us visible in AI search for our key topics">
        **Complexity:** Complex | **Scope:** Multi-page | **Platform:** All

        Rewrite and restructure content so it's more likely to be cited by generative engines like ChatGPT, Perplexity, and Google AI Overviews.

        **Sample Prompt**

        ```
        Optimize our content for generative engine visibility on these topics: [topic 1], [topic 2], [topic 3]. For each, identify the pages most relevant to that topic, rewrite them to include clear factual statements and direct answers, and add structured data where applicable.
        ```
      </Accordion>

      <Accordion title="9.09 — GEO optimization (single page)">
        **Complexity:** Medium | **Scope:** Single Page | **Platform:** All

        Optimize a page's content to improve visibility and citation likelihood in AI-powered search engines.

        **Sample Prompt**

        ```
        On this page: [page URL], optimize the content for generative engine visibility. Rewrite or supplement the content to include clear, factual statements, direct answers to likely search questions, and well-structured information about [topic or subject matter]. Prioritize clarity and specificity so the content is more likely to be cited by AI search tools.
        ```
      </Accordion>

      <Accordion title="9.10 — GEO Monitoring (ongoing visibility over time)">
        **Complexity:** Medium | **Scope:** Multi-prompt | **Platform:** All

        Track brand and competitor visibility across AI search engines as a time series on a recurring cadence.

        Because the value comes from the breadth of the set, this isn't a single paste-able prompt. Download the starter set below, fill in your brand and competitors, and bulk-upload it from the **Prompts** tab.

        <Card title="Download the example prompt set (XLSX)" icon="file-excel" href="https://www.dropbox.com/scl/fi/v07bjbuad94mccfv4wo1e/geo-monitoring-example-prompts.xlsx?rlkey=xapp96bv0vv64nj5gcr0qc2q4&dl=1">
          20+ example prompts with topics, personas, and tags — formatted for Bulk Import.
        </Card>

        See [GEO Monitoring](/docs/insights/geo-monitoring) for the full setup and how topics, personas, and tags work.
      </Accordion>
    </AccordionGroup>

    **CX & Performance**

    <AccordionGroup>
      <Accordion title="9.11 — Find every dead end and broken CTA in our signup flow">
        **Complexity:** Medium | **Scope:** Multi-page | **Platform:** All

        Walk the full signup journey and surface every point where users can get stuck, hit a broken link, or encounter a non-functional CTA.

        **Sample Prompt**

        ```
        Audit our signup flow starting at [entry URL]. Walk every step and identify: broken CTAs, dead ends, form errors, pages that don't load correctly, and any steps where the journey stops unexpectedly. Return a list of issues with page URLs and descriptions.
        ```
      </Accordion>

      <Accordion title="9.12 — Create an A/B test for my landing page">
        **Complexity:** Medium | **Scope:** Single Page | **Platform:** All

        Set up a controlled experiment on a landing page — defining the variant, hypothesis, and success metric.

        **Sample Prompt**

        ```
        Set up an A/B test on this page: [page URL]. Create a variant that changes [element, e.g., the hero headline / CTA copy / hero image] to [new version]. Define the success metric as [conversion event] and run the test until we reach statistical significance.
        ```
      </Accordion>

      <Accordion title="9.13 — Map the journey from ad click to purchase and identify drop-off">
        **Complexity:** Complex | **Scope:** Multi-page | **Platform:** All

        Trace the full conversion path and pinpoint exactly where users abandon.

        **Sample Prompt**

        ```
        Map the full journey from [ad entry URL] through to [purchase confirmation URL]. Identify the steps where we see the highest drop-off, and for each one describe what the user experience looks like and what's likely causing the abandonment.
        ```
      </Accordion>

      <Accordion title="9.14 — Find where our mobile experience diverges worst from desktop">
        **Complexity:** Medium | **Scope:** Multi-page | **Platform:** All

        Compare desktop and mobile rendering across key pages and flag the worst breakpoints and missing elements.

        **Sample Prompt**

        ```
        Compare the desktop and mobile experience across these key pages: [list of URLs]. Identify the most significant differences in layout, component rendering, and usability. Prioritize issues by impact and provide a fix recommendation for each.
        ```
      </Accordion>

      <Accordion title="9.15 — Show me which experiments won and roll the winners out site-wide">
        **Complexity:** Complex | **Scope:** Multi-page | **Platform:** All

        Review completed experiments, identify statistically significant winners, and promote the winning variants.

        **Sample Prompt**

        ```
        Review all completed experiments run in the last [time period]. For each one that reached statistical significance, identify the winning variant and apply it to the full page population. Summarize the lift achieved for each.
        ```
      </Accordion>
    </AccordionGroup>
  </Tab>
</Tabs>