Headless systems
Digital transformation has shown that a CMS is not always enough to reach all of a customer's digital touchpoints. This is where headless systems come into play. Here, the backend of the TYPO3 system is still used for content maintenance. By connecting to a REST API, the content provided can then be flexibly retrieved and output in any form. We recommend the use of headless systems when it comes to complex developments, portals or web services.
Data consistency and easy maintainability
Content is often available on different platforms. If editors want to incorporate changes or news, this must be repeated on the various platforms so that content is duplicated in the process. If a change is not made on all platforms, then the information is already no longer consistent. Using a headless CMS allows data to be maintained in one place. Changes to content are applied to all end devices (smartwatch, smartphone, notebook, tablet or desktop PC) and platforms. No resources are needed to display the content. The fact that fewer resources are required also results in a noticeable performance gain.
Data consistency and easy maintainability
Content is often available on different platforms. If editors want to incorporate changes or news, this must be repeated on the various platforms so that content is duplicated in the process. If a change is not made on all platforms, then the information is already no longer consistent. Using a headless CMS allows data to be maintained in one place. Changes to content are applied to all end devices (smartwatch, smartphone, notebook, tablet or desktop PC) and platforms. No resources are needed to display the content. The fact that fewer resources are required also results in a noticeable performance gain.
Security
Templates and therefore user interfaces are separated from the raw data when using a headless CMS. This circumstance reduces the surface area for potential attackers on the system and thus further increases the security of the headless CMS.
Security
Templates and therefore user interfaces are separated from the raw data when using a headless CMS. This circumstance reduces the surface area for potential attackers on the system and thus further increases the security of the headless CMS.