fragments

Fragments are re-usable bits of content. Examples could include "tips" that are displayed on various pages, or locations to be shown in a table overview. It is highly dependent on your application whether fragments are a good fit. In some cases standard nodes will be more appropriate (in general, when each item will need its own page in addition to where ever it is shown), in others custom blocks might serve you better (be aware of the limited control over permissions core blocks currently offers, though). However, in some cases, neither nodes nor blocks are appropriate; Fragments fills a gap between these two solutions. Fragments are similar to Paragraphs, but where Paragraphs are bound to their host entity (and revisioned along with it), fragments are meant to be re-used and potentially update the same bit of content across many pages. Fragments are fieldable and revisionable.

Recommended modules

Views Bulk Operations

With this module available, an alternative, Views-based admin screen will be installed with filtering, sorting and, of course, bulk operations.

Inline Entity Form

Inline Entity Form offers a entity reference widget that will display a form to create a new Fragment inline in e.g. the node form where you reference Fragments. In certain uses cases you may want to enforce the need to create a Fragment separately, but in many cases it is extremely convenient to be able to create a new Fragment on the fly, right where you need it.

Automatic Entity Label

Every Fragment needs a label to identify it in the editorial interface, but in many cases you do not want to tie this to a title displayed to users (i.e. two Fragments may need the same title on your site's frontend, but editors still need a way to distinguish them). So, you end up adding a Display Title field. This module will help to set things up so editorial users only need to fill in the display title in most cases, but still have the option to override the administrative label when needed.