Introduction
Summary
Introduces the Headless Platform principle of decoupling frontend from backend, and the versatility this brings for supporting multiple frontends.
Details
The principle of a Headless Platform is to decouple the User Interface (frontend) from the backend services. The responses from the platform are then used by another system, such as a website or mobile app.
Its design leads to a great deal of versatility in the setup and configuration. Here are some advantages of the Headless Platform:
- The ability to have multiple frontends, each targeted to various end-users, like desktop vs mobile, iOS vs Android, etc.
- Different frontends (websites) for various niches (younger vs older users) and countries (including localization).
- Ability to customize separate frontends in terms of design, as well as available features.
FAQ
Q: What is the core principle of a Headless Platform?
A: Decoupling the User Interface (frontend) from the backend services.
Q: Who consumes the platform's responses?
A: Another system, such as a website or mobile app.
Q: What are the advantages of this design?
A: It allows multiple frontends targeted to different end-users, niches, and countries, each customizable in design and features.
See also
- Architecture Overview — how Dotkernel implements this principle with API, Admin, Queue, and Core.
- Getting Started — prerequisites and installation basics.