Understanding pages, collections, and templates

Documentation / Getting started

A page holds content and metadata for a visitor-facing destination. Its identity is separate from its URL: renaming a path does not mean you intended to create a different page. Internal page references use that stable identity rather than relying only on a readable path.

A collection groups pages and defines how they are organized. Sequential collections support ordered trees. Dated collections support date-oriented content such as blogs. Collection configuration and tree structure influence item addresses and listings, so select the intended collection before adding content.

Structure is not metadata

Navigation ordering and nesting come from the collection's root structure. Page labels, titles, availability, and other metadata come from the individual pages. Typing a nested-looking URL is not a substitute for placing a page in the navigation tree.

A page template supplies reusable page structure. The renderer combines the template with the page's named editable content and permitted overrides. Template-controlled sections are not ordinary independent copies on each page. Editing the shared template can therefore affect existing pages.

Choose the right starting point

For an ordinary informational page, use the page list and review its access and navigation settings. For a growing library, choose a sequential collection. For dated posts, use a dated collection. When several pages must follow the same structure, assess a template before duplicating content repeatedly.

After creating an item, inspect its actual route, collection membership, title, and template state. Do not judge those settings from appearance alone.

Continue with Collections and content trees, Blogs, or Templates and reusable content for the corresponding model.