The un-CMS for the next wave of digital technology
The age of monolithic content management systems (CMS) is finally over. These beasts brought with them a lot of weight and made numerous assumptions that no longer fit with today’s world. Myriads of digital channels, content-types, devices, screen-sizes and user interfaces make it impossible for a single system to handle all things content in a sensible way.
Recent trends have seen the rise of paradigms like headless and decoupled CMS. The drastic metaphor — think of a human body with a head chopped off to grasp the consequences — indicates an architectural shift towards an API-driven, microservices, serverless and cloud-based content management system landscape. Only this allows to deliver content as a service (CaaS), optimised for performance, search engines (SEO), distribution, and time to market.
In this new landscape, the traditional CMS is reduced to its proper role as a fancy editor for content creators, i.e. the human beings on the backend side. In a decoupled setup, it then just exports the pure data of the content to other systems. This is what Paperboy does. Do one thing, and do it well, in classic UNIX-style philosophy.
Paperboy sits between the decoupled CMS, e.g. Adobe Experience Manager (AEM) or Wordpress, and the content delivery network (CDN). It consists of an army of microservices that import the exported data of the CMS, process it, and hand it over to the CDN. This includes image processing and template rendering.
Paperboy utilizes microservices to be able to react quickly to business and technology changes. It scales on demand with serverless architecture, and allows to build a mobile-first, high performance, SEO and reach optimized frontend. At the same time, it supports editors as much as possible. For example, it automatically creates the necessary image formats for different screen sizes and bandwidths.
Paperboy is the essence of our deep knowledge of how to create the best mobile experience for users — the primary way users consume content today. Not only implementing approaches for real and perceptive speed of loading times like Optimistic UI, but also with distribution to other relevant specialised targets like Google AMP, Facebook Instant Articles, Amazon Alexa and news aggregators.
With kiekmo and aio, our first client products are already up and running on Paperboy. We also maintain a backlog of possible features that would be implemented as soon as our clients need them, and naturally made available to all Paperboy clients.