Reference Architectures, 1.0.0

Headless content delivery

For more general information on how FirstSpirit works, refer to Crownpeak CMS (FirstSpirit).

Product description

To seamlessly deliver content to and reuse it on multiple digital channels and touchpoints with our hybrid publication capabilities, headless content delivery decouples the content management system (FirstSpirit) from the presentation layer. This allows you to deliver content anywhere with speed and agility. In turn, it enables you to provide exceptional digital experiences on websites, mobile apps, IoT devices, and any emerging technology with modern web APIs (using REST and GraphQL).

In a headless scenario, the content from CaaS can be fetched in a predefined JSON format either via REST or GraphQL API. URLs of media files stored in Amazon S3 can also be fetched from CaaS.

Information about the contents’ structure, maintained by the editor in the FirstSpirit project, is stored in the Navigation Service. This data can be consumed for routing in the target touchpoint application.

With Omnichannel Manager (OCM) FirstSpirit brings a What-You-See-Is-What-You-Get (WYSIWYG) editor experience to third-party applications.

The following graph shows an overview of the FirstSpirit components in a headless scneario.

Content deployment

When using CaaS in combination with CaaS Connect, content changes are automatically synced to CaaS. Media files are saved automatically to an Amazon S3 bucket.

Scalability and performance consideration

To improve performance and reduce requests to CaaS and Navigation Service, it is highly recommended to implement a frontend caching mechanism according to your specific needs.

Security and compliance guidelines 

Security and compliance guidelines vary depending on your individual use case. The following provides a selection that should be widely considered.

Decoupled systems offer the advantage that a potential attack or downtime on the delivery layer (i.e. CaaS) does not result in CMS downtime, and content deployment can be directed to an independent system.

Conversely, an attack or downtime affecting the CMS only disrupts the editors' workflow without impacting the performance or availability of touchpoints.

It is also important to keep in mind that only the FirstSpirit server is equipped with a backup strategy. Therefore, when data loss occurs on the CaaS side, only data from FirstSpirit can be redeployed to the CaaS. Data that is deployed to CaaS from external sources is lost, unless a dedicated backup strategy is employed.

When using CaaS it is highly recommended to use middleware to hide API Keys from the client.