Livingdocs agency for newsrooms and publishers.

Sidora AG in Winterthur integrates Livingdocs, the component-based editorial system for media companies. We build the frontend, connect wire feeds, print and sign-in, and keep the platform running.

  • Integration from Winterthur
  • Frontend via the Public API
  • Operations and ongoing development

What is Livingdocs? An editorial system built from components.

Livingdocs is a component-based editorial system (CMS) for media companies, publishers and news portals. An article is assembled from components such as headline, lead, image, info box or video. Several people write in the same text at once, and an API delivers the content to the website, the app and the newsletter.

As a Livingdocs agency, Sidora AG covers everything between the licence and your readers: the setup for your newsroom, the frontend, the connections to agencies, image archive, print and sign-in, and day-to-day operations. You sign the licence agreement directly with Livingdocs AG.

If you need a company website rather than a newsroom, a classic CMS such as Statamic or TYPO3 is often the better fit. Our website development page gives an overview.

Livingdocs at a glance

Type
Component-based editorial system, headless
Made for
Media companies, publishers, news portals and organisations with their own editorial team
Channels
Website, app, newsletter and print via interfaces
Vendor
Livingdocs AG, commercial licence
Role of Sidora AG
Integration, frontend, connections and operations

Six modules for everyday journalism.

Livingdocs is modular. Your newsroom uses the modules it actually needs, and we add whatever is missing through the interfaces. These six form the core.

  • Article Editor

    Build articles from components with drag and drop. The editor runs in the browser, on a desktop as well as on tablets and phones.

  • Editorial Workflows

    Plan topics, assign owners, set priorities. One overview shows every story together with its current status.

  • Page Management

    Place teasers on overview pages by hand, or let rules and automatic lists fill them.

  • Digital Edition

    Self-contained products such as e-papers, newsletter issues or topic specials in a responsive layout.

  • Ticker

    A dedicated module for live coverage, built for speed when a story is only just breaking.

  • Print Connect

    Links Livingdocs to print systems such as PEIQ, Hermes, EIDOS or Interred. Online and print versions sit side by side in a split screen.

Writing the same article together, in real time.

In Livingdocs several people work on one article simultaneously. You can see who is writing where, questions are attached to the paragraph they concern, and every version is kept. The editor-in-chief sees where each story stands, and freelancers get accounts with limited permissions.

  • Write simultaneously

    Visible cursors instead of guessing who saved last.

  • Comments on the text

    Discussions sit next to the paragraph in question, not in an email thread.

  • Compare versions

    Trace every change and bring back an earlier version.

  • Roles and permissions

    Graded rights for authors, production, the editor-in-chief and guests.

AI support right inside the editor.

Livingdocs brings AI features into the writing environment: suggestions for headlines, summaries, metadata and the search for suitable images. Suggestions stay suggestions, because the newsroom decides what gets published.

  • Headline suggestions

    Several variants side by side, the newsroom picks one and sharpens it.

  • Summaries

    Lead, teaser and social media copy drafted from the article.

  • Metadata

    SEO title, description and structured data prefilled.

  • Image search

    Find suitable pictures in agency archives by meaning rather than by keyword.

Custom assistants, for example with access to your archive or in your house style, are added through the extension options of Livingdocs.

More about our AI solutions

Moving to Livingdocs in six steps.

Introducing Livingdocs affects technology and editorial work alike. That is why we start with how your newsroom works today, and we do not stop at launch but stay on for operations.

  1. Analysis

    We review the workflows, content types and existing systems of the newsroom and clarify the technical prerequisites.

    Result: Requirements and risks

  2. Architecture

    Components, data model and the links to agencies, print and sign-in are defined.

    Result: Components and interface plan

  3. Migration

    Articles, images and author profiles move over from the old system, first as a trial run, then in full.

    Result: Content in the new system

  4. Frontend

    Website and app fetch the content through the Public API. We build a new frontend or connect your existing one.

    Result: Delivery on every channel

  5. Training and launch

    The newsroom practises with real stories before the switch. We stay close during the first weeks after launch.

    Result: Newsroom works productively

  6. Operations

    Monitoring, updates, new components and adjustments whenever the way your newsroom works changes.

    Result: Continuous development

