Linked Content Field Types

Understanding Linked Content

• Every linked content field stores a reference name pointing to the content list.

• Shared Content: References existing content lists, either the entire list, or specific items in the list. If specific Items are being referenced, the IDs of those content items are stored in a separate field, specified in the linked content field's properies.

• Nested Content: Creates child content that belongs exclusively to the parent.

• There different render types to handle various UI types (dropdown, grid, checkboxes) for different use cases.

Let's go through the various types of linked content fields that you would need.

Best Practices for Linked Content

• Choose Shared when content needs to be reused across multiple items

• Choose Nested when content is specific to a single parent and should be deleted with it

• Use Grids for managing multiple relationships or when you need sorting/filtering

• Use Dropdowns for single selections from shared lists

• Use Search List Box when dealing with hundreds of items

• Remember that dropdown, checkbox and search-list-box fields need companion hidden fields for storing values

Shared - Dropdown List

Select a single item from a content list via dropdown

How it works:

• Stores the reference name of the linked content list
• Requires two companion hidden fields:
  • Value field (Integer): Stores the selected item's ID
  • Text field (Text): Stores the display text
• Perfect for 1:1 relationships

Common uses: Author selection, primary category.

Shared - Checkbox List

Multiple selection using checkboxes

How it works:

• Allows selecting multiple items from a content list
• Stores selections as comma-separated values
• Can display in multiple columns for better UX
• Great for many-to-many relationships when there are fewer than 50 items.

Common uses: Tags, product features, multi-select-categories, skills, amenities

Shared - Search List Box

Searchable list for large content collections

How it works:

• Provides search functionality for large datasets
• Better UX when dealing with hundreds/thousands of items
• Customizable display columns
• Checkbox List can be converted to this if the parent list grows too big.

Common uses: Product catalogs, user directories, location lists, extensive tag libraries.

Nested - Grid

Grid interface for creating child content unique to each parent item.

• Creates new content that belongs only to the parent
• Each parent item gets its own unique child list
• Child content is deleted when parent is deleted
• Perfect for true parent-child relationships

Key characteristics:

Common uses: Carousel slides, FAQ items, product variants, testimonials, timeline events, accordion sections

Nested - Link

Simple link for nested content without grid interface

How it works:

• Creates child content unique to the parent
• Simpler than grid - the link will take the user to the content on its own screen.

Common uses: Creating a link to a relavent shared list as a convenience for users.

Shared - Link

How it works:

• Creates a reference to existing shared content
• Simpler than grid - just establishes the relationship
• Content must exist in a shared list or item

Common uses: Default settings, global configurations, shared headers/footers

Shared - Grid

Grid interface for managing relationships with existing shared content and you need to show the whole list. 

Key characteristics:

• Links to content that exists independently
• Multiple items can reference the same shared content
• Supports sorting, filtering, and customized columns
• Content must be created separately in a shared list

Common uses: team members, shared resources, product ingredients, office locations.