dardo
ESLet’s talk ↗

Platforms

WordPress vs a custom website: what changes for your team?

WordPress is a publishing platform; a custom website is an implementation approach. They are not mutually exclusive: a custom frontend can use a CMS. Compare editorial needs and maintenance responsibilities rather than labels.

01

Start with the publishing team

WordPress includes publishing, media and user-management capabilities. Whether those are sufficient depends on your content structure. Give editors a realistic task rather than assuming that familiarity with a brand means the configured site will be easy to use.

02

Price the whole stack

Document hosting, backups, updates, integrations and paid extensions. In a custom build, document deployment, CMS access and dependency maintenance as well. Neither approach is maintenance-free, and the person responsible should be named before launch.

03

Prototype the distinctive part

If the project depends on unusual motion, complex data or product behavior, prototype that section before choosing the final architecture. If ordinary publishing is the main job, avoid adding technical complexity that does not help the editor or visitor.

Sources & further reading

Public sources consulted for this edition. Agency descriptions reflect published offerings, not an independent performance audit.

How we publish these guides →
From an idea to something real

Make your next
move matter.

Start a project ↗Explore the project planner →