What's next?

Editing stories
  • Updated

In this article, we cover the editor of stories: where editors spend most of their time and effort.

Topics covered here:

Building a story

FORGE Back Office is where editors create content by combining text, visuals, and structured parts into a story.

When creating a new story, the story editor displays:

Once you specify the title, the story gets three identifiers:

  • Entity code: Unique identifier of the story across the FORGE instance. It's generated by FORGE and cannot be edited.
  • Localized entity code: Unique identifier of the story across the FORGE instance for a specific culture — English (GB) in the screenshot below. It's generated by FORGE and cannot be edited.
  • Slug: The slug is part of the published story URL; it's unique across the FORGE instance, human-readable, and different for each story translation. It's generated by FORGE but can be edited for SEO optimization. 

Next, add text and built-in and or custom entities, defined by the producer. The screenshot below shows the available custom entities: Promo, Events, Team, Player, Federations, BrightcoveVideo, KEPlayerVideo, VimeoVideo, YouTubeVideo, OEmbed, Quote, Minutely, LiveLike, and Table.

For example, after writing some text, add a player — a custom entity:

For example, after writing some text, you can add a player — an editorial custom entity.

Configuring a story

Once you've inserted the content into your story, tune its configuration:

  • Thumbnail: Assign a thumbnail that previews the story in a list:
  • Taxonomy: Build the story taxonomy by:
    • Assigning tags to categorize the story to:
      • Make it automatically belong to editorial selections.
      • Assign it to presentation modules — see Presentation for an overview of the modules.
    • Defining relationships with other entities to let the front-end display them near the story.
  • Promotion: Decide whether the story must belong to an editorial selection or be featured — see Editorial lists and featured content for more information.
  • SEO: Check whether the story is compliant with the SEO criteria that the producer configured — see Search Engine Optimization (SEO) for more information.
  • Sharing: Once the story is published, configure on which social networks the story will be shared.

Publishing and translating a story

On the top-right of the story editor, select the PUBLISH button to make the story available on the front-end:

For translating the story, go through the following steps:

  1. Select the Translate button:

  2. Select the language in which you want to translate the story (e.g., German):
  3. A new story is created with the same Entity Code but dedicated Localized Entity Code and Slug. Translate each part because, by default, the new localized story contains the same content as the one to be translated:

Related articles