List Guide
List Guide
Lists are used when a Page should automatically display a collection of content that grows over time.
Instead of manually updating an archive page every time new content is published, you configure the rules once and let the website keep the page current.
When To Use a List
Use a List when the page should show an ongoing collection such as:
- a blog archive
- a resource library
- a case study index
- a team directory
- a product collection
- a news or updates hub
If the content will continue to grow and should be displayed according to rules, a List is usually the right tool.
When Not To Use a List
Do not use a List when:
- the page should be a manually curated sales page
- the content set is small and unlikely to change
- the order needs full hand-crafted control rather than rule-based display
In those cases, a regular Page built from Components may be the better fit.
Recommended Workflow
- Define the content purpose
- Choose the Page that should host the List
- Configure the content rules
- Choose how items should be displayed
- Review pagination and growth behavior
What Makes a Good List Experience
Strong Lists usually:
- focus on one clear type of content
- use a consistent display pattern
- help visitors scan quickly
- support content growth without becoming cluttered
- make navigation easy as the collection expands
Common Use Cases
- blog listing pages
- events archives
- product catalogs
- team directories
- resource hubs
Common Mistakes
- using a List where a curated landing page would be better
- mixing unrelated content types into one collection
- showing too many items at once
- designing only for the first few entries
- forgetting to review how pagination and browsing feel over time
Team Guidance
- keep one List focused on one content purpose
- design for growth from the beginning
- review the browsing experience with realistic content volume
- use Lists when content should stay current automatically