# Introduction to Agility CMS

> Source: https://agilitycms.com/docs/training-guide/content-editor-introduction

Agility CMS is a **headless content management system** that separates content management from presentation. This means:

- **Content is reusable**: Create content once, use it anywhere
- **Flexible presentation**: The same content can appear on websites, mobile apps, or other platforms
- **Modular approach**: Pages are built using reusable components

## Understanding Headless Architecture

Agility CMS follows a headless architecture pattern, where content management is completely separate from content delivery:

![Diagram of how content flows through Agility CMS. Agility CMS (content and pages, media library, Web Studio) publishes to the Content Fetch API and the Asset CDN, which your website and other apps and channels read. A publish webhook tells your site to revalidate. In the other direction, AI agents (through the MCP server) and scripts and CI (through the SDKs and CLI) write to Agility CMS through the Management API.](https://cdn.aglty.io/agility-cms-docs/images/training-guide/docs-diagram-headless-architecture.svg)

*In a headless architecture, publishing makes your content available through the Content Fetch API and your images through the Asset CDN. Your website and other apps and channels read from them, and a publish webhook tells your site to revalidate. In the other direction, AI agents (through the MCP server) and scripts (through the SDKs and CLI) write content through the Management API.*

**Key Benefits:**
- **Multi-channel publishing**: Same content for web, mobile, and other platforms
- **Technology freedom**: Use any frontend framework or technology
- **Performance**: CDN delivery and optimized asset management
- **Scalability**: Scale content management and frontend independently

## Understanding the Data Model

Agility CMS organizes content using a structured data model that separates content from presentation:

![Diagram of the Agility data model. A top row of models (page model, component model, content model) defines a row of instances below it. The sitemap maps the URL /blog/first-post to page 4 and content item 6. Page 4's main content zone uses a PostDetails component, the component displays content item 6 (a Post), and that post links to an Author content item.](https://cdn.aglty.io/agility-cms-docs/images/training-guide/docs-diagram-data-model.svg)

*The Agility data model shows how a Sitemap organizes Pages, Pages contain Components, and Components display Content Items. Each entity (Page, Component, Content) has a corresponding Model that defines its structure. This separation allows content to be reused across multiple pages and components.*

**Key Relationships:**
- **Sitemap** → Maps URLs to Pages
- **Pages** → Contain multiple Components
- **Components** → Display Content Items
- **Content Items** → Standalone, reusable pieces of content

## Understanding the Interface

The Agility CMS interface is organized into four main sections:

![Diagram of the four main sections of Agility CMS and what each holds. Content holds content lists and items, such as blog posts, authors and categories. Assets holds files, images and PDFs, served through the Asset CDN. Pages holds the sitemap, pages and components. Web Studio is where you preview pages before you publish. A typical workflow: upload assets, create content items, build pages from components, then preview in Web Studio.](https://cdn.aglty.io/agility-cms-docs/images/training-guide/docs-diagram-agility-sections.svg)

*The Agility CMS interface is organized into four main sections:*
- **Content**: Manage Lists and Items (reusable content)
- **Assets**: Manage Files, Images, and PDFs (media library)
- **Pages**: Manage Sitemap, Pages, and Components (page structure)
- **Web Studio**: Preview content before publishing

## Key Concepts

**Pages** → Individual web pages organized in a sitemap
**Components** → Reusable building blocks that display content on pages
**Content Items** → Standalone pieces of content that can be linked to components
**Media** → Images, documents, and other digital assets

## What You'll Learn

This generic training guide will teach you:

1. **How to navigate** the Agility CMS interface
2. **How to create and manage** content items
3. **How to build pages** using components
4. **How to work with** the media library
5. **How to publish** and preview content
6. **How to troubleshoot** common issues

Each section focuses on **how Agility CMS works** in general, not how a specific instance is configured. This knowledge will apply to any Agility CMS instance you work with.

---

**Next**: [Core Concepts](/docs/training-guide/content-editor-core-concepts) - Deep dive into the Agility Data Model, Headless Architecture, and Sections

---

## Related pages

- [Core Concepts](https://agilitycms.com/docs/training-guide/content-editor-core-concepts.md)
- [Navigating the Agility CMS Interface](https://agilitycms.com/docs/training-guide/content-editor-navigation.md)
- [Content Management Basics](https://agilitycms.com/docs/training-guide/content-editor-content-basics.md)
- [Page Management Basics](https://agilitycms.com/docs/training-guide/content-editor-pages-basics.md)
- [Working with Components](https://agilitycms.com/docs/training-guide/content-editor-components.md)
- [Publishing Workflow](https://agilitycms.com/docs/training-guide/content-editor-workflow.md)
- [Troubleshooting Common Issues](https://agilitycms.com/docs/training-guide/content-editor-troubleshooting.md)
- [Content Editor Training Guide](https://agilitycms.com/docs/training-guide/content-editor-overview.md)

Index of every docs page: https://agilitycms.com/docs/llms.txt
