Content entries

Team members create content entries based on the content types that have been configured in a project. Entries represent structured content pieces (such as article, events, or products) that can be accessed by APIs for use in Canvas compositions or in any digital channel or application.

An entry is structured content that represents a piece of content in a design-agnostic way. A component or composition describes the experience layer by defining which concrete UI component should be used to show particular content.

By connecting the fields of an entry to the parameters of a component you define how the content is displayed in a certain context. For example, you could show the same article entry in a hero, a card, or a list component. Which fields of an entry are shown can be different for each use case.

Add or edit entry#

Access entries by going to Experience > Entries in the application navigation menu. If you click the Add an entry button, a list of available content types is shown.

Select an available content type to create your first entry.

Once you select a content type you will see the entry editor screen showing the fields available.

An example of an entry ready to be authored.

There are some fields that are common to all entries, and some that are dictated by how the content type is configured. Global elements include:

  • Name: A value extrapolated from the display name entered by the entry author.
  • Slug: Similar to name, this is a value extrapolated from the display name entered by the entry author.
  • Save: This will save the entry as a draft.
  • Publish: Clicking this will save and publish it.
  • A menu, accessed by , manages several properties:
    • Manage data resources: Opens the data resource panel in the side rail.
    • View source JSON data: Opens the source panel in the side rail.
    • History: This opens the history panel in the side rail.
    • View properties: Opens the properties panel in the side rail.
    • Duplicate: This option creates an additional content entry with the same data as the original in a draft state. After selecting it, you will be taken to the duplicated entry.
    • Edit content type: Selecting this will open the content type for additional configuration. Some roles may not have permission to edit content types.
    • Delete entry: This will delete the entry.

There is also a side rail for quick access to functionality.

The side rail sits to the left of the screen and allows you to view details and resources connected to the current composition.

It contains five elements:

The structure icon in the side rail
Data resources
The data resources icon in the side rail
The source icon in the side rail
The history icon in the side rail
The properties icon in the side rail

In the structure section shows the hierarchy of field groups and fields.

An example view of the structure element.

The data resources section provides features to manage your data sources and data types from within your entry.

An example view of the data resource element.

The source element shows you the references of your entry as JSON data. You can see entry data:

  • As it will be saved as JSON.
  • As it would be returned for use in a consuming application, with data resources applied.
An example view of the source element.

Here you can see drafts and published versions of your entry. If you make several changes within the same day, those updates will be collected together as the number of versions created on the day. Selecting a revision will load the composition as "read only" with the references as they were at that point in time. You can:

  • See what was changed, when, and by whom.
  • Restore this version (which will create a new version with the associated references).
  • Go back to the current version.

Data is saved for the last 30 days.

This is useful when there are multiple people collaborating on a single entry, or previous version data needs to be reviewed. You should note that this isn't a full audit feature. Uniform does track the references that are saved as JSON. It doesn't save the data coming from external sources. If you're reviewing a pattern, only the references will be saved.

An example view of the history element.

Within the properties section of the structure panel you will see some basic information about your entry, including the:

  • Entry slug
  • Entry ID
  • Created, modified, modified by, content type, and last published dates. Clicking on the content type will open it for editing.
An example view of properties element.

Once entries have been created, they're listed at Experience > Entries. From the list you can:

  • Toggle between card and list view
  • Sort the list by:
    • Name, A-Z
    • Name, Z-A
    • Modified, newest first
    • Modified, oldest first
    • Created, newest first
    • Created, oldest first
  • Filter the list by state:
    • Published
    • Draft
    • Modified
  • Define how many results appear on each page:
    • 10
    • 20
    • 50
    • 100
  • Filter by type. This will filter by the content types configured for your project.
  • Duplicate an entry
  • Delete an entry
There are several management options available from the entries page.