'API driven architecture',Headless CDP' or why headlessness can be an advantage

This blog post explains the concept and benefits of c-rex.net as a 'Headless CDP'.

Image of a person pointing a finger at the API acronym. It shows how to distribute content to different output channels using an API.

The concept ofheadless' architecture has been increasingly found in content management and store systems for several years.

Here you separate the user interface (frontend) from downstream processes (backend).

Both layers communicate via a standardized programming interface (API) and exchange information through it.

The goal is to make data and functionality available to the largest possible number of usage scenarios, such as classic websites, mobile apps, or knowledge portals.

c-rex.net IDS is also developed according to this principle and thus offers flexible options for accessing content. Read what we have to offer in this short blog post.

Theheadless' approach of c-rex.net IDS

ContentDelivery with c-rex.net means that content is made available where users need it.

With c-rex.net technology in the background, you can provide information flexibly:

centrally in your existing portal,
on your existing web pages,
simply where your customers are.
Even integration with machine controls is possible.
Machines can get the information they need to make available to users directly from the API, or need to control themselves, such as maintenance intervals.

It goes without saying that content is provided and updated fully automatically. And of course, you can present the information the way your customers expect it.

This is made possible by the API-driven approach of the c-rex.net software modules.

Sounds good? Yes, we think so too.

Example of content integration via c-rex.net REST API

To make the whole matter a bit more concrete for you, we show an example of a possible integration in the following diagram.

Diagram showing a process for distributing information across a cloud architecture. c-rex.net DTS and c-rex.net IDS are involved in information preparation. — Example of information preparation with c-rex.net DTS and content distribution with c-rex.net IDS

This example is about Markdown documentation of a company managed on Git Hub.

Shown is a cloud architecture. Information from the internal technical documentation is prepared by c-rex.net DTS and made accessible via c-rex.net IDS, namely via the Content API.

With our HTML framework, the IDS Connector, we provide you with a tool for easy integration of the functionality into web portals.

You can easily implement this yourself with your web agency or webmaster.

This is how easy it is to integrate technical documentation into existing websites and portals:

Include three Javascript files in your web page.
From your HTML, define the element ID of your search slot as well as the element ID of the area where you want the search results to be displayed.
Still some web design for a good user experience (UX) and the appropriate CI.

Unnoticed, users who enter search terms on your website are redirected to c-rex.net IDS and find exactly the results they want in a modular content enriched with metadata.

We would like to draw your attention to another implementation example in which various c-rex.net software components and services play a role.

It is the GMP-BERATER, a knowledge portal of GMP-Verlag Peither AG, which we introduced to you in the blog post Scalable and future-proof knowledge portal The 'GMP-BERATER', a standard work in the pharmaceutical industry. introduce.

The c-rex.net IDS Content API

Take a look at the c-rex.net IDS Content API here.

The developers among you will immediately see the possibilities offered by such a scalable and flexible solution.

Screenshot of c-rex.net IDS API version — Extract from c-rex.net IDS API