Agility CMS documentationAgility CMS documentation
OverviewEditorsDevelopersOwners & AdminsTraining GuideApps
Sign inLet's Chat
Editors
Introduction to AgilityPages vs ContentPreviewing, Publishing, and Content StatesScheduling OverviewVersion History and CommentingContent SearchApprovals and WorkflowsLocalesSet your timezone and display languageBatch Content PublishingImporting and ExportingTask ManagementDeleting and Restoring ContentCopying and Duplicating ItemsRich Text EditorLive CollaborationPreviewing in Web StudioReal-Time Co-Authoring & Conflict HandlingLive Commenting & Collaboration in Web StudioYour account menuManage your notifications

Introduction

Previewing, Publishing, and Content States

Measure twice, cut once. Preview your content prior to publishing it.

What are Previews and why are they important?

Previewing allows Editors to view Staging Content within the context of your sites design. This is a crucial step before publishing content to the public. 

A Preview Environment should be set up and configured by your developer so Editors can Preview their Content in real-time as they make edits within Agility. Enabling Previews provides a level of confidence and security in an Editors workflow which has come to be expected as standard functionality. 

What types of Content can be Previewed?

You can Preview and Publish the following types of Content: 

  • Content Items 
  • Pages 

Content States

Content can exist in a number of different states, knowing what state your content is in is important when trying to preview it.

New

New State Indicator<br>

A brand new piece of content that has never been saved before.

Staging

Staging State Indicator<br>

Content that’s been saved but not yet published, this includes changes you've made to previously published content. Items in this state can be previewed.

Published

Published State Indicator<br>

Content in this stage is live and viewable on your website. 

Unpublished

Unpublished State Indicator<br>

Content that is no longer viewable on the live site. Content in this state cannot be previewed until new changes are made. 

Other

  • Scheduled - Content scheduled to be published
  • Expired - Content that had a set expiry date and has now expired and become unpublished
  • Awaiting Approval - An item that an Editor has requested approval to publish
  • Approved - An item that has been reviewed and approved for publishing
  • Declined - An item that has been reviewed and declined for publishing until new changes are made.

Use Case Example

An Editor creates a new piece of content. Until saved it will exist in the New state and cannot be previewed. 

  1. An Editor creates a new piece of content which will automatically exist in Staging
  2. When happy with the content and how it looks in Preview Mode, the Editor can request Approval to publish the content if necessary.
  3. The designated Approver can than review and Approve it
  4. That content would now be Published and viewable on the live site
  5. A couple of days later, the Editor needs to make some updates. The version they're working on would exist in a Staging until the new changes are submitted and Approved again. During this process, the original content is still live and Published on the site.
  6. The decision is later made to remove the content from the site. It’s moved to an Unpublished state where it can no longer be previewed and will not be viewable on the live site.

Preview not working?

Setting up a preview deployment is required for preview to work. If you are having issues, contact your developer or contact support@agilitycms.com for assistance.

The ability to preview content before publishing is crucial to the success of your digital solutions. As editors, you need to be confident of your changes before they are made public.

Agility provides a built-in content workflow that seamlessly enables editors to preview their changes before they publish. Understanding this concept is important to managing content in the CMS.

Content States

In Agility, there are a number of states in which your Content can be in. Below is an outline of each state and what they mean.

New

A new piece of content that has been initialized but not yet saved of published. This content is not viewable in Preview or on the Live website.

Creating new content in Agility CMS Select an Image

Staging

Content that is staging means it is not yet published. This refers to content that can be viewed in 'Preview' mode but not on the Live website. This is useful when you are making content changes and would like to Preview the changes before publishing them on the live site.

Staging content in Agility CMS Select an Image

Published

Published means your content is on the latest version, and it is viewable on the Live site.

Viewing published content in Agility CMS Select an Image

Previously Published

This state indicates that the current content is published, however, there is content that has been updated that has not yet been published. This content is still viewable in Preview.

Previously published content in Agility CMS Select an Image

Unpublished

Content that is unpublished will not appear on the Live website. Any content that is unpublished will also not be available to Preview.

Viewing unpublished content in Agility CMS Select an Image

Why is Preview Important?

Being able to Preview Content prior to Publishing is crucial for Content Editors. Content Previews provides Content Editors with the ability to view Staging Content from the CMS within the context of your website's design.

A Preview Environment should be set up and configured so Content Editors can Preview Content in real-time as they are making edits within Agility CMS. Enabling Previews provides a level of confidence and security in a Content Editors workflow which they've come to expect as standard functionality.

What Can You Preview and Publish?

In Agility CMS, you are able to Preview and Publish the following types of Content:

  1. Content Item(s)
  2. Content Lists
  3. Pages
  4. Page Modules

What is The Typical Content Workflow?

New Code or changes to Content Models are typically handled by developers. Content Editors should only have to focus on one thing, the Content!

A typical workflow looks like this:

  1. A Content Editor
  2. When ready, the Content Editor
  3. The designated
  4. Once
  5. Published

Implementing a content workflow such as above allows Content Editors to focus on writing good content while designating an approver to manage if and when content should be published and made available for production. Keep your editors productive, while maintaining a high level of quality control.

Preview Not Working?Setting up a preview deployment is required for preview to work. If you are having issues, contact your developer or contact support@agilitycms.com for assistance.

← Previous
Pages vs Content
Next →
Scheduling Overview
On this page
What are Previews and why are they important?What types of Content can be Previewed?Content States
Agility CMS documentationAgility CMS documentation

Documentation for the CMS built for editors, developers, and AI agents.

Docs
  • Overview
  • Editors
  • Developers
  • Owners & Admins
  • Training Guide
  • Changelog
Resources
  • Get Support
  • MCP Server
  • System Status
  • llms.txt
Agility
  • agilitycms.com
  • Start Free Trial
  • Sign in
  • Blog
© 2026 Agility Inc. All rights reserved.
Privacy PolicyTerms of Service