In this article, we cover the editor of stories, where editors spend most of their time and effort:
Language-driven settings
Stories follow the language-driven editorial workflow: for each language, editors manage a different variant of stories.
The story editor page reflects that language-driven behavior. It groups the story settings — within the red framework in the screenshot below — whose value depends on the language. Except for the Entity code field, all other fields are related to the language you chose in the translation section.
Translations
The translations section — within the red framework in the screenshot below — allows editors to:
Choose the story language
For each language, visualize the story workflow status:
Published
Reviewed
Unpublished
There's no status for languages that have no story variants.
When a system language is removed for an existing story, the Language removed symbol
displays near that language. E.g., the ee-GH language in the screenshot below.
Title and subtitle
On top of the story body, editors can set the title and subtitle — "The story of Alpha" and "Where it all began" in the screenshot below — for the selected language.
Main properties
Like for any other entity, the story's main properties are:
Entity code: The unique identifier of the story. This is the only field that doesn't depend on the selected language.
Localized entity code: The unique identifier of the story for the selected language.
Slug: The human-readable unique identifier of the story. It can be different per selected language.
Content date: Auto-filled when the story is first published in the selected language. Editors can change the auto-filled value.
Body
By selecting the add button
in the body area, editors can add many types of content: text, photos, albums, documents, and any available custom entity.
Also, they can add built-in and custom elements like quotes, tables, or embedding links. Developers can add further elements to meet the editorial needs.
On the bottom of the body area, there's the word count for:
Title
Subtitle
Body
Total word count
SEO recommendations
While writing the story, the SEO recommendations tab shows editors how well the story is doing in SEO for the language they selected.
In the case of some improvements detected, a warning icon 
and a short explanation guide editors to improve SEO performance. Also, a red message displays when the story has:
No title
No slug
Empty body
History
Like for any other entity type, the History tab provides editors with snapshots of the many versions of the story for the selected language.
Hovering over a history version, the Compare button displays, which allows editors to compare the selected snapshot with the latest story's version.
In the case of changes between the compared versions, what editors have added, changed, or removed is highlighted. E.g., in the screenshot below, the in version 65, the story part 3 was added compared to version 55.
Finally, when comparing with the latest published version, it's possible to restore the latest published version:
Language-independent settings
Regardless of the language-driven editorial workflow, stories have settings that apply to all languages. This is in common with any other entity type.
General settings 
Editors can select:
Authorization group: Select the authorization group that editors must have to edit the story.
List availability: Select whether the story must be included into lists that the front-end queries. See List Availability for more information.
Context and tags 
Editors can select:
Context: Text that appears above an article on the front-end. It's a small, but important piece of text which highlights the key features of the content.
Tags: Story's taxonomy. E.g., stories around football competitions may have the following tags: goal scorers, match report, manager comments.
Promotion 
Editors can promote the story's visibility by leveraging:
Feature the content: Flag that makes a story featured. This flag informs the front-end that the story's visibility has a higher priority than not-featured ones.
Add to selections: Add the story to one or many editorial selections.
Relations 
Editors can relate the story to other entities regardless of their type.