Headless CMS
A headless CMS is a CMS that separates the panel where content is managed from the front end that shows it. Content is served through an API, so one source can feed a website, an app or another screen. The front end can be designed freely and made fast, but set-up and maintenance need developers.
- Area
- Web and software
- In Turkish
- Headless CMS
- Read more · Service
- Web and software
Why it matters
A headless setup pays off when the same content must serve a website, a mobile app and other screens. Because each part is built separately, the initial work grows. For a small brochure site it can add needless complexity, so it should be chosen only when the need is real.
Example
Say a restaurant chain shows its menu on the website, in a mobile app and on tablets in its branches. The menu is edited in one panel and sent to all three through an API. A price is changed once and updates on three screens at the same time.
Related terms
- CMSA CMS is software that lets a site’s pages, articles and images be added and updated from an admin panel without writing code.
- APIAn API is the interface a piece of software offers to other software, defining which requests it answers and in what form.
- Design systemA design system is the single place where the colours, typefaces, spacing and components of a brand’s digital products, such as buttons, forms and cards, are defined with their rules.
- DNSDNS is the system that translates domain names into the numeric addresses of servers.
- MVPAn MVP is the first version of a product, carrying the fewest features needed to test the idea with real users.
- SaaSSaaS is the model in which software is used online by subscription instead of installed on the user’s computer.
The definitions are general information. If you think one is incomplete or wrong, write to us and we will reply within one working day. Get in touch
From our journal
From what we have written on Web and software; they show how the term turns up in the work.
- Core Web Vitals explained: how to read LCP, INP and CLSThe three thresholds, the gap between field and lab data, and which row to look at in Search Console and PageSpeed Insights, step by step.
- How to brief a digital agency: seven headings on one pageThe one-page document to write before you ask for proposals: goal, current numbers, audience, what has been tried, constraints, who decides and the deadline. Plus a template and how to compare proposals.
- How to build a multilingual website: a 6-step decision listURL structure, one address per language, the language switcher, translation quality, the forgotten parts and a workflow that keeps versions in step: the decisions to make before you build.
- Website security checklist: 8 steps for ownersHTTPS and HSTS, updates, admin accounts and two-step sign-in, a backup you have restored, form spam, security headers, what Google does and the first hour after a breach.