A CMS in one paragraph
A content management system, or CMS, is software that lets people add and change the words, images, products and pages of a website through a web-based dashboard, without touching code.
Your receptionist can update clinic opening hours, your marketing assistant can publish a Thai-language promotion, and your sales manager can add a new product, all from a browser. The CMS stores that content and turns it into finished pages using templates a developer set up once.
Almost every business website today runs on some kind of CMS. The real question is which kind fits your team, your languages and your budget, and that is what this guide covers. If you are at the very start and still planning pages and content, our guide to build a website step by step puts the CMS decision in its proper place in the wider project.
How does a content management system work?
Under the dashboard, most systems have the same four parts.
- The admin area. A password-protected screen where editors log in, write, upload images and press Publish. Roles decide who may do what, so a junior writer can draft while only a manager publishes.
- The database. Content is saved as structured records: a page title, its body, its images, its Thai and English versions, its publish date. Keeping content as data, not as finished pages, is what lets you change the design later without retyping everything.
- Templates. A developer builds templates, often called a theme, that decide how each type of content looks: a blog post, a service page, a product. The same template serves hundreds of pages.
- Output. When a visitor opens a page, the CMS merges the stored content with the right template and sends the finished HTML to the browser, usually with a cache in front so repeat visits are quick.
Extensions, called plugins, apps or modules depending on the system, add features such as forms, booking, online payments or search tags. They are convenient and also the main source of upkeep, because each one needs updating.
What are the main types of CMS?
Content management systems fall into five broad families. The names below are examples, not a ranking.
| Type | Examples | What you manage | Who it suits |
|---|---|---|---|
| Open-source, self-hosted | WordPress, Drupal, Joomla | Hosting, updates, backups; you own the files and data | Most business sites that want control and room to grow |
| Hosted website builder | Wix, Squarespace | Very little; the platform runs everything | Simple sites where a monthly fee and platform limits are acceptable |
| E-commerce platform | Shopify, WooCommerce on WordPress | Products, orders, payments, shipping | Shops selling online, including PromptPay and COD in Thailand |
| Headless CMS | Contentful, Strapi, WordPress used headless | Content only; a separate app shows it | Teams publishing to apps and other screens as well as the web |
| Enterprise suite | Adobe Experience Manager, Sitecore | Licences, integrations, a dedicated team | Large organisations with complex workflows |
A word on headless systems: they store content and deliver it through an API to a separate front end, which suits companies publishing to apps and screens as well as a website, but adds a second codebase to pay for. Our longer piece on headless WordPress weighs that trade in detail.
Static site or CMS?
A static site is a set of plain HTML files written by a developer. There is no database and no admin area, so it is quick, cheap to host and hard to hack. The catch is that every change, even fixing a phone number, needs someone who can edit code.
A static site can be the right call when:
- the site has a handful of pages that change once or twice a year;
- you already pay a developer who will make every edit;
- there is no blog, no product list and no second language to keep in step.
Most Bangkok businesses outgrow that quickly. Menus change, rooms get new rates, clinics add treatments, and a bilingual site doubles every edit. Once more than one person needs to update content, or you publish anything regularly, a CMS pays for itself in saved developer hours and in content that stays current.
How do you choose a CMS?
Start with people and content, not with features. The checklist below covers the questions that decide the choice for most Thai businesses.
- Who edits, and how oftenCount the people who will update the site and how comfortable they are with software.
- LanguagesThai and English versions of each page, and a Thai admin area if staff want it.
- Selling onlineWhether you need a cart, PromptPay, cards, COD and Thai courier rates.
- Budget, now and yearlyBuild cost plus hosting, subscriptions, extensions and upkeep.
- Ownership and lock-inWhether you can export your content and move host or platform later.
- UpkeepWho installs updates, checks backups and fixes problems after launch.
Thai-language editing
Check two separate things. First, can the admin area itself be shown in Thai for staff who prefer it? WordPress, for example, offers a Thai translation of its dashboard. Second, can the site hold a Thai and an English version of every page, linked to each other, with the right language tags? That usually needs a multilingual plugin or a built-in feature, and it is worth testing with real Thai text, including long words without spaces, before you commit.
Costs by type
Open-source systems have no licence fee but need hosting, updates and a developer for the build. Hosted builders charge a monthly subscription, and costs grow with add-ons. E-commerce platforms add monthly plans or transaction fees, so check the provider's current pricing page. Enterprise suites carry licence costs that only large organisations justify.
For deeper reading, start with what WordPress is and what it does, then see how WordPress is used by Thai businesses. When you are ready to compare named systems side by side, our head-to-head guide covering WordPress vs Drupal and other CMS options for Thai firms does that job.
Changing CMS later
You can move to a different CMS, but it is rarely a copy and paste. A migration usually involves:
- Exporting content. Open-source systems export fairly cleanly. Hosted builders often export only blog posts, or nothing useful, so pages may need copying by hand.
- Rebuilding the design. Templates do not transfer between systems. The new site needs its own theme.
- Keeping URLs and search traffic. Every old address needs a 301 redirect to its new one, or you lose links and rankings.
- Re-creating features. Forms, booking, product options and language switching must be rebuilt with the new system's tools.
Lock-in also happens inside a single system. A site built with a heavy page builder can be hard to redesign because its layouts only work while that builder stays installed. Our comparison of WordPress with Elementor versus a custom theme explains that risk. If you are planning a clean start, the guide on how to build a WordPress website shows the order of work.
Our recommendation for most Thai SMEs
For a Bangkok business with a brochure site, a blog, a booking or enquiry form and Thai and English versions, we recommend WordPress with a custom-built theme and no page builder. You own the content, staff can edit in a familiar dashboard, and the site is not tied to one platform's monthly plan, as our breakdown of WordPress pricing shows. For stores, Shopify or a WooCommerce store is the better base, depending on how much control you want.
As a WordPress developer in Bangkok, this is the kind of site we build. Our Starter package begins from THB 10,000 as an indicative one-time price for up to five pages with custom design, mobile-first WordPress, contact, WhatsApp and LINE buttons, on-page SEO and PDPA cookie consent. The final price is set in your written quote, and our page on how much a WordPress website costs lays out every package.
More guides on platforms
Sources
Builds and ranks the websites: the systems behind the 17 client sites whose Search Console numbers we publish. This guide was written by the Website Development Bangkok team. More about us