Three ways we can work together.

Livingdocs is an editorial system for larger teams. Instead of package prices we agree on an approach that matches the phase of your project, and after the analysis we set out the effort in a written quote.

  1. Assessment and concept

    You are checking whether Livingdocs suits your newsroom.

    • Requirements workshop
    • Architecture outline
    • Assessment of migration risks
    • Advice on licensing
  2. Main phase

    Rollout and migration

    The decision is made and you want a clean switch.

    • Component library
    • Frontend connection
    • Content migration
    • Workflow setup
    • Newsroom training
    • Support during launch
  3. Operations and expansion

    Livingdocs is live and you want to extend it in a targeted way.

    • Monitoring and support
    • New modules and components
    • Tuning the AI features
    • Faster loading times
    • Training on request

Livingdocs integration: agencies, print, sign-in and frontend.

Livingdocs is API-first. We connect the system with the services your newsroom relies on today and with the frontend through which your audience reads the content.

  • News agencies

    Wire copy flows straight into the newsroom planning.

    • Keystone-SDA
    • Reuters
    • dpa
    • AFP
  • Image agencies

    Research and import pictures together with their rights information.

    • Keystone-SDA
    • Getty Images
    • dpa Picture-Alliance
  • Print systems

    Print Connect brings articles into newspaper production, with online and print versions in a split screen.

    • PEIQ
    • Hermes
    • EIDOS
    • Interred
  • Sign-in and SSO

    One sign-in for the whole newsroom, including freelancers with their own permissions.

    • SAML
    • OpenID Connect
    • Microsoft Entra ID
    • Google Workspace
  • Frontend

    Website and app fetch the content through the Public API, and the frontend stays in your hands.

    • Next.js
    • Nuxt
    • Astro
    • Your existing frontend
  • Analytics and SEO

    Measure reach and mark up articles with structured data for search engines and AI search.

    • GA4
    • Plausible
    • Search Console
    • Schema.org

Operations that respect the FADP and the GDPR.

For media companies and public bodies, data protection and accessibility belong in the requirements. We configure Livingdocs and the frontend so that both are covered from the first day.

  • Hosting in Switzerland

    Frontend and backups run on servers in Switzerland. Where the Livingdocs environment runs is agreed with you and Livingdocs AG.

  • FADP and GDPR

    Retention, logs and procedures for access and deletion requests under Swiss and European law.

  • Accessibility

    We build the frontend to WCAG 2.1 AA, with alt text and a clean structure coming from the editor.

  • Standards for public bodies

    For government clients we take the Swiss accessibility standard eCH-0059 into account.

For editorial teams in media, publishing and government.

Livingdocs is built for teams that publish every day. Three groups benefit in particular, each for a different reason.

  • News portals and online magazines

    Speed and depth at once.

    • Live ticker
    • Breaking news workflow
    • Many authors
    • Stable under traffic peaks
    • Push and newsletter connection
  • Publishers and media houses

    Print and digital, several titles.

    • Print Connect
    • Separate tenants
    • Components shared across brands
    • Subscription system connection
  • Public bodies and organisations

    Trust, languages, approvals.

    • Accessibility to WCAG
    • Multilingual content
    • eCH standards
    • Four-eyes approvals

What Sidora AG brings to your project.

Sidora AG has already delivered Livingdocs for news portals in Switzerland and abroad, from a pure frontend connection to a full rollout with migration from an older CMS.

  • Web engineering since 2003

    Websites and platforms have been our trade since 2003, organised as an AG in Winterthur since 2022.

  • Experience with many CMS

    WordPress, TYPO3, Craft CMS, Statamic, Contao and Cloudrexx: we know the systems newsrooms are moving away from.

  • Frontend and interfaces in-house

    Frontend, API connections and hosting come from one team, without hand-offs between several providers.

  • A feel for newsroom routines

    We configure the system around the way your newsroom works, not the other way round.

  • First meeting on site

    The first meeting is free of charge, at your newsroom if you like, with no travel costs.

