External website; opens in a new tab.

Websites

WordPress or a custom website: what should decide the choice?

Choose around editing, maintenance, integrations and ownership; neither a CMS nor custom code is automatically the safer or cheaper answer.

Websites

Source review 21 November 2026

The useful comparison is the whole operating arrangement, not whether a platform is fashionable. A small information site, a frequently edited publication and an application processing private customer records have different needs. Ask what people need to change, how often, and who will keep the system supported after launch.

Where a content management system helps

WordPress can suit a team that needs familiar browser-based editing and a well-supported range of publishing features. The cost includes selecting and maintaining themes/plugins, backups, accounts and a suitable host. A long plugin list is not a substitute for a clear requirement, and an abandoned plugin can become a continuing risk. Check who owns paid licences and whether updates remain available after a supplier changes.

An editing account is a privileged capability. Users need appropriate roles, secure authentication and a safe publishing process. A supplier should explain how updates are tested and recovered, not promise that installing a security plugin makes every compromise impossible. Changes to content and changes to executable plugins have different consequences.

Where a smaller source-driven site helps

A static or source-driven site can keep the public runtime simple when content changes are occasional and a version-controlled editing process is acceptable. It does not automatically provide a friendly authenticated editor. If every text change requires an expensive rebuild of unrelated work, the workflow needs improvement. A bounded content edit should have a preview, review diff, stable URL and straightforward rollback.

Custom code may be justified for a genuine workflow or integration gap, but it brings design, testing, dependency and handover responsibilities. Do not commission a bespoke CMS merely to avoid using a conventional product. Conversely, forcing private operational features into a public theme/plugin stack can create unnecessary security and maintenance complexity.

Compare the actual proposals

Ask both suppliers to show the editing task you will perform, the cost of routine updates, supported versions, hosting, licence renewals, access ownership and exit process. Include content migration, old URLs, accessibility and enquiry handling in the comparison. “You own the website” needs detail about source, design files, accounts and third-party rights.

A useful decision record says why the selected route fits the current need and what would trigger reconsideration. For example, a modest source-driven public site may remain appropriate even if a separately secured customer portal is added later. That does not require turning the public website into the privileged application.

Avoid promises that one platform guarantees rankings, has no security risk or will never need maintenance. The safer choice is the simplest supported arrangement that meets the task and can be operated by the real people and budget available.

Sources and review

Prepared by Yellow Brick Tech. General guidance; the source and test conditions for your own situation still matter.

Next review: 4 May 2027

Related services

How Yellow Brick Tech can help.

Next step

Need to apply this to a real situation?

Ask a question or choose the closest project route. A short conversation can often clarify the next step.