Agility Glossary

Short definitions of the terms used across the Agility documentation. Each term links to its own page, which explains it in a few sentences, lists related terms and points to the full documentation.

For how these concepts fit together, see Concepts and the Training Guide's Core CMS Concepts.

A

• App: A self-contained micro-site installed into an instance to extend the Content Manager, for example with custom fields that connect content to an external system.
• Asset: A file, such as an image, PDF or video, uploaded to the asset manager and served by URL over a global CDN.

B

• Batch: A group of pages, content items and components that are published or unpublished together with one action. In the Management API, most writes are queued as batches.

C

• Channel: The name the APIs and SDKs use for a sitemap, as in the channelName parameter.
• Component: An instance of a component model placed in a page zone, holding the content for one piece of UI.
• Component Model: The definition of the fields of a type of component. Each one needs matching code in your site.
• Component Zone: see Zone.
• Content Fetch API: see Fetch API.
• Content List: A container of content items that share a content model, stored in the Content section.
• Content Management API: see Management API.
• Content Model: A schema of fields that defines the structure of a type of content.
• Content states: see Staging and Published.
• Content Sync: Copying your content and pages into a store you own and keeping it current with a sync token.
• Custom Field: A field with a custom editing interface, provided by an App.

D

• Dynamic Page: A sitemap page that generates one page for each item in a content list.

F

• Fetch API: The read-only REST API that delivers your content, pages and sitemaps as JSON.
• Fetch Key: The API key that reads published content.

G

• Gallery: A named group of assets that can be attached to content and components.
• GraphQL API: A query API that returns exactly the fields you select, with several queries in one request.

I

• Instance: A dedicated area where editors create, manage and publish pages and content. It belongs to an organization.

K

• Knowledgebase MCP Server: A read-only MCP server that lets AI assistants search and read the Agility documentation.

L

• Linked Content: A field type that links an item or component to other content, as shared or nested content.
• llms.txt and Markdown twins: An index of a site's pages for AI agents, and a clean Markdown copy of each article.
• Locale: A language or region in which you serve a different version of your content.

M

• Management API: The REST API for writing to Agility: content, pages, models, media, workflow and webhooks.
• Markdown twin: see llms.txt and Markdown twins.
• MCP Server: The Agility CMS MCP Server, which connects AI assistants to your instances so they can manage content within your permissions.
• Module (formerly): now Component.
• Module Zone (formerly): now Zone.

N

• Nested Content: Linked content made of child items that belong only to their parent.

O

• Organization: Your main account, which all of your instances belong to.

P

• Page: An entry in a sitemap with a URL, SEO properties, a page model and the components in its zones.
• Page Model: The definition of a page's structure: the zones where editors add components.
• Page Module (formerly): now Component Model.
• Page Template (formerly): now Page Model.
• PAT: see Personal Access Token.
• Personal Access Token: A token that authenticates scripts and pipelines with the Management API as the user who created it.
• Preview Key: The API key that reads staging content as well as published content, for preview.

S

• Shared Content: Linked content that points at an existing content list, or items in it, so it can be reused everywhere.
• Sitemap: The page tree of a website or other destination. An instance can have several.
• Staging and Published: The two main content states: saved but not live, and live.

W

• Web Studio: The area inside Agility that shows your site for preview, visual editing and commenting.
• Webhook: An HTTP request Agility sends to your URL when content or pages change.
• Workflow: The approval process content and pages go through before they are published.

Z

• Zone: A named area of a page model where editors add and arrange components.