The choice of a CMS usually starts with platform names, though a different question is more useful: who will update the site, and what exactly will they do every week. A platform that suits a developer and one that suits an editor are not always the same. Below are the signals that make the decision a considered one rather than a guess from the first search result.
Start with editorial tasks, not with the platform
Write down what will happen to the site after launch. Adding a new service once a quarter is one task. Changing catalog prices every week is another. Publishing news, translating pages into three languages and uploading photographs from sites is a third.
That list is the brief for the admin panel. If it has one line, a complex system is not needed. If it has ten and different people handle them, roles and permissions come into play, and that narrows the choice immediately.
Questions worth answering before choosing
- How many content types the site has: pages only, or also services, products, articles and reviews
- How many languages are needed and whether every version will be maintained equally
- Who edits the material and whether staff permissions need limiting
- Whether connections to external systems are required: inventory, payment, delivery, CRM
- Who will maintain the site technically and what budget is set aside for it
- What happens to the project in two years: growth, steady state or a rebuild
Three options and how they differ
A website builder gives a fast launch and needs no technical maintenance. The price is limited access to template code, server headers and URL structure - some technical recommendations simply cannot be applied on such a platform, and moving the site later is not straightforward either.
An off-the-shelf CMS such as WordPress, OpenCart or MODX brings an ecosystem of ready modules and a wide pool of specialists. In return it needs regular updates: the platform, its modules and the PHP version on the hosting have to stay compatible.
Custom development is justified when the data model does not fit an existing system: unusual relationships, bespoke pricing rules, integrations with internal systems. Such a panel matches the task exactly, but its future depends entirely on the developer.
What to check in an off-the-shelf platform
- Whether security updates are released and how recent the last one is
- Whether required features exist as maintained modules rather than custom patches
- How multilingual content works: a built-in translation model is more reliable than a translator plugin
- Hosting requirements: PHP version, database type, access to server settings
- How many specialists are available who could continue the work if the contractor changes
Four decisions people regret later
Choosing by the number of ready templates. A template is replaced within a week; the data structure stays for years.
Thirty plugins instead of one considered configuration. Each needs updating, and any of them can break the site after the next core release.
Multilingual content through automatic browser-side translation. The search engine sees one version of the page, while an Azerbaijani-speaking visitor gets machine text in the service description.
A platform with few available specialists in Baku. The technology may be excellent, but an urgent fix turns into a search for a developer abroad.
Frequently asked questions
Can we migrate to another CMS later?
Yes, and it happens regularly. But migration is a project in itself: exporting content, mapping it to the new structure, moving images and setting up redirects from the old URLs. The more pages and inbound links a site has accumulated, the more a platform change costs, so the first choice is better made with a couple of years in mind.
Does a website builder suit a small business?
For a simple site with contacts and a couple of pages, it does. The limits show up once tasks appear such as catalog structure, custom URLs, page speed work or integration with inventory. If those are likely within the next year, it is better to start on a platform with access to the technical layer.
Does a landing page need a CMS?
Often not: a single page with occasional edits can be maintained without an admin panel. A CMS earns its place when the offer changes regularly, several campaign pages appear, or enquiries need to sit in one place alongside the rest.