In this article, we cover FORGE's capabilities of defining new and bespoke custom entities to build content faster.
Topics covered here:
Out-of-the-box entities
FORGE provides the editorial teams with the following entities:
- Story: Together with photos, stories are the main building blocks to assembling content. A story is a collection of story parts, which can be either text or any other type of editorial entity.
-
Photo: The other main building block that, with stories, makes up the content.
FORGE relies on Cloudinary for photos storage: all formats Cloudinary supports, FORGE supports. Size limits depend on the Cloudinary paid plan, which is a choice of the digital project based on FORGE. - Album: A collection of photos.
- Document: Any file. Administrators configure the allowed file formats and sizes.
-
Editorial selection: A collection of entities grouped in an entity, which is called editorial selection.
An editorial selection can contain different types of editorial entity; for example, it can collect stories, photos, and documents together.
Custom entities
Beyond the out-of-the-box (OOTB) entities, administrators and producers can define custom entities and use them inside stories and as items within editorial selections.
The following screenshot shows a list of possible custom entities:
Permission-based visibility and management
For each custom entity C, a permission Wcm.View.CustomEntity.C exists that editors must have to see and use that specific custom entity in:
- Menus
- Lists
Editors need the additional permission CanOperateOn.Wcm.C to create, edit, and delete the custom entity C.