Passer au contenu principal
Accéder au tableau de bord
Vous ne savez pas par où commencer? Répondez à un court jeu-questionnaire pour obtenir des recommandations personnalisées.
CMS Vendors
Livingdocs logo

Livingdocs

Livingdocs

Livingdocs is a newer CMS targeting the German-speaking world, with a comparatively modern interface featuring "Google Docs"-like collaboration, at the expense of front-end capabilities and print integration

  • Modern architecture with an easily customisable editorial environment, including a DAM and some planning functionality
  • Targeted mainly at news organizations that have multiple publications, and a reasonably sized technical team to take care of customizations, willing to focus on developing their own front ends
  • Key customers include Neue Zürcher Zeitung, Süddeutscher Verlag, Handelsblatt

Likely fit

Livingdocs is well suited to Mid-sized Chains of News Organizations, who have a strong in house technical team but favor leveraging their development effort into control over their audience facing front end. Since Livingdocs offers no front end (and no advertising, subscription, or paywall services), the platform is unlikely to be a good fit to Micro or Small Publishers.

At a glance

Primary Customer Fit

Mid-Sized Chain Of News Organizations

Secondary Fit

Mid-Sized Independent News Organizations

Most Active Geographies

EMEA

Official Support Hours

The vendor says "24/7" but is unclear on what channels this refers to

Officially Supported Languages for User Interface

DE, EN, FR, IT

Third-party Language Support Available?

No

License Model

Monthly Subscription Fee based on number of users, depending on number of users € 11 - € 72 per seat per month; additional hosting/support cost for SaaS; median implementation cost ~€100k

Scope Summary

Complete editorial environment, but without visitor facing front-end, suitable for publishers in EMEA

Tech Base

SaaS Model with Azure Hosting included

Cloud Model

SaaS

Headquarters

Zürich, Switzerland

Head Count

24

What customers say

  • Editorial staff seem to welcome a comparatively easy-to-use collaborative news room environment
  • Clean modern architecture allows for sandboxed customization
  • Steady platform evolution with frequent releases bodes well for future innovation
  • Has no front-end or print integration, and therefore works best when supported by a reasonably sized in-house technical team
  • The vendor itself will not help with your front end development, and holds only very small partner network to outsource this work
  • Because the company is relatively small, customers report they aren't always as quick to take on board feature requests as they'd like, and tends to prioritize the wishes of larger customers

Background

  • Livingdocs was founded in 2015 in Zürich, Switzerland, launching with their first major customer, NZZ (the Neue Zürcher Zeitung), who subsequently invested in the company (though the majority of shares is still held by the two founders, Gabriel Hase and Lukas Peyer).
  • Livingdocs' core ambition was to deliver "Google Docs for the newsroom", with a clean and modern interface that allows editors to collaborate and comment on articles. This has expanded into a more elaborate environment that also includes DAM capabilities. Most users will work from customizable dashboards that also allow basic planning features based on tasks (which can, for instance, be organized as a Kanban board). Customers report that editorial staff is very comfortable with the interface, and generally prefer to work in the Livingdocs editor, rather than an external word processor.
  • Early customers will often still run Livingdocs themselves (on-premises or on cloud), and have in many cases extensively extended the core system, working closely in co-development with Livingdocs, the company. However, Livingdocs is now shifting more towards a SaaS model; and is also migrating from Angular to the Vue JavaScript framework. With this development, extending the core platform is also becoming more productized, and it's relatively easy to customize the offering without touching the core code. Although this will still, in most cases, require developer resources, customers can likely keep up with Livingdocs' frequent release schedule without breaking their customizations.
  • Livingdocs focuses on the editorial environment, and exposes the content through APIs to your custom front end. As a headless system, this means customers have full control over the front end; however, Livingdocs doesn't provide resources to develop these (the company has a nascent partner network of companies who can provide such services). Livingdocs customers tend to have their own in-house development staff, and cite the main advantage comes in shifting focus to audience facing technology.
  • As have other systems, Livingdocs has recently integrated AI functionality in its editor; however, interestingly, this has been done as a plugin, which means customers should have full control over which third party services to use for this (or to develop their own).
  • While the product is popular in the DACH (Germany, Austria, and Switzerland) area of Europe, it has not yet made major inroads elsewhere. Staff is steadily but slowly expanding, and as a result the evolution of the platform isn't always as rapid as customers would like to see.

Portée de l'ensemble (telle qu'indiquée par le fournisseur)

Plateforme de base, c.-à-d. intégré au produit (oui/non/version bêta) Module complémentaire (oui/personnalisé/tiers)
Cycle de vie du contenu : créer/classer/éditer/approuver/publier/réutiliser/archiver/éliminer
Oui
Gestion de base des ressources numériques/vocales/médiatiques
Oui
Prendre en charge l'édition imprimée
Non
Tiers
Republication simple dans les médias sociaux
Non
Personnalisé
Modules optionnels : formulaires/sondages/widgets sociaux/etc.
Oui
Tiers
Bibliothèque de connecteurs (connecteurs prêts à être utilisés, API, etc.)
Oui
Réseau de livraison de contenu intégré (avec protection contre les attaques DDoS)
Oui
Inscription de l'utilisateur
Non
Gestion et fourniture des abonnements (version numérique)
Non
Gestion des abonnements (version imprimée)
Non
Personnalisation
Non
Gestion des annonces (version numérique)
Non
Gestion des annonces (version imprimée)
Non
Gestion de l'application mobile
Oui
Recherche sur le site
Oui
Planification du contenu et de l'attribution
Oui
Gestion vidéo/OVP
Oui
Gestion audio/Baladodiffusion
Non
Visualisation des données
Non
Tiers
Annonces classées
Non
Commentaires/Fonctionnalités de la communauté/
Non
Tiers
Production et gestion du bulletin d'information
Oui
Tiers
Notifications et alertes
Oui
Test A/B
Non
Personnalisé
Référencement
Oui
Gestion de plusieurs titres avec héritage variable
Oui
Mise en page complexe et clonage de sous-sites/sous-sections
Oui
Services améliorés de RA/RV
Non
Documentation publique
Oui
Forums en ligne pour les utilisateurs/partenaires
Non
Réunions régulières des groupes d'utilisateurs
Oui
Interested in the CMS?
Go to vendor
Quitter et perdre la progression?
En quittant cette page, vous perdrez toute progression dans la leçon en cours. Voulez-vous vraiment continuer et perdre votre progression?