Content Form

The first tab is named after the content type. It contains the display name followed by the fields defined by that content type.

Content types are supplied by applications available to the project or site. They determine which fields are shown, the kind of value each field accepts, and whether a value is required. Editors fill in these fields but do not change the form structure.

A mixin is a reusable set of fields that an application can add to multiple content types. For example, an SEO mixin might add a page title, description, and other metadata without defining a separate content type. The available mixins are determined by the configuration of your project or site. Some mixins are required and cannot be disabled, while others are optional and can be enabled or disabled by the editor.

Each enabled mixin has its own tab. Required mixins are enabled automatically and cannot be disabled. To manage optional mixins, open the menu next to the tabs, select or clear the available mixins, and click Confirm.

Developers can learn how mixins are defined and assigned in the Enonic CMS mixin documentation.

The Page tab is available when the item has a page configuration. It contains a hierarchical tree of the page, its regions, and its components.

Selecting a component in the tree also selects it in the Page Editor and opens its configuration in the Components widget. Use a component’s context menu to access its available actions. Components that support moving can also be rearranged by dragging them in the tree.

See Page Components tree for details about managing a page structure.

The display name is the large field at the top of the content type tab. It identifies the item throughout Content Studio and is a required field. An application’s content type can also define an expression that generates the display name from other field values.

For new items, Content Studio automatically generates a URL-friendly path name, also called a slug, from the display name. The path name is shown in the center of the Editor toolbar.

Like a file system, the path name is relative to its parent item. It must use supported characters and be unique among its siblings. The path name is commonly used in the item’s URL and can be changed by renaming the item.

Content items are automatically assigned a unique ID when they are created. This ID remains unchanged throughout the item’s lifetime. References between content items use these IDs, so renaming or moving an item does not break the reference. You can see and copy the ID from the Details panel.

Required fields are marked with an asterisk. If a required value is missing, or a value does not match the field’s rules, the form highlights the field and explains what must be corrected.

Optional fields can be left empty. Some fields may appear or become required only after another option has been selected.

A field that accepts multiple values provides controls for adding and removing occurrences. Minimum and maximum occurrence rules can limit how many values the field accepts.

Related fields may be grouped into field sets or repeated as structured items. Values inside a structured item belong together; add or remove the complete item when managing its occurrences.

Selectors let you find and reference other content, media, or predefined options. Start typing to search when the field supports search, then choose a result. The selected item remains separate content: the form stores a reference rather than copying its data.

Available actions depend on the selector and your permissions. They can include opening the selected item, replacing it, or clearing the field.

Rich text fields provide formatting, links, images, and embedded content. See the Rich Text Editor reference for its controls and supported content.