Introduction to Content

Follow

In Agility, the Content area is a place for you to store and manage content across your website or digital solution.

The Content area is a place to store content that is not specific to a Page. Storing items here allows them to be available to all pages across your digital solution, and makes it easily exposed as an API for other services such as apps, or other external websites.

Content can come in the form of an individual item, or as a list of items and can be linked together to create Relationships. These items are based on a content schema or Content Model as they are referred to in Agility.

  1. Content Item
  2. Content List
  3. Relationships

Screen_Shot_2021-02-03_at_10.08.19_AM.png

Content Item

A content item is a singular item of content that is based on a content model. Content Items are especially useful for things that do not need to be re-used, such as Website Settings, a Global Header or Footer, or any other things that are used globally throughout your website.

When to use:

  • You have an individual item that must be accessible to multiple pages
  • You do not need a list of these items

Example:

An often-used content item is something like a global header. Your global header will normally be used for your company’s name and logo and will appear at the top of the website across all pages. This is a basic example of a global header that has 3 fields - a Logo, Site Name, and a Primary Call to Action link.

Screen_Shot_2021-02-03_at_10.34.16_AM.png

Content List

Content Lists allow you to create lists or collections of content that are shared and re-purposed on multiple areas of your site. Content lists are useful for situations that require multiple items of a specific content model in a single list.

When to use:

  • You have a list of items that must be accessible to multiple pages
  • You need to have multiple instances (i.e. stored in a list)
  • You want to expose structured content to an API
  • You want to build dynamic pages based on items stored in a list

Example:

A great example of a content list is a Blog, in this case, we have a list of posts. Developers can create a Post content model that represents the list of posts and how each post should be structured. This allows editors to create new posts based on the fields in the content model, such as a title, slug, date, image, and rich text area.

Posts Listing View:

Screen_Shot_2021-02-03_at_11.39.05_AM.png

Single Post View:

Screen_Shot_2021-02-03_at_11.54.05_AM.png

Relationships

Agility CMS allows you to link content to other content you have created which is tremendously useful for building relationships in your content architecture.

The way in which you relate content is facilitated by using Linked Content fields in your Content Models or Modules. There are a variety of Linked Content field types for different purposes. For example, you may want to create one-to-one, many-to-one, or one-to-many relationships.

Not only is this helpful for Editors in the CMS, but it can also be useful for Developers as they model their content architecture and directly influence what content is returned by the Content Fetch API. The Content Fetch API will automatically resolve linked content references and provide all the associated content in a single API call.

Example:

Our posts may have Linked Content or a relationship to a list of Authors. When creating a post, editors can link to the author who wrote the post.

Content List of Authors:

Screen_Shot_2021-02-03_at_12.13.44_PM.png

Authors Content List linked to Posts:

Screen_Shot_2021-02-03_at_12.29.22_PM.png

Introduction to Content Modelling

Agility CMS's unique approach to Content Modelling enables a robust and consistent way to define, and relate your content with endless possibilities!

Learn More

2 out of 2 found this helpful

Comments

0 comments

Please sign in to leave a comment.