1 of 35

Dev Webinar

release-2025-07

2 of 35

Overview

  • Welcome!
  • Q&A at the end
  • Technical release notes
  • Feedback -> marc@livingdocs.io

Recording of the webinar | Passcode:

3 of 35

Packages

  • News Agencies (30’)
    • Intro
    • News Agency Screen
    • System Metadata Plugin Priority
    • Import Flow
  • Media Center:
    • Improve image search and navigation (10’)
    • Deletion routines (10’)
  • Page Management: Rubrics (10’)
  • Target Length Extensions (5’)
  • Command API: additional commands for publish control (5’)

This slide is hidden!

4 of 35

Features

5 of 35

News Agencies: Introduction

We're offering a dedicated «News Agencies» module to integrate news agencies and their respective workflows into Livingdocs, enabling editors to work with them effortlessly.

  • Automatic and manual news agency flows
  • Extend the Import API for News Agency support
  • Tailored News Agency Screens where editors can view and search specific reports and easily create articles based on them.

6 of 35

News Agencies: Disclaimer

While this release introduces the foundational components for integrating news agency workflows into Livingdocs, the feature is not yet ready for full rollout.

Further development is in progress, and we’ll keep you updated along the way - notifying you as soon as it’s ready for you to explore.

7 of 35

News Agency Screen & Import Flow Demo

8 of 35

News Agency: Manual Flow

9 of 35

News Agency: Manual Flow

The manual flow lets users decide which news agency reports should be turned into articles.

  1. Import: News agency reports are imported via the Import API.
  2. Triage: Imported reports are displayed on a dedicated news agency screen.
  3. Article Creation: On the news agency screen, users can copy a report into a regular article. This creates an independent copy that no longer receives updates from the original report.
  4. Editing: The regular article behaves like any other article in Livingdocs.

10 of 35

News Agency: Auto-publish Flow

11 of 35

News Agency: Auto-publish Flow

The auto-publish flow requires no user-interaction. It enables publishing news agency reports automatically.

  1. Import: Auto-publish reports are imported via the Import API. The metadata property autoPublish must be set.
  2. Triage: Auto-publish reports do not appear on news agency screens.
  3. Article Creation: The report is automatically copied into a new article and published.
  4. Editing: Auto-published articles are read-only. They continue to receive updates from the original report. Users can convert them into editable articles.

12 of 35

News Agency: Manual and Auto-publish Flow

13 of 35

Media Center: Improve image search and navigation

Authors need to search for and select the best images for their stories effortlessly. For that purpose they want to view more images simultaneously and navigate through them with ease.

Demo: Marc H.

14 of 35

Media Center: Improve image search and navigation

15 of 35

Media Center: Improve image search and navigation

16 of 35

Media Center: Improve image search and navigation

New displayfilter for li-boolean

17 of 35

Media Center: Deletion routines

Image agencies produce a constant daily stream of incoming images that require management. We need a mechanism to ensure that only valuable and actively used images are retained, while the rest are systematically removed. This approach supports more effective image research and helps meet contractual obligations.

18 of 35

Media Center: Deletion routines

Deletion routines must be configured individually for each mediaType that you would like to delete entries from. The main config is the filters property which is an array of base filters. You will probably want to include metadata filters for agencies combined with a created date.

Media library entries which are “used”, meaning that they are stored in archive, referenced, or have appeared in a publication, will not be deleted.

19 of 35

Media Center: Deletion routines

Example roll-out:

  1. Run the July release livingdocs-server migrate up and livingdocs-server release-2025-07-populate-reference-ids commands to populate the states and references of media library entries
  2. Modify the CDN setup (e.g. Imgix) to point to the server endpoints instead of the S3 bucket (if not already done)
  3. Update the project config to enable use2025Behavior (if not enabled)
  4. Manually correct any metadata states, for example if archive was used for validity then convert this to use an li-boolean metadata property instead
  5. Once everything is confirmed to be running smoothly then update the project config to enable the deletion routine(s)

20 of 35

Rubrics

Many of you are structuring their pages after departments or a similar categorisation scheme.

With the introduction of «Rubrics», we’re aiming to provide a flexible but also standardized approach to associate articles with pages.

21 of 35

Rubrics

  • You can assign a rubric to each article, by selecting the rubric from a nested tree of options.
  • When a rubric is selected for an algorithmic teaser, articles with this rubric or with a sub-rubric of will appear in this spot
  • Example: A story is assigned to the rubric «AI», so the story automatically appears in all algorithmic teasers where either «AI», «Digital» or «Tech» was selected.

Rubrics

Politics

Tech

Sport

Digital

Energy

AI

22 of 35

Rubrics

23 of 35

Rubrics

  • Rubrics have a similar technical foundation like menus: They are based on Data Records with an li-tree metadata property, but they have a different purpose
    • Menus: Describing the navigation structure in the frontend and their relation to pages
    • Rubrics: Describing the logical hierarchy of topics and associating articles with sections on pages
  • Once configured, rubrics can be managed by users in the Livingdocs Editor

24 of 35

Rubrics

  • Rubrics are in an experimental state and we’re not certain that it solves most use cases yet; configs and behaviors might change in the near future
  • Since rubrics are closely related to algorithmic teasers, we’d like to gather feedback from customers using such a setup first. In case you do, please contact your account manager and we schedule a meeting to figure out how it fits your needs.

25 of 35

Target Length Extensions

Since some newsrooms still think in lines instead of characters and want to be able to use T-shirt sizes or exact numbers respectively we extended the capabilities of the target length plugin.

Demo: Marc H.

26 of 35

Target Length Extensions

Two new config options:

  • unit (character, lines)
  • showExactCountCheckbox

* lineCountFraction needs to be set with unit lines

{

handle: 'targetLength',

type: 'li-target-length',

ui: {

config: {

showExactCountCheckbox: true,

unit: 'lines',

steps: [

{ label: {en: 'S', de: 'Klein'}, value: 5 },

{ label: {en: 'M', de: 'Mittel'}, value: 10 },

// ...

]

}

}

}

{ // editorSettings

textCount: {

lineCountFraction: 39.5

}

}

27 of 35

Command API: additional commands for publish control

To support automatic flows for articles with publish schedules or embargoes, we've added publish control commands to the Command API, making the API more comprehensive.

Demo: Robin

28 of 35

Command API: additional commands for publish control

29 of 35

Deprecations

30 of 35

Deprecations

  • Deprecate Postgres v13 as it’s end of life in November.�Support for it will be removed in release-2026-01.�
  • The endpoint GET /api/:apiVersion/channelConfig is deprecated and /api/2025-05/channelConfig is the last api version that supports it.�Please use /api/2025-07/projectConfig instead.

31 of 35

Breaking Changes

32 of 35

Breaking Changes

  • Command API operations publish, unpublish, and addPublishSchedule can only be used as the last operation in a request and are mutually exclusive
  • The content type handle liNewsAgencyReport can no longer be configured manually. It is a reserved content type handle and should not be used.
  • The Livingdocs Server config properties server.* has been moved to httpServer.* in release-2022-09. In this release we’ve enforced the new config as breaking change.
  • The terms blacklist and whitelist have been deprecated in release-2025-01 and this is now enforced by a breaking change.
  • The features li-images and li-videos got removed. Please use li-media-library.
  • Multi-Channel Setups are not supported anymore.�The server now throws errors when one tries to create a second channel for a project.

33 of 35

Q & A

34 of 35

Next Dev Webinar

16.09.25

14:00 - 15:00

35 of 35

Thank you!

Livingdocs ∙ Tellstrasse 31 ∙ 8004 Zürich ∙ www.livingdocs.io