A content system separates what a page says from how it looks, so non-technical people can change the words. That capability comes with an ongoing maintenance obligation and a set of access decisions most businesses never make deliberately.

What it gives you

Three things, and only the first is usually the reason it was chosen.

Editing without a developer. Somebody in the business can change text, swap an image, or add a page.

Structure applied automatically. New pages inherit the design, the menu updates itself, and lists of articles or products organise themselves.

Roles and history. Different people can be given different permissions, and changes can be reversed.

That second point is more valuable than businesses realise. Adding the fortieth page to a hand-built site means recreating the layout; on a content system it means writing the words.

What it costs you

The part rarely explained at the point of purchase.

Updates, to the system, the theme, and any extensions, on an ongoing basis. Skipping them accumulates security exposure; applying them carelessly breaks things.

Complexity. A system with a dozen extensions has a dozen things that can conflict, and diagnosing which is slower than fixing a static page.

Performance. A page assembled from a database on each request is slower than one that already exists, which is manageable with caching and is a thing to manage.

A larger attack surface, since a login exists and extensions are written by many parties.

None of that is an argument against using one. It is an argument for knowing that a content system is something you maintain rather than something you install.

Who can edit what

The decision most businesses never make, and it causes trouble later.

Most systems offer roles: somebody who can write but not publish, somebody who can publish, somebody who can change settings, and somebody who can do anything including removing other people.

The common arrangement is everybody as an administrator, because it is simpler, which means any compromised account is a full compromise and any mistake is unlimited.

The workable arrangement: one or two people with full control, everybody else scoped to what they actually do, and the developer's account removed when the project ends rather than left indefinitely.

Revision history is worth knowing about too, since it means an accidental deletion is recoverable and a business that does not know it exists will panic unnecessarily.

Templates against content

The distinction that determines whether the site stays coherent.

The template controls how a page looks; the content is what it says. Editing content is safe and editing templates is not.

Where a system lets an editor place arbitrary layout inside a page, that separation erodes, and after a year the site is thirty pages with thirty layouts.

Which is an argument for constraining what editors can change: they should be able to change every word and very little of the appearance.

That constraint feels limiting and it is what keeps a site looking like one site.

What you actually own

Worth settling at the outset rather than discovering at the end.

The content is yours. The hosting account should be in your name. The domain should be in your name. And you should have administrative access to your own site, which is not universal.

Where a site is built on a hosted platform rather than software you run, the position differs: you are renting an arrangement, and the practical question is what you can export if you leave and in what form.

Exporting text is usually possible. Exporting the design and the structure frequently is not, which means leaving a hosted platform generally means rebuilding.

That is not a reason to avoid one. It is a reason to know it before choosing.

When a content system is not needed

Being proportionate.

A site of a handful of pages that changes twice a year does not need one, and a hand-built version is faster, has nothing to update, and has no login to attack.

The threshold is roughly whether somebody in the business will genuinely be editing regularly, and whether the site has content that accumulates, such as articles, projects, or products.

Where the answer is yes, a content system pays for its maintenance. Where the site is static in practice, the maintenance is a cost with no corresponding benefit.

The questions to ask before it is built

  1. Who will edit, and what will they need to change?
  2. Who applies updates, and how often?
  3. What happens if an update breaks something?
  4. What extensions are being installed, and why each one?
  5. Will I have full administrative access?
  6. What can I export if I move?

The second is the one most likely to go unanswered, and an unmaintained content system is the most common cause of a small business site being compromised, which follows from the architecture question set out in static pages versus a database.

Frequently asked questions

What does a content system give you?

Editing without a developer, structure applied automatically to new pages, and roles with revision history so changes can be scoped and reversed.

What does it cost?

Ongoing updates to the system, theme, and extensions, added complexity, slower page assembly needing caching, and a larger attack surface because a login exists.

How should editing access be set?

One or two people with full control and everybody else scoped to what they do, with the developer's account removed when the project ends.

Why constrain what editors can change?

Where editors can place arbitrary layout, the template separation erodes and the site becomes thirty pages with thirty layouts within a year.

What should I own?

The content, the hosting account, the domain, and administrative access to your own site. On a hosted platform, know what you can export before choosing it.

When is a content system unnecessary?

A handful of pages changing twice a year. A hand-built version is faster, has nothing to update, and no login to attack.

West Coast Media Solutions Inc. provides web design, web development, hosting, digital marketing, and business consulting to organisations across Canada, drawing on more than twenty-five years in the field.

Site built on a system nobody has updated in two years?

We check what is installed, who can edit, and whether the maintenance is happening, which is where most compromises start.

Start a Conversation