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

# Start Here

> Find what you need in Gradial's documentation — or follow a guided path if you're just getting started.

**Already using Gradial?** Use the search bar above or the tabs to jump directly to what you need — **Setup & Administration** for integrations and access, **Gradial in Action** for workflows and features.

***

## New to Gradial?

Pick the path that fits where you are right now and we'll take you from there.

<CardGroup cols={3}>
  <Card title="I'm evaluating Gradial" icon="magnifying-glass" href="#im-evaluating-gradial">
    You want to understand what Gradial does, how it works, and whether it fits your team's needs.
  </Card>

  <Card title="I'm setting up the platform" icon="server" href="#im-setting-up-the-platform">
    You're an IT admin or technical lead connecting systems, provisioning access, and getting the environment production-ready.
  </Card>

  <Card title="I'm using Gradial daily" icon="bolt" href="#im-using-gradial-daily">
    You're a content manager, author, editor, or communications lead running tasks, updating content, and getting pages live.
  </Card>
</CardGroup>

***

<a id="im-evaluating-gradial" />

## I'm Evaluating Gradial

You want to understand what Gradial is, what it can do, and how it fits into your team's existing workflows before committing to a full setup. This path gives you the full picture without requiring any credentials or configuration.

<Steps>
  <Step title="Understand what Gradial is and the problem it solves">
    Gradial is the system of work that sits across your existing martech stack and executes the jobs between brief and live. This page covers the content supply chain problem, the systems-of-record vs. systems-of-work framing, what Gradial's agents actually do, and the three architectural pillars that differentiate it.

    [What Is Gradial? →](/docs/getting-started/what-is-gradial)
  </Step>

  <Step title="Learn how it works">
    Understand the mental model behind Gradial: how agents receive and execute work, how specialized agents orchestrate across complex jobs, how it connects to your stack, and how it builds a working understanding of your organization over time.

    [How Gradial Works →](/docs/getting-started/how-gradial-works)
  </Step>

  <Step title="See what integrations are supported">
    Gradial connects to the CMS, project management, design, and marketing automation tools your team already uses. Review the full integrations list to confirm your stack is covered.

    [Integrations Overview →](/docs/integrations-administration-and-setup/integrations/get-started-with-integrations)
  </Step>

  <Step title="Understand the core workflows">
    Gradial organizes work into two main categories: updating existing content and creating new experiences. Read both overviews to understand the scope of what agents can handle.

    [Content Updates →](/docs/updating-existing-experiences-i-e-content-updates/content-updates) · [New Page Workflow →](/docs/creating-new-experiences/new-page)
  </Step>

  <Step title="See cross-channel campaign execution in action">
    One of Gradial's most powerful capabilities is turning a single campaign brief into fully built assets across every channel simultaneously — web pages, email templates, audience configuration, content updates — without per-channel tasking or coordination overhead.

    [Cross-Channel Campaign Execution →](/docs/campaign-management/cross-channel-campaigns)
  </Step>

  <Step title="See how Gradial handles quality and compliance">
    Gradial enforces brand standards, SEO rules, and WCAG 2.2 AA accessibility compliance automatically. This is often a key differentiator for enterprise teams with strict governance requirements.

    [QA Reports →](/docs/quality-assurance-and-accessibility/qa-report) · [Accessibility Reports →](/docs/quality-assurance-and-accessibility/accessibility-report)
  </Step>

  <Step title="Review what's shipped recently">
    Check the release notes to see the current pace of product development and what capabilities have been added in recent months.

    [Release Notes →](/release-notes/overview)
  </Step>

  <Step title="Talk to the team">
    Ready to go deeper? Request a demo to see Gradial running against your actual CMS and content — not a generic sandbox.

    [Request a Demo →](https://www.gradial.com/request-demo)
  </Step>
</Steps>

***

<a id="im-setting-up-the-platform" />

## I'm Setting Up the Platform

You own the technical foundation. Before anyone on your team can use Gradial, you need to connect your systems, configure access, and validate the environment. This path takes you from a freshly provisioned org to production-ready.

**Estimated time:** 1–3 weeks (largely dependent on your IT team's security review process)

<Steps>
  <Step title="Understand what you're setting up">
    Start with how Gradial works — what it connects to, how agents receive and execute work, and what systems are involved — before you touch any credentials.

    [How Gradial Works →](/docs/getting-started/how-gradial-works)
  </Step>

  <Step title="Run environment discovery">
    Before connecting anything, work through Phase 1 of the onboarding checklist. It tells you exactly what your team needs to gather — example tickets, workflow docs, golden page candidates — before technical setup can begin.

    [Onboarding Checklist →](/docs/getting-started/onboarding-checklist)
  </Step>

  <Step title="Connect your CMS">
    This is the critical path. Connect Gradial to your primary CMS. Each integration requires specific service accounts and permission configurations — plan for security review time.

    <CardGroup cols={2}>
      <Card title="AEM (6.5 or Cloud)" icon="layer-group" href="/docs/integrations-administration-and-setup/integrations/aem/aem-overview">
        OAuth 2.0 or IMS authentication, JCR permissions, technical account setup
      </Card>

      <Card title="Sitecore" icon="layer-group" href="/docs/integrations-administration-and-setup/integrations/sitecore-integration">
        XM Cloud or Content Hub — guided wizard setup
      </Card>

      <Card title="Marketo" icon="layer-group" href="/docs/integrations-administration-and-setup/integrations/marketo">
        API-only user, LaunchPoint service, OAuth credentials
      </Card>

      <Card title="Salesforce Marketing Cloud" icon="layer-group" href="/docs/integrations-administration-and-setup/integrations/salesforce-marketing-cloud">
        Installed Package, Server-to-Server API, multi-BU support
      </Card>
    </CardGroup>

    [See all integrations →](/docs/integrations-administration-and-setup/integrations/get-started-with-integrations)
  </Step>

  <Step title="Connect your ticketing system">
    Gradial works directly from tickets in Jira, Workfront, Wrike, and others. Connecting your ticketing system activates the queue automation that makes Gradial most valuable for content teams day-to-day.

    [Set Up Ticketing Integrations →](/docs/integrations-administration-and-setup/how-gradial-works-with-ticketing-systems/setting-up-ticketing-integrations)
  </Step>

  <Step title="Configure SSO">
    Connect Gradial to your identity provider to enable single sign-on. Supported: Microsoft Entra ID, Okta OIDC, and custom OIDC.

    [Configure SSO →](/docs/integrations-administration-and-setup/managing-access/sso)
  </Step>

  <Step title="Set roles and invite your team">
    Define who can do what. Gradial has organization-level and workspace-level roles. Invite your admins, content leads, and editors, and assign appropriate permissions before handing off to content teams.

    [Roles & Permissions →](/docs/integrations-administration-and-setup/managing-access/roles) · [Manage Team Members →](/docs/integrations-administration-and-setup/managing-access/manage-team-members)
  </Step>

  <Step title="Validate and hand off">
    Complete Phases 3 and 4 of the onboarding checklist — confirm integrations are live, run sandbox validation, and sign off with your Gradial contact before content teams begin using the platform.

    [Onboarding Checklist: Phases 3 & 4 →](/docs/getting-started/onboarding-checklist)
  </Step>
</Steps>

<Warning>
  The single most common delay in Gradial onboarding is IT provisioning and security reviews. Submit a single, consolidated credential request rather than individual asks spread out over time — it can cut weeks off your timeline.
</Warning>

***

<a id="im-using-gradial-daily" />

## I'm Using Gradial Daily

You're a content manager, author, editor, communications lead, or team owner running tasks and getting content live. This path covers the operational skills you need — starting with the basics and building toward more complex workflows and quality configuration.

**Estimated time:** 2–4 hours to get comfortable with the basics; add new workflows as you go

<Steps>
  <Step title="Get oriented in the platform">
    Start by learning how the platform is laid out — where tasks live, how workspaces are organized, and how to navigate between projects.

    [Navigating the Platform →](/docs/getting-started/navigating-the-platform)
  </Step>

  <Step title="Learn how to brief an agent">
    The quality of what Gradial produces depends heavily on how you describe the task. Read the prompting guide before running your first task — it will save you from multiple re-runs and frustration.

    [Prompting an AI Agent →](/docs/getting-started/ask-grady)
  </Step>

  <Step title="Run your first content update">
    Start small: a copy change, a link swap, a styling fix. These are fast, low-risk, and a good way to learn the task loop — brief → run → review → stage → publish.

    [Small Content Updates →](/docs/updating-existing-experiences-i-e-content-updates/small-content-updates)
  </Step>

  <Step title="Move to medium-complexity updates">
    Once you're comfortable, tackle more involved work: component swaps, batch changes, find-and-replace across pages, and content fragment updates.

    [Medium Content Updates →](/docs/updating-existing-experiences-i-e-content-updates/medium-content-updates-in-gradial)
  </Step>

  <Step title="Create a new page">
    Learn the four ways to create a new page in Gradial: copying an existing page, using design patterns, working from a Word doc or creative brief, or importing a Figma design.

    [New Page Workflow →](/docs/creating-new-experiences/new-page)
  </Step>

  <Step title="Validate your work before it goes live">
    Before content publishes, run a QA report to catch brand and compliance issues, and an accessibility report to validate WCAG 2.2 AA conformance.

    [QA Reports →](/docs/quality-assurance-and-accessibility/qa-report) · [Accessibility Reports →](/docs/quality-assurance-and-accessibility/accessibility-report)
  </Step>

  <Step title="Work directly from your ticketing system">
    Once you're comfortable running tasks manually, learn how Gradial picks up tickets from Jira, Workfront, or Wrike automatically — so you can execute directly from your existing workflow without copy-pasting between tools.

    [How Gradial Works with Ticketing →](/docs/integrations-administration-and-setup/how-gradial-works-with-ticketing-systems/setting-up-ticketing-integrations)
  </Step>

  <Step title="Configure quality standards for your team">
    If you're a content lead or strategist responsible for how agents behave, the next step is setting up golden pages, design patterns, and QA rules. This is what scales quality across your entire team.

    [Golden Pages →](/docs/creating-new-experiences/golden-pages) · [Design Pattern Ingestion →](/docs/creating-new-experiences/design-pattern-ingestion) · [QA Rules Manager →](/docs/quality-assurance-and-accessibility/qa-report)
  </Step>
</Steps>

<Tip>
  The fastest way to improve output quality is better prompts, not re-running the same task. If a result isn't what you expected, revisit the [Prompting Guide](/docs/getting-started/ask-grady) before trying again — a clearer objective and one concrete example makes more difference than anything else.
</Tip>