Export Page

This developer-centric technical overview of Content Authoring complements the more end user-centric Content Authoring Introduction that describes the content management problem along with the Amplience "Content Authoring" solution. Here we present in technical terms how our headless CMS provides the benefits associated with decoupled content management, and we outline the relationships between the Content Authoring components.

 Read about Decoupled Content Management...

Decoupled Content Management

The Amplience "Big Content Cloud" provides a headless Content Management System (CMS), which means that the presentation of content (e.g. as HTML web pages) is decoupled from the content structure in the CMS.

Most CMS systems present three major challenges:

  1. They focus on managing your website rather than your content.
  2. They monopolize the presentation layer, making cross-platform publishing and custom user experiences difficult to create and manage.
  3. It is difficult to add new channels such as mobile apps and microsites without duplicating your content.

Our presentation- and platform-agnostic solution aims to solve these problems by decoupling our back-end content storage and management (the Content Authoring CMS) from your front-end multi-channel presentation. The Content Authoring tool facilitates the storing, editing and publishing of content, but also addresses a number of content management problems such as content reuse and responsive design.

The benefits of a headless CMS include:

  • Giving front-end specialists full control over the user experience using native tools.
  • Shifting display logic to client side while the server-side CMS concentrates on delivering content.
  • The ability to create once and publish everywhere.
  • Organization and structure of content in a logical way that is not restricted by fixed predefined templates.
  • A relatively non-technical user interface.

With Content Authoring you can:

  • Describe your content types using the JSON Schema open standard, which defines the content and structure that your presentation layer needs to capture.
  • Use tools that provide user-friendly interfaces for populating those content type schemas with content.
  • Deliver content to your presentation layer in a platform-agnostic way using REST APIs that deliver standard formats including JSON, JSON-LD and Markdown.
  • Devise front-ends (rendering kits) that turn the platform-independent content into HTML web pages, native user interfaces, and more.
  • Utilize Dynamic Imaging to deliver the right size and quality images for different devices and screen sizes.

The decoupled content management is illustrated by the following diagram, in which the dashed line indicates point at which the front-end "head" is decoupled from the back-end CMS (thus making it headless).

 See the Content Authoring Components...

Content Authoring Components

The following diagram shows the Content Authoring components, their relationships and interactions. In short, Your App calls the API which fetches Content that is based on Content Type Schemas.

Note that Content Authoring uses the concept of content "cards" (bottom-right of the picture) that provide visual representations of the content for easy identification by content authors. These cards are not necessarily representative of how the content will look when delivered by your application to different devices (desktop, tablet or mobile phone) with different screen sizes; they are merely a visual aid for navigating content. There are many built-in cards, and you can also build your own.

  • No labels