Websites rarely fail because the design is not attractive enough. They fail because the decisions at the start were made too quickly — a domain picked without a second thought, hosting bought because it was discounted, a platform that does not match how its owner actually works — and the cost only shows up a year later: the site is slow, awkward to change, and expensive to move.
This topic collects how we look at owning a website: choosing the right foundation early, building pages for reasons that can be explained, and looking after the site once it is live so it stays fast, secure, and easy to grow.
Three decisions that determine the rest
Almost every technical problem on a website traces back to the first three decisions:
- Domain — the address people use to find a business. A name that is hard to spell, or that does not match the business, adds friction to every promotion that follows.
- Hosting — where the site’s files and data live. Speed, availability, and how easily you recover from a problem are decided here, not in the theme.
- Platform — the system used to create and change pages. That choice decides who can edit content, how quickly changes can ship, and what the monthly upkeep costs.
The three lock together. Picking a platform before knowing who will maintain the content is the most common way a website project ends up with a monthly bill nobody wanted.
What we consider worth checking before buying
We do not judge a provider by its marketing page, but by things that can be verified:
- Renewal pricing, not just the first-year price.
- How easy it is to leave — whether the data, the domain, and the site files can be moved without drama.
- Backups and recovery, including whether a restore has ever been tested.
- SSL certificates that are issued automatically and renewed without asking.
- Support that reaches a human, with a clear response limit when a site breaks.
- Server location and network path, because both affect speed where the audience actually is.
For the deeper server layer — serving, TLS, and recovery — the discussion lives under Server. The day-to-day habits that keep it healthy are under DevOps & Sysadmin.
After launch, the work is not finished
A website is an asset that keeps running, not a one-off delivery. What keeps a site healthy for years is almost always small, repeated work: installing updates on time, checking backups, compressing images before uploading them, and refreshing pages when the information changes.
That is why we treat speed and security as budgets with numbers attached, not promises. The performance budget, the update habits, and how we measure the result are written up in our code standards and the security layer we apply to every project.
What we publish under this topic
Articles here are written for the people who own a website — business owners, marketing teams, and anyone who has to make decisions without becoming a developer: how to build a website from scratch, how to choose a domain and hosting, how to enable SSL, how to structure the core pages, and how to look after the site after launch.
Start with the full guide: how to build a website for beginners, which walks from defining the purpose through to a live, maintained site.
Related reading: the how-to guides we test before publishing, the code standards behind the sites we build, and the Server topic for the serving and hosting side.
Weighing up a new website or fixing an existing one? Tell us what you need and we will help sequence it sensibly.
