Configuration status markers
Next to each configuration section, a field marker highlights whether there are either changes, warnings, or errors within the section. The marker's color can be:
Red: There's a blocking error and the configuration cannot be saved.
Yellow: There's a non-blocking warning and the configuration can be saved.
Blue: There are unsaved changes.
Within the section's details, near each field that causes the section marker, there is an icon representing the issue. Hovering over those icons, a tooltip shows the detailed explanation of the issue.
Issue full list
By selecting the 
button on the bottom left page, administrators can read the full list of issues across all sections.
Configurations
Permissions
This section defines the authorization groups that administrators assign to users and content to determine ‌content access.
Authorization groups
Content
This section customizes how editorial teams edit and search content.
Custom behaviors
Administrators can associate each entity with a software component, either out of the box or bespoke. This adds features that entities don't have natively.
E.g., add the story-part-table component to allow editorial teams to insert tables within stories.
Custom entities
Editorial teams need to shape content that represents their business. Administrators can craft bespoke entities accordingly in this section.
See the Assets customization article for details on how to create a custom entity.
Custom tabs
For each entity type, administrators can enrich the edit page by adding new tabs.
The following fields define a new tab:
Icon: The tab's icon.
Label: The tab's title.
Web component: The web component that renders the tab.
For example, the Sharing tab defined above for stories looks like in the following screenshot:
DIVA upload
This configuration allows connecting FORGE to the DIVA video workflow:
Custom Entity: Select which custom entity stores information about the FORGE-DIVA connection. Usually, it's the DIVA Video custom entity.
File extensions or MIME types: Which file extension is enabled to upload videos to DIVA.
Max file size (Megabyte): Maximum size of files to upload videos to DIVA.
Preroll: ID of the pre-roll campaign to apply to the uploaded videos.
Postroll: ID of the post-roll campaign to apply to the uploaded videos.
Custom attributes: When editors need other fields to shape the DIVA Video custom entity, they can add custom attributes as key/value couples:
Key: Name of the custom attribute.
Value: Value of the custom attribute.
When the FORGE-DIVA connection is not enabled, the following message displays:
Documents
This section defines the list of file types that the document entity can manage.
Entity view details
Administrator can customize filters and details available in the entity overview pages — both list and grid view:
Select the entity to customize:
For the list and grid view of the entity overview page, select the fields available for filtering:
Extended fields
Administrators can extend built-in entity types (e.g., Photo and Story) by adding custom fields.
For each entity type, a JSON Schema defines the object defining the list of extended fields for that entity type. E.g., the author field for stories.
External story parts
This configuration section allows referencing pieces of software that extend the available parts to add to stories. E.g., quotes and tables.
Photos
Within Photos, the following is configurable:
Defining ‌photo auto-publishing behavior:
After uploading the image
After replacing the image
Overriding and adding new formats to render images on the front-end through transformations
Adding photo fields as metadata
Preset texts
Use this configuration setting to define snippets of text to reuse within the text editor.
Editors select the snippet of text to use in the text editor toolbar by opening the Presets dropdown list.
Reference fields
Each entity can be enriched by adding other entities as custom properties. This section allows administrators to define that reference among entities.
Story body length
For each system language, this configuration section allows setting the maximum recommended word-number for stories.
Story part properties
Story parts are blocks of content that make up a story, like photos. This section allows extending the properties of those blocks.
The definition of the extended properties uses the JSON format.
Select the Give a sample button to get a snippet that helps you start defining new properties.
External sources
External feeds
This configuration section collects the external data sources for each entity type.
The following fields define a data source:
Name: Source's identifier.
URL: Source's URL.
External tags
This configuration section collects the external tag sources.
The following fields define a tag source:
Name: Source's identifier.
URL: Source's URL.
System
Distribution indexes
This configuration section allows defining how to index entities to enhance ‌search performance.
Select the Add distribution indexes button in the top right and choose the entity type.
In the JSON Schema field, define indexes for the selected entity type (tag, in the example below).
System languages
This section lists and allows adding the languages that the Content Manager manages.
The Culture — the language tag — and Name fields identify each language.
Hover over a language to make it the default one
or delete
it:
Text editor
Across the Content Manager, the text editor either displays or does not display the following features based on the configuration below:
Undo/Redo
Quote
Capitalization
Clear formatting
Subscript
Superscript
Strikethrough
Symbols
Emojis
Format painter
Spellcheck
Web components
Web components are pieces of software that extend the Content Manager user interface. They are identified by a name.
Web components extend:
Dashboards web components. When web components extend a dashboard, they can optionally set a permission required to display them.
Non-dashboard web components. E.g., the story-part-table web component adds tables to the story edit page.
Bundles. Bundles are collections of web components.
Technological limitations
Web components can be based on either Polymer or Lit, which cannot work together on the same entity edit page.
By default, entity edit pages support script-based modules (e.g., Lit and React).
In the section below, select the entity types for which to enable the Polymer web components in the edit page.
