The order I work in, and why.
A website is the result of hundreds of small decisions. Working in the right order keeps them all pointing at the same goal.
I don’t start with the design.
I start with questions.
What does the business offer?
Who is the website for?
What are people trying to understand?
What does the business want them to do?
What’s missing from the current experience?
Those answers decide what gets built. The visual direction comes later.
Structure, then words, then design.
01
Structure before screens
Good information architecture (how the pages are organised and linked) makes a website feel obvious. Visitors shouldn’t have to reverse-engineer your company to find the service they need.
I work out the hierarchy first: what belongs on the homepage, what needs its own page, how services relate and where the important links lead. That structure also makes the content and the SEO easier to get right.
02
Write before decorating
Designing around placeholder text sets the wrong limits: the real words end up squeezed into spaces made for fake ones. I settle the core message early, so the layout is built around the content.
Copy and design still move together as the project goes on, but the main message comes first.
03
Design with a job to do
I like beautiful websites, but looking good is only part of the job.
The design has to point people to what matters most on each page, make the information easy to take in and show the quality of the business. I’d rather a site feel thought-through than decorated.
The process, step by step.
- 01
Understand
I start with the business: your services, customers, goals, current website and what needs to change. I ask the questions that need answering before any design starts.
- 02
Structure
I decide which pages are needed and what each one has to do. The aim is a clear site structure, not pages added because other websites have them.
- 03
Write
I work out the message and write the core website copy, so the design has real words to work around.
- 04
Design
With the structure and message settled, I design around them. Typography, spacing, imagery and interaction are there to make the content easier to take in.
- 05
Build
Once you’ve approved the design, I build it in Astro, with mobile layouts, accessibility, any CMS, technical SEO and speed handled as part of the build.
- 06
Test & launch
I check it across devices, test the forms and links, set up the agreed search settings and get the site ready to go live.
The tools, and why I use them.
Why Astro?
Light by default, interactive only where it’s needed
Astro is a web framework built for content-led sites, the kind of business and marketing websites I specialise in.
It produces light pages that don’t load extra JavaScript (code that runs in the visitor’s browser) unless the page needs it, and I can still add interactive features where a project calls for them.
WordPress isn’t bad
It just isn’t my default
WordPress can be an excellent choice for sites that need its plugins and publishing tools.
For the focused business sites I usually build, I prefer Astro’s leaner approach. I choose the tool for the result, not because it’s the one I’m used to.
Content management
Added only when something needs regular editing
I don’t install a CMS by default just because that’s how websites have usually been built. First I find out what content changes, who changes it and how often.
If you need an editing area, I set up Sanity or EmDash around what you’ll be changing. If you don’t, the site stays simpler.
Performance without giving up control
A fast site you can still keep up to date
Choosing Astro doesn’t mean choosing a website nobody can edit.
Astro gives me control over how the public site is built and loaded. A CMS gives your team control over the content they’re responsible for.
When you need both, I connect them, so the site stays fast and well organised while you keep the content up to date.
SEO is part of the architecture.
There’s no SEO button to press at the end.
Search engines read a website through the same things visitors notice: how it’s organised, what it says, how the pages link together, how the code is marked up and how fast it loads. So search is part of how I plan and build the site, not a problem left for later.
The technical basics are in place on launch day.
Where performance comes from.
Some of it is in the code. The rest is in:
The message.
The navigation.
The content.
The mobile experience.
The path to an enquiry.
A website should be efficient at doing its job, as well as efficient at loading the page.