Why Agility CMS has Page Management as a Headless CMS

It Just Makes Sense When Your Website is the Anchor

Joel Varty
Joel Varty
March 5, 2019
Why Agility Includes Page Management with its Headless APIs

The main benefit of Headless CMS is that it provides a much more flexible and efficient way to maintain a sophisticated Content Architecture across multiple digital properties. The "compose once, publish everywhere" paradigm is a major factor in why folks choose Headless CMS. Send content to mobile apps, websites, social networks, marketing automation platforms, and more... the list is as long as your digital strategy.

Most headless platforms eschew the concept of "Page Management." They claim that the separation of content from its presentation disallows the management of "pages," as they are only intended for a single output - your website. While this is true, it also ignores the fact that the main anchor for online content is your website, and it needs a special case.

How Agility Handles Pages

Agility allows you to define 3 things that make working with Pages really easy for both Content Editors and Developers to work with. Developers set up the templates and definitions, while Content Editors determine how and where they want to use those templates and definitions. This part of the Content Architecture is fundamental to the success of any CMS solution that includes a Website.

Page Templates

Agility Page Template

This allows a Developer to determine a Template name and a set of Module Zones that Content Editors can drop content into using Modules. The developer can then write code in the website to render this template into HTML.

Module Definitions

Module Definitions

This allows a Developer to define a set of fields to render a reusable item inside a Module Zone of a template. This can be anything as simple as a Header with a Description that is rendered as an <H2> and a <P> element. Or, it could be a complex user interface component, such as slider carousel, contact form, or a listing of blog posts.

The Developer has the choice of what properties the Content Editor will have to work with. These can be simple text, number, or date fields; they can image or file attachment fields, or they can link to other content that is defined elsewhere, such as Shared Content.  What's more, those Shared Content items or lists can then link to other Shared Content as well!

Modules are the building blocks that enable a Content Editor to create a complex website structure with tools the developer has set up for them to be successful.

Digital Channels & Sitemaps

Sitemaps and Digital Channels

Each Agility website can have one or more Sitemaps defined, each in its own Digital Channel. Each Digital Channel can be used to control a separate Digital Property.  This could, for example, be used for a contest or a completely separate branded site.

Essentially a Sitemap is a nested content structure which the developer will use to render on the website. Giving the Content Editor the control to manage multiple channels of page content is an extremely powerful and cost-effective way to manage content.

Shared Content is Paramount

We still believe in a "Content First" approach to designing your Content Architecture, and that starts with the Shared Content section of Agility. This is where all your main lists and items will live, and this is where you'll create most of your content that is reused across multiple destinations or endpoints, such as your app, social networks, etc.

The Pages section, however, is often the first place that users look to find the content they are working on, as the primary responsibility of your Content Teams is the website itself, and finding what Page something on just makes sense to people.

Back to All ResourcesBack to All Resources