Introducing Livingdocs one step at a time.

Changing the editorial system is a big step for any media company. Articles, images and routines from many years move over, and the newsroom still has to publish on the day after the switch. That is why we plan every Livingdocs integration in stages and test each one with real content.

Livingdocs handles the work inside the newsroom, the frontend handles what readers see. We develop that frontend with the same care as any other site, as described under website development. Where data moves between systems, for instance to subscription management or the newsletter, our API development takes over.

For companies without an editorial team, Livingdocs is usually too big. Depending on scope and team we then recommend a CMS such as WordPress, Craft CMS or Contao. If you want to take AI further in your newsroom, have a look at our AI solutions.

It all starts with a conversation about your newsroom, your systems and your goals. Write to us, the first meeting is free.

Frequently asked questions about Livingdocs.

What newsrooms and publishers want to know before introducing Livingdocs, answered briefly. If your question is missing, get in touch with us directly.

Tap a question to see the answer

Livingdocs is editorial software for publishers, media houses and news portals that builds articles from components such as headline, lead, image or info box. Several people can edit one article at the same time, and an API passes the content on to the website, the app and the newsletter. The system is developed by Livingdocs AG, while Sidora AG handles integration, frontend and operations.

A Livingdocs agency sets up the editorial system for a media company and connects it with the rest of its technology. At Sidora AG this covers the component library, the migration of existing content, the frontend via the Public API, connections to agencies, print and sign-in, as well as training, support and further development. The licence remains a contract between you and Livingdocs AG.

WordPress is a versatile CMS for all kinds of websites, TYPO3 one for large multilingual sites with many permission levels. Livingdocs, by contrast, is built entirely for newsrooms: writing together in the same article, planning stories, live tickers, plus connections to wire feeds and print. For a company website it is usually oversized, while in a newsroom it plays to its strengths.

Yes. We migrate from WordPress, TYPO3, Drupal or in-house publishing systems. First we map your content model onto Livingdocs components, then we move a sample, review it with the newsroom and transfer the rest afterwards. Redirects from the old article addresses make sure that links and rankings are preserved during the switch.

Livingdocs stores and manages the content but does not display it itself. Website and app fetch articles, teasers and pages through the Public API and render them. This keeps the frontend technology open, for example Next.js, Nuxt or Astro. Sidora AG either develops a new frontend or connects the one you already have, depending on your plans.

With the Print Connect module, Livingdocs works together with print systems such as PEIQ, Hermes, EIDOS or Interred. The newsroom sees the online and the print version of an article next to each other and edits both deliberately. Other systems are connected through the Livingdocs interfaces once we have checked the data format and the prepress workflow.

Livingdocs is a commercial system with an annual licence. Its price depends on modules, number of users and volume and is agreed directly with Livingdocs AG. On top of that comes the effort for rollout, frontend and operations. We set this out in a quote after an analysis, so you can assess both parts side by side before you decide.

Inside the editor, Livingdocs suggests headlines, drafts summaries, prefills metadata such as SEO title and description, and helps find suitable pictures in agency archives. The newsroom reviews and accepts every suggestion itself. Additional assistants, for instance with access to your archive or written in your house style, are added through the extension options of the system.

Yes. Roles and permissions give freelance authors their own account, which can be limited in time. They only see their own articles, write in the same editor as the newsroom and go through the defined approval before anything is published. Control stays with the newsroom, and texts no longer travel back and forth by email.

That depends on the operating model you agree with Livingdocs AG. Sidora AG hosts the frontend and the backups on servers in Switzerland. On top of that we set up retention periods, logs and procedures for access and deletion requests so that they meet the requirements of the FADP and, where needed, the GDPR.

The duration depends mainly on the migration and the connections. A new news portal without legacy data goes live faster than a publisher with several titles, print and an archive going back many years. A schedule with milestones follows the analysis. Early test access and a newsroom that reviews from the start keep the pace up.

Let us talk about your newsroom.

Tell us how your newsroom works today and which systems it uses. Afterwards you will know whether Livingdocs fits and where we would begin.

Discuss your Livingdocs project