Content
Intro to Content for Editors
Manage structured content that can be accessed across pages and other digital solutions.
What is Content and how is it managed in Agility?
The Content section in Agility is a hub for Editors to manage and edit any content that’s shared across your website or digital solution. Content Items can be made available to any page of your site and can even be stored in Content Lists to make grouping and publishing content even easier.
What is an Individual Content Item?
An individual Content Item is a singular content item that you only need one of. A good example is a site header as it's not something you'd need a whole list of.
Example Use Cases
- You have an individual item that must be accessible across multiple pages (like a Global Header or Footer)
- You don’t require the items to be grouped together in a collection
What is a Content List?
A Content List allows you to create a collection of content that can easily be shared together or re-purposed across multiple areas of your site, all using the same content model.
Example Use Cases
- You have a list of items that must be accessible to multiple pages (like a list of news articles)
- You need to have multiple instances of an item (i.e., stored in a list)
- You want to build a Dynamic Page based on items in a Content List
Content Relationships
Agility 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. 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 relationship.
Not only is
this helpful for Editors in Agility, 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
Further Reading
In Agility, the Content (area) is a place for you to store and manage content across your website or digital solution.
It is designed 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.
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 across 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.
Using global headers in Agility CMS Select an Image
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 of an item (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:
Post listing view in Agility CMS Select an Image
Single Post View:
Viewing blog posts in Agility CMS Select an Image
Moving Items within a Content List
If your list is being sorted by Item Order, you can use the move features that allows users to move content items within a content list to any point within the list.
You can move an item by Selecting it, then using the Up or Down arrows.
Moving items within a content list in Agility CMS Select an Image
Alternatively, you can use the tool beside the arrows to freely rearrange the order of items without having to click “up” and “down” many times to arrange the items in the order they want.
The Move mode also spans pages in the list. You can move an item from the bottom to the top of the list in a single click.
To initialize move mode within a content list simply select an items you want to move with the checkbox and select the “Move” option.
Initializing move mode in Agility CMS Select an Image
When Move is selected the grid will be put into “Move Mode” where you will be able to move through pages and click the “Move To Here” divider strip to perform the move operation.
Moving through pages in Agility CMS Select an Image
If you select multiple items to move they will move group together (if they are not already grouped side by side) and move to the position specified.
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. 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
Posts may have Linked Content or a relationship to a list of Categories. When creating a post, editors can link to the category the post should belong in.
Content List of Categories:
Creating relationships in Agility CMS Select an Image
Categories Content List linked to Posts:
Blog categories in Agility CMS Select an Image