Skip to content
Strife Docs

Reference Fields

References

The References editor lets you connect existing documents from other collections directly into your content, enabling structured reuse instead of duplication.

Functionally similar to adding Chapters, the References editor differs in that it does not create inline content bound to the current document. Instead, it allows you to reference one or more existing documents from a specified collection. This makes it easy to compose content from shared building blocks while keeping a single source of truth.

If needed, editors can also create a new document in the target collection on the fly and immediately reference it—without leaving the current editing context. All referenced documents remain fully editable and can be opened and updated directly from where they are referenced, ensuring a smooth and efficient workflow.

This approach supports modular content architectures, reduces duplication, and keeps related content consistently up to date across the system.

Settings

In addition to the basic settings, this section provides information about unique settings and configurations specific to this field.

Note:

You can find a comprehensive list of all basic settings in the 'Overview' section.

OptionDescription
Restrict types
Restrict the collections that can be added to this reference editor
Size
Optional setting for limiting the number of references allowed

Define with JSON

When defining templates using JSON, this field is represented using:

  • Component Name: str-references
  • Type: references
  • Reference ID: str-references

The settings above map into the editor object inside the JSON definition.

JSON
{
  ...
  "editor": {
    "name": "str-references",
    "type": "references",
    "propertyName": "...",
    "attributes": {
      "hint": "...",
      "size": 3              //Any number
    },
    "options": {
      "availableTypes": [...] //Array of the collection's normalized template name
    }
    ...    
  },
  ...
}

Live preview

Note:

This field does not have any default Strife Web Components. Custom live preview implementations are fully supported.

Note:

For more information on live preview and Strife Web Components, please refer to the Live preview documentation.