The order a web project has to be built in, and what deferring costs

Most project plans are a sequence of deliverables — design, build, content, launch — which describes what gets produced but not what gets decided. The useful order is the order of irreversibility: settle the things that are hard to undo while nothing depends on them yet.

1. URLs, before design

A URL is the one part of a website that other people copy, link, print and paste into messages. Changing it later means redirects, lost equity and support conversations. Decide the hierarchy first: what is a section, what is a page, what is a filter that should never have its own address.

2. The content model, before templates

Decide what kinds of things exist — a project, a service, an article, a location — and what fields each one has, before anyone builds a page that displays them. A site whose content model is invented page by page ends up with the same information stored four ways, and no way to list it.

3. The language architecture, before content

Bilingual is a structural decision, not a plugin. Decide whether each language has its own URL space, whether translations are enforced or optional, and what happens to a page that exists in one language only. Retrofitting Arabic onto a site built as English-with-a-translation-layer is one of the most expensive corrections in this work.

4. Who edits this in six months

This decision quietly selects the entire stack. A client whose marketing person adds a page every week needs a different build from a client who will send two emails a year. Choosing the wrong one produces either a site nobody can update or an editing system nobody uses — and both are discovered long after launch.

The sequence that follows from that

1. Requirements as questions the site must answer, not as a feature list.
2. URL hierarchy and content model, written down and agreed.
3. Language architecture and the rules for partial translations.
4. Real content for the three most important templates — never lorem.
5. Design against that real content, at the narrowest viewport first.
6. Build the templates, then the long tail of pages.
7. Performance and structured data as part of the build, not a phase after it.
8. Redirects, analytics, sitemap and a launch checklist written before launch day.

Designing against real content is the item people skip and the one that saves the most. Lorem ipsum is the same length in every box; a real Arabic product name is not, a real client testimonial is four lines longer than the placeholder, and a real price has a currency symbol that has to sit somewhere.