Content Items, Content Lists, and Dynamic Page Lists

Follow

This article will walk you through the different types of items that can be created and managed within Shared Content, when to use them, and examples of each.

Content Item

Content items are an individual representation of a specific content definition. They are especially useful for things like Website Settings, API configurations, or any other settings 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 multiple instances of this item

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. Each site will likely have a customized global header content definition with any number of fields, which is dictated by the requirements of the header and what content it has.

In this case, this basic global header has two fields (one for the name, and another for the logo). If you wish to update a new logo for your brand, simply click upload (locally from your computer) or browse (from your Media & Documents in the Agility manager). You can also change the site’s name here. Remember to click publish, so the global header will go live on your page.

Note: this is just an example of a global header, every site will be different, as it will be customized to your exact requirements.

Content Lists

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

When to use:

  • You have a list of items that must be accessible to multiple pages
  • You need to have multiples instances (i.e. stored in a list)
  • Items in the list will not be used to generate dynamic pages
  • You want to expose structured content to an API

Example

If you have a list of categories that help group other content like blog posts or products together. In this case, we have a list of product categories that are used to group products together and is used to render a dropdownlist on the product input form. This allows editors to create new product categories and be able to select those categories on their product input form. Developers may also directly reference the list of product categories to be able to render a listing of categories on the website.

Product Categories Listing View:

Product Categories Input Form:

Product Input Form - referencing the Product Categories list:

Dynamic Page Lists

A dynamic page list is a special type of content list, where each item in the list represents a page.  Dynamic Page List’s are designed to work in unison with Dynamic Page nodes in the sitemap tree.

Dynamic Page List’s can be created from any Content Definition and are perfectly suited for things like Articles, Blog Posts, or any other type of structured content that makes up the main content for a page.

Once you create a dynamic page list, each dynamic page item will now have page specific properties - same ones you'd normally have on a static page.

Page level properties:

  • Meta Keywords
  • Meta Descriptions
  • Scripts
  • Additional Header Code

When to use:

  • You have similar requirements for a Content List, plus the following...
  • You have structured content and each item in the list should have its own page
  • You are going to have many items and don't want to have to create static pages for each piece of content
  • You want to maintain similar structure and layout for each item in the list 

Example

If you have structured content like an article, video, blog post, product where each item will have its own page.

In this example we'll look at how products can are setup to use dynamic pages.

Each product should have its own page, and there may be a large amount of products, therefore we should have a consistent way to manage products in one place, without having to create static pages for each one.

Solution:

  • A dynamic page list of products
  • A dynamic page node in Agility that represents the template used for each dynamic page
  • Routing formula defined in dynamic page node

A List of products:

Each product has page-level properties:

The dynamic page node in the page tree:

The dynamic page path, page title, and menu text formulas for the dynamic page node:

The dynamic page as shown on the website - note the page path is based on a URL friendly version of the product Title:

1 out of 1 found this helpful

Comments

0 comments

Please sign in to leave a comment.