Defining Story Content Types

Text-heavy content types in CUE are generally referred to as stories or articles. A story typically consists of a long flow of formatted text stored in a single field, accompanied by other shorter text items such as a headline, a title, a lead text plus various items of metadata and a set of relations to other content items: images, videos, other stories and so on. CUE supports two different ways of modelling these structures:

  • Escenic legacy stories: this is the way stories were defined for the Escenic Content Engine.

  • Native CUE stories: this is a newer, more flexible method of defining stories, and is the recommended method.

You can freely choose which kind of story content type you want to use; both are fully supported. If you have existing publications containing Escenic legacy stories, then you can continue to use them as before. If you are starting from scratch then you are strongly recommended to use native CUE stories for the following reasons:

  • Greater overall flexibility (due to extensibility)

  • Better structural control (the storyline templates let you, for example, specify required elements)

  • Better editing experience

  • Planned functionality improvements