collection

The Collection module allows users to organize content or configuration entities in arbitrary collections.

Examples include blogs (collections of posts), periodicals (collections of articles or stories), subsites (collections of pages, along with a related menu, for a discreet section of the site) and personal collections of content or configuration of interest to individual users.

Features

• Fieldable, revisionable Collection entities, which can be used as content pages like nodes.
• Collection types, similar to content types.
• Fieldable Collection item entities, used to link content (or configuration) entities (e.g. nodes) to Collections.
• Collection item types.
• Ability to place content in multiple Collections, while designating one Collection as the canonical (or primary) Collection.
• Ordering of items in Collections.
• Collection item listings as Paragraphs (via the included, experimental Collection Listing module).
• Multiple extension points (events and hooks) allowing developers to implement the specific requirements of their use cases.

Requirements

This module requires the following modules:

• Dynamic Entity Reference
• Path (core module)
• Inline entity form
• Key value field

Optional modules

• Paragraphs:
  When enabled along with the included Collection Listing module, users can create listings of the items in a given Collection for placement on another content entity.
• Pathauto:
  When enabled along with the included Collection Pathauto module, the URL alias of the Collection will be prepended to the URL alias of the content items with the Collection.

Similar modules

Collection has some similarities to the Group module, in that it uses Collection item entities as relation objects to join content/configuration to Collections. But Collection does not enable custom permissions and roles per Collection, and Collection allows users to place configuration entities, such as menus, into Collections.