Content Schemas

This document will explain the concept of Content Schemas and the types that are offered. We will walkthrough how to create and configure them as well as go over a few common use cases for each type.

In this document the term "developer" will refer to the person who creates and configures the Content Schemas. The term "content manager" refers to the person who will add and manage the content that uses the Content Schemas. These roles are not expected to be exclusive and at times will overlap.

The goal of the developer in designing Content Schemas should be creating an interface and experience that best serves the content manager.

What are Content Schemas

Content Schemas are definitions of your data. They are how a developer structures their data model and exposes it to content managers. Because Content Schemas are customizable with a large set of field data types they can be composed to represent rich sets of data.

Once a Content Schema has been created it's fields are available to the auto-generated template. A developer can begin templating against the data model while a content manager adds content independently of development.

Content Schema Types

  • Page: Has a singular view
  • Pageset: Multiple pages which a single view and parent page
  • Dataset: A set of data with no view


A Page type can be thought of as one-off pages. When you create a Page type there is an associated view, with the same reference name, created in the code editor. This will be the template for rendering instances of this page type.

Page Examples

  • Generic Reusable Page: This could be a generic page template which is intended to be used by content managers when ever they need a simple page. In this case you would be creating many page instances using one page template.
  • Landing Page: A self contained landing page with it's own design and/or functionality.
  • One-off Page: Contact, About, Sitemap, etc... can be instances of a one to one relationship of a page Content Schema and page template.


Pagesets are used to describe a many to many relationship. Meaning you can have a list of pages which each have a sub list of pages. Both the parent and child get a view generated in the code editor which will be used to render their respective instances.

Pageset Examples

  • Blog Posts: You could have a blog with many categories which each have many articles.
  • Product Listings: A simple product page could be a singular parent page which has many child product pages.
  • Team Page: A listing page of team members with sub-pages for each member.


Datasets represent a collection of data that does not need a view. They are meant to be used throughout the site on any number of pages. They can be related to a page via a relationship field type.

Dataset Examples

  • Social Links: Your social networks could be managed as a dataset and related to other Content Schemas as needed.
  • Forms: Can be beneficial as a dataset to be used across multiple pages.
  • Image Carousels: Sets of images which can be used in multiple places through out your web property.

Creating a Set

The Content Configurator section is where you will build your Content Schemas, the backbone of your web property. You can access the Content Configurator under the Styles & Settings tab.


To create a page, pageset, or dataset, click on your desired set type and fill out all the type information.


Click "Create page" to finalize the set.

Helpful Terms To Know

Content Schemas: Getting Started