Decoupling the front- and backend
Headless CMS for eCommerce
A headless architecture allows for more efficient development and deployment, greater flexibility in terms of content delivery, and enables companies to be more agile, allowing them to quickly adapt to changes in the market and customer needs.
Headless refers to a type of architecture in which the front-end and back-end of a website or application are decoupled. In a traditional architecture, the front-end (or “head”) is tightly integrated with the back-end, meaning that changes to one will often require changes to the other, which can be time-consuming and costly. With a headless architecture, the front-end and back-end communicate with each other through APIs.
Headless CMS
Digital experiences are evolving beyond webpage-based channels. Deploy content across your websites, mobile apps, kiosks, custom displays and virtually any other interface with our modern, API-first CMS.
Save time and cost
Because the front-end and back-end are decoupled, developers can work on each independently, which can speed up the development process and make content delivery more efficient and cost-effective.
Freedom to design
If you can think it, you can build it. Developers enjoy complete access to their website's code so they can customize experiences to any user requirement.
API-first principles in DynamicWeb
DynamicWeb API
DynamicWeb 10 is an API-first application supporting headless implementation and separation of front-end and back-end through APIs.
DynamicWeb API allows for a more flexible, modular and scalable architecture, as the API offers endless possibilities and can be used by a variety of different clients, including web and mobile applications, as well as third-party microservices.
Delivery API (expose data) is optimized to deliver data in context of permissions, devices and personalization, facets etc. for smooth headless implementations. Our delivery API gives you the flexibility to use whatever front-end technology and third-party microservices you prefer.
Management API (process orchestration) is used to make integrations and create users, content, update prices and any other task available in the UI. The management API enables you to perform tasks in DynamicWeb 10 from third-party system and reuse services from DynamicWeb 10 in other systems. This API approach lets you use your preferred developer tool and orchestrates everything in the backend is accessible via the web API.
The right fit
Time to go headless?
When considering a headless CMS, you should always focus on your specific business scenarios to understand whether a headless CMS is the right fit.
The two biggest factors to consider, are requirements for multiple data sources (CMS, Commerce, Search, Personalization and more) and multiple digital channels, e.g. websites, app or in-store solutions.
In these scenarios, a headless solution makes a strong case in terms of efficiency and flexibility. A headless solution can both support channels and adapt channels individually independently of other sources.
Customer success story: Laks & Vilt
Headless B2B eCommerce with customer portal and integration to Microsoft D365
The new eCommerce solution offers a much improved user experience that saves both customers and the sales force at Laks & Vilt a lot of manual work and time.
