What's next?

Create and manage localized editorial selections
  • Updated

In this article, we cover how to manage localized editorial selections.

Topics covered here:

What's a localized editorial selection?

Suppose your job is to prepare content on a multilingual website that shows the result of the final France vs. Spain match. Then, suppose France is the winner.

As an editor, you want to display content that describes how the final went. You aim to have the French version of the website celebrating the win while the Spanish version narrates the fans' disappointment.

Given a topic (i.e., the France v. Spain final), a website may require different content per language. For example, celebrating a win or reporting disappointment to provide fans with a tailored and localized experience.

Localized editorial selections cover this scenario. The French version of the editorial selection France-Spain Final contains content that narrates the joy and excitement for the win. On the other hand, the Spanish version of the same editorial selection list emphasizes the disappointment and frustration of ‌Spanish fans.

Create a localized editorial selection

  1. In FORGE Back Office, select Editorial Selection in the left menu:
  2. In the top-right of the editorial selection list page, select the New button and choose the option Editorial Selection (localized):

    The editorial selection detail page displays:

    1. Localizations — List of the system languages in which the editorial selection can be localized.
      Boxes b, d, e, and f refer to the selected localization in box a. For example, when selecting en-us, all the following sections refer to the English (US) localization of the editorial selection:
      • Flag (box b)
      • Item list (box d)
      • Main properties (box e)
      • Status (box f) 
    2. Flag of the currently selected localization — By default, the first one.
    3. Title of the editorial selection — It displays on the list page.
    4. Item list — Add entities to the editorial selection. See Manually add items section.
    5. Main properties — Properties that identify the editorial selection:
      1. Entity type Editorial selection (localized) — Read-only field that reports the editorial selection entity type.
      2. Entity Code — Unique code of the editorial selection.
      3. Localized entity code — Unique code of the selected localization.
      4. Slug — Unique human-readable code of the selected localization.
      5. Content Date — By default, the date when the editorial selection was first published, however, the date is editable.
      6. Data Source — Only available when the editorial selection comes from an imported feed. It displays the name of the feed source.
    6. Editorial workflow status of the editorial selection — It can be New, Unpublished, Reviewed, and Published.
    7. History icon — Select to view the history of the editorial selection.
    8. Icons of:
      • Selection and Autofill — See step 4.
      • General Settings — See step 6.
  3. Write the editorial selection in box c.
  4. Select within box h to set up the autofill rules:

    Once the number of items is at least 1, the Content Types, Context, and Tags sections display. Then editors can define the autofill rule that applies to all localizations.
    For example, in the screenshot above, the rule autofills each localization with up to two stories with alpha week as Context, alpha as Tags, and the localization language.

    Tips:

    • In brackets, the context label displays the context slug. E.g., in the context label, alpha week (alpha-week), the in-brackets alpha-week is the slug.
    • Find tips for tags in the Content taxonomy article.
    • When adding tags to autofill the editorial selection, select whether the to add entities:
      • Matching at least one tag:
      • Matching all tags:

    Editors can set whether the maximum number of automatically added items is also the maximum number of items in the editorial selection:

    When the toggle is turned on, reaching the maximum number of items implies that any new added item — either manually or automatically — removes the last item. This applies to all localization.

    Info: Administrators need to assign editors the following permissions to enable them to set and manage the maximum number of items:

    • SetSelectionLimitCommand
    • SetSelectionMaxItemsCommand
    • UnPinSelectionItemCommand
    • UnsetSelectionLimitCommand

    Note: If you're only manually adding entities to the editorial selection, skip the autofill rules setup. Still, set the maximum number when needed, as it's independent of the autofill.

  5. In the Item list box, for autofilled items, hover over the item you want to replace with an entity and select Pick item:

    In the entity selection window, select the entity.

    Note: The selected entity is automatically pinned.

  6. Select within box h to set up the authorization groups needed to see the editorial list in FORGE Back Office:

    In the example above, only users assigned to the alpha-editor authorization group can see the editorial selection you're creating.

    Note: If you don't plan to restrict ‌editorial selection visibility, skip the authorization groups set up.

  7. In the Localizations box, select the localization to edit:

    • Add items to the localization — See paragraph Manually add items for more information.
    • Optionally, set the content date for the localization.
    • Select Preview to get a preview of the localization based on the manual selection and autofill rules:
    • Select Publish to make the localization published on the front-end:

      After publishing, you get the localization (e.g., en-us) published:

Manually add items

  1. In the Item list box, select Add items.
  2. Select what type of entity you want to add, and pick the list of entities to add. Repeat the selection for each entity type.

    Tip: When adding photos and documents to the editorial selection, editors can upload other photos and documents directly in the entity selection page.

  3. Move the added entities to reorder them.
  4. Pin one or more added entities to make sure that no further changes to the editorial selection can change their position.
  5. Hover over an added item to:
    1. Display and edit contextual fields.

      When selecting the contextual fields icon, the Contextual fields tab opens in the Main properties box. It allows overriding the item's fields when it displays within the localization. Which fields editors can override depend on the entity type; e.g., for stories, below is an example of the Contextual fields:
    2. Open the entity details page in a new tab.
    3. Remove the entity from the editorial selection.

Empty slots: side case and solution

Suppose you manually added five items and didn't set an autofill rule:


Then, suppose you pin the fifth item (Alpha Friday):

Eventually, delete the second, third, and fourth items. This creates three empty slots and a warning icon in the top-right highlights the side case:

The editorial selection preview lists only two slots where the pinned item is in the second position (not in the fifth one):

There are two ways to overcome that incoherence:

  • Hover over each empty slot, select the pick icon, and add an item.
  • Define an autofill rule for a maximum number of items equal to or greater than five, so that three autofilled items fill the empty slots.

Publishing behavior

Schedule publishing and unpublishing

By selecting the three dots on the right of the Preview button , editors can select to schedule either the editorial selection, publishing or unpublishing:

Once you select Schedule publishing, a popup window displays, which allows you to set the​ following:

  • Year
  • Month
  • Hour
  • Timezone
  • Hour format

Bulk publishing of still unpublished items, tags, or context

When editors publish an editorial selection that includes some still unpublished items, tags, or context, the following popup displays, which lists unpublished or not-visible items, unpublished tags, and context:

In the example above,

  • alpha player is a photo whose visibility is off for translation en-gb
  • alphanews is an unpublished tag
  • alpha is an unpublished context

Editors can:

  • Select the alphanews tag to publish it together with the editorial selection. Otherwise, editors can deselect the alphanews tag and keep it unpublished when publishing the editorial selection.
  • Select the alpha context to publish it together with the editorial selection. Otherwise, editors can deselect the alpha context and keep it unpublished when publishing the editorial selection.
  • Select the alpha player photo to switch its visibility on for en-gb when publishing the editorial selection. Otherwise, editors can deselect the alphanews tag and keep it unpublished when publishing the editorial selection.

Tips: Remember that the front-end doesn't display entities when filtered by unpublished tags or context. In the example above, if editors deselect the alpha tag and publish the editorial selection, the auto-fill doesn't include entities with that tag.

By selecting the button, editors publish the editorial selection and selected items, tags, and context.

Publishing and archiving

Editors manage localized editorial selections at localization level: each localization goes through its own independent publishing workflow.

For example, if the English and Italian localizations are published and editors modify the Italian one, only this latest localization transitions into the Reviewed status. Instead, the English localization remains published and unchanged.

Instead, after archiving the editorial selection, all localizations are archived.

Related articles