Fazley RabbiA content management system (CMS) is the software behind a website that lets you add and change pages, products, photos and posts from a simple dashboard instead of editing code. When a shop owner logs in to update a price, or a school posts an exam notice, they are using a CMS. The main choice today is between a traditional CMS, which stores your content and also builds the pages visitors see, and a headless CMS, which only stores and manages content and sends it to a website or app built separately.
What a CMS does day to day
Behind the dashboard, a CMS handles several jobs:
- Storing content: text, images, products and files, usually in a database.
- Editing: forms and a text editor, so staff without technical skills can make changes.
- Users and roles: who can write, who can publish, and who can change settings.
- Templates: applying the site's design to every page automatically.
- Extras: menus, search, forms, revision history, scheduled posts and sometimes multiple languages.
Without a CMS, every change goes through a developer. That can be fine for a small site that rarely changes, but it becomes a bottleneck for any business that updates prices, stock or notices often.
The traditional CMS
In a traditional (sometimes called "coupled") CMS, one system does everything: it stores the content, provides the dashboard and produces the web pages. WordPress is the best-known example. Shopify works in a similar all-in-one way for online shops, as a hosted service.
Picture a restaurant where the same kitchen cooks the food and serves it in its own dining room.
Strengths:
- Quick to set up, with many ready-made themes and plugins.
- Plenty of developers know it, so help is easy to find.
- Editors can see roughly how a page will look while they work.
Weaknesses:
- The content is tied to that one website.
- Heavy reliance on plugins can make a site slow and fragile.
- The design is limited by what the theme and system allow without custom work.
If your WordPress site already feels overloaded, see too many WordPress plugins.
The headless CMS
A headless CMS keeps the storage and the dashboard but removes the "head", the part that builds web pages. Instead it delivers content through an API, and developers build the front end separately, often with a framework such as React. The same content can then feed a website, a mobile app, a screen in a showroom or a chatbot.
In the restaurant picture, this is a central kitchen that sends meals to several outlets, each with its own dining room.
Strengths:
- One source of content for many channels.
- Full freedom over design and performance.
- A clean separation between content and code.
Weaknesses:
- You need a developer for the front end and for changes to how content appears.
- There are two systems to host, secure and maintain.
- Editors may not get a live preview unless one is built for them.
Side by side
| Traditional CMS | Headless CMS | |
|---|---|---|
| Builds the web pages itself | Yes | No, a separate front end does |
| Effort to set up | Lower | Higher |
| Developer needed for layout changes | Sometimes | Usually |
| Content reused in apps and other channels | Limited | Designed for it |
| Design freedom | Within the theme and system | Full |
| Typical fit | Company sites, blogs, small shops | Several channels, custom web apps, larger teams |
Which one suits your business?
For most small and medium businesses in Bangladesh, a well-built traditional CMS is enough: a company website, a blog, a catalogue or a small shop where staff update content themselves. A headless set-up starts to make sense when the same content must appear in several places, such as a website and a mobile app, when you need a fully custom interface, or when you already have developers who will maintain it.
There is also a middle path: a custom-built site with a small admin panel made only for what you actually need to edit. WordPress versus a custom website compares those options, and when to use React explains the front-end side.
Questions to ask before choosing
- Who will update the site, and how often?
- Will the content appear anywhere besides the website?
- Do you need Bangla and English versions linked to each other?
- Who will apply updates and security fixes, and what happens if that person leaves?
- Can you export all your content if you change platform later?
- Are the accounts and hosting in your business's name?
Whichever you choose, a CMS needs regular updates and backups; see a website maintenance and backup plan. If you want help weighing the options for your situation, my web development service starts there.