Creating and configuring a collection
Documentation / Collections and content trees
Create the collection before filling it with pages so that new items belong to the correct group from the start. Collection configuration defines the group; individual page settings define each item's content and access.
Create the collection
- Open the collections screen and choose New collection.
- Enter Name, using a label editors can recognize.
- Set Base path, such as
/resourcesor/news. - Choose Sequential (tree hierarchy) or Dated (blog/changelog) under Type.
- For a dated collection, enable Enable RSS feed if you want a feed.
- Choose Save, then select the collection when adding pages.
The main collection is special: its base path and type are not edited through the same controls as additional collections. Additional base paths are normalized to begin with a slash, and the configuration API rejects duplicate base paths.
Configure translations and advanced behavior
With a secondary content language selected, the form edits localized collection names and base paths. It does not create translated item content. Translate those pages separately.
The implementation also supports configuration properties such as parent-content behavior and default templates. They are not all exposed in the basic collection form. Do not assume a control exists for every supported property; obtain administrator assistance for settings absent from your screen.
Validate the collection
Add one page, save it, and open its public address. Then place a listing for the collection on a page and check the title and link. Before changing an established base path, review incoming links and redirects.
See Languages and translations and Search visibility and sharing.