DEV Community

likayeltsova for flotiq

Posted on • Originally published at flotiq.com

Enterprise headless CMS - what large companies should consider before buying a headless content management system

Interoperability

In an enterprise environment, you often have a variety of existing software solutions and they already store a lot of data, which could be very useful if shared across the organization. Unfortunately - that data is often locked, siloed in the applications where it's stored because of a lack of support for standards-based access. Proprietary data formats, built-in databases and similar solutions make it difficult to reuse content that has been collected and stored by your company for years.

When implementing a headless CMS in your organization - one of your key goals should be, what we call content freedom - any piece of content you produce and store in the system should be widely accessible across the enterprise. Here are some features you should look for to make this happen:

  • API-based access to content - RESTful and GraphQL,
  • Well documented API,
  • OpenAPI 3.0 compliance,
  • Easy to use tools for developers to quickly start reusing content,
  • No-code or low-code solution support through integrations like Zapier or Microsoft Power Platform.

System integrations

Headless Content Management Systems usually pride themselves on being ready for “omnichannel” content delivery. In reality, this means that headless CMS systems are focusing on storing clean data, which is not tied to a specific channel (e.g. website) and does not include any details as to how this data will be eventually displayed (for example - what colors will be used, or what font size). Thanks to that - the content stored in a headless CMS is easier to reuse in different scenarios.

What about existing data and systems? Data migration is one option, but in an enterprise scenario - quite often you won’t be able to simply switch off an existing system as there are many processes already relying on it. In that case - you will have to synchronize the data, or subsets of data, between systems, often using custom “glue” code to provide that synchronization. This is a lengthy process and requires a lot of time and effort to complete. How to avoid this or minimize the extent? Look for a headless CMS system that receives data just as easily as it publishes it.

Flotiq - for example - is open to thousands of data sources. It’s the only headless CMS that integrates with the Microsoft Power Platform and it’s a breeze to feed it with data coming, for example, from Microsoft SharePoint or Excel. With a couple of mouse clicks, you can set up synchronization between systems that requires no development at all.

Data migration

One of the most painstaking parts of implementing new systems is the necessity of data migrations. If you’re planning to replace an existing system, or systems, with a headless CMS - you need to verify how difficult and time-consuming it will be to perform such an operation. If the source and target systems are not flexible in terms of the structure of content it may take a significant effort to develop a migration tool that will convert between the data formats. The most important features during migration are:

Ability to batch upload large bulks of content into the CMS,
Flexible content models, which allow for easy adaptation of the existing data structure to avoid the time-consuming and costly development of custom migration tools.

Security

Implementing any new application in an enterprise is usually a lengthy process, involving multiple parties. One of the most important stakeholders in that process is the security officer. If you’re looking for a smooth implementation, here are the important points that the security team will check:

Access control:

  • Support for roles and Role-Based Access Control (RBAC),
  • Ability to define user-level access to specific parts of the system,
  • Ability to enforce password policy and enforce Multi-Factor Authentication,
  • Support for enterprise Identity Provider (IdP), for example, Azure Active Directory,

Application security:

  • Security of the APIs provided by the system, penetration testing records,
  • How are security considerations addressed during system development, does the vendor follow a well-defined process for addressing security issues, is the vendor ISO-27001 certified,

Hosting security:

  • On-premise deployment capabilities,
  • Secure, ISO-27001 certified data centre,
  • Support and continuity:
  • Enterprise support availability,
  • Backup policy,
  • System availability guarantees.

Summary

Enterprises consider headless CMS to help them automate and optimize the process associated with content management, decrease the time their employees spend on content distribution, enhance team communication and improve content reuse across organizations. Depending on the existing company policies – some CMS systems will fit in better than others, one of the main discriminators being the deployment model – for some organizations, cloud-based SaaS is still a no-go when it comes to storing company data.

As a headless CMS, Flotiq provides solutions dedicated to Enterprise customers.

Discussion (0)