Want to add content - such as a blog, team, news, portfolio, etc.? Cherry-pick content from your collections, based on certain parameters, and autopopulate both overview and detail pages, automating repetitive tasks.
A webpage with static content is hard-coded and consists of elements that are created one by one. Although there is a time and place for the benefits of static content, it is considered impractical for content that is constantly changing. Think of bulk content such as a blog, team, news, portfolio, product catalog, etc. that would require you to manually duplicate and adjust large amounts of content to build and maintain. This, of course, is something you want to avoid. Hence, dynamic content.
A dynamic content webpage changes, based on the data you feed it. The idea is that you collect and store data - or bulk content, in a collection - often referred to as a database. These collections consist of a generated list and a dynamic page. Think of an overview page with all data, on the one hand - a blog for example, and a detail page on the other hand - a blog article, for example.
As opposed to a webpage with static content, dynamic content is not hard-coded. Instead, it:
- is generated 'dynamically', referencing a CMS or (external) collection
- automatically adapts to a number of predefined parameters represented by data fields, such as categories
- allows you to render content from a collection, both on an overview page and detail page.
Note: Before you can implement collections on your website, you or your project owner need to activate the Dynamic Content module in your General Project Settings.