Zero to Live in One Afternoon: Three Routes Compared

You can build a website in a day. All three routes in this course get you to a real address serving real pages over HTTPS inside about four hours, and that is not a marketing claim — it is just true in 2026. The interesting question is what each of them quietly trades away to hit that deadline.

This lesson is the afternoon plan, hour by hour, for each route. Read all three even if you have already chosen; the shape of the other two tells you what your own is costing.

The rules of the exercise

Four hours, one person, no help. You have a domain, a rough idea of your pages, and — this is the part that decides everything — your words and pictures already written and saved in a folder. If you start the afternoon without content, you are not building a site this afternoon. You are writing one, which is a different and slower job.

The target in each case is the same: a live URL, HTTPS working, a usable phone layout, and nothing on the page you would be embarrassed by.

Route one: hosted builder

1. First thirty minutes: account, plan, template, domain connected. This part is genuinely as quick as advertised, and the certificate is issued for you without you doing anything.
2. Hours one to three: replacing every piece of the template's content with yours, and discovering which parts of the layout the editor will and will not let you change. This is where the afternoon actually goes.
3. Final half hour: the contact form, the mobile view, and a pass over the pages on a real phone.

What you end up with: a live multi-page site on your own domain, HTTPS, a template-based design, a usable mobile version and a working contact form. Presentable, on the day, with no technical knowledge required.

Where this route stalls: wanting a layout the editor cannot express. When it happens you will spend an hour fighting a component that was never going to do what you want, and the only real fix is to want something else.

Route two: WordPress at a one-click host

1. First forty-five minutes: hosting account, one-click install, domain pointed, HTTPS enabled, admin password stored somewhere sensible.
2. Next hour: choosing a theme and accepting that it will not look like its demo, because the demo is full of demo content. Budget this hour honestly — theme browsing has eaten more afternoons than any other single activity in this lesson.
3. Final two hours: three to five pages of your own content, a menu that makes sense, and exactly one plugin configured — the one thing your site genuinely needs and nothing else.

What you end up with: a live site on your own hosting with a lightly customised theme, three to five pages, HTTPS, and one working extension. Slightly rougher than the builder result at the same hour, and entirely yours.

Where this route stalls: plugin conflicts, or update paralysis — the moment you become afraid to press the update button in case something breaks. Both are cured by having a backup you have actually tested restoring.

Route three: hand-coded HTML on free static hosting

One caveat before the timings, and it is the honest one: this route is realistic in an afternoon only if you are technical, or at least unafraid of a terminal. If you have never written HTML, four hours will produce a page and a great deal of learning, not a finished site — and that is a perfectly good outcome, just not this one.

1. First hour: the boilerplate and the page structure. Doctype, lang, charset, viewport, title, then real headings and paragraphs.
2. Next two hours: CSS. A box-sizing reset, a max-width container, a font stack, and one media query for wider screens. This is the bulk of the work and the bulk of the satisfaction.
3. Final hour: the deploy pipeline. Repository, static host, custom domain, certificate. If you have not used version control before, this hour is the one that overruns.

What you end up with: a live one-to-three-page site on a real domain or a subdomain, HTTPS, and responsive CSS you wrote yourself. One thing to check before you commit to it, though — the free-tier terms and limits from lesson four apply in full here. Some popular free hosts prohibit commercial sites outright, and one of them meters deploys tightly enough that a heavy build day can pause your project.

Where this route stalls: anything that needs a database. A contact form, a login, a booking system. Static files cannot do those alone, and bolting on a third-party service is a different afternoon.

What each route trades away to hit four hours

The builder trades ownership and portability, permanently. Your design ceiling is whatever the component set can express, and the recurring cost starts today and does not stop. That is a real trade and for a lot of people it is a good one — but make it knowingly rather than by accident.

WordPress trades nothing structural. What you inherit instead is maintenance: updates, backups, security, forever, performed by you or by somebody you pay. Theme lock-in is softer than builder lock-in but it is not nothing — switching themes rearranges a site more than people expect.

Hand-coding trades features. There is no content management system, no forms without a third-party service, and every content change is a code change. If someone other than you will ever need to edit the words, this route strands them.

The one clock you cannot speed up

This applies identically to all three routes. If you buy the domain through the platform you are building on, it is live the same day. If the domain already exists somewhere else, the switch is gated by the TTL on your existing DNS records, not by anything the platform does. Buy the domain first thing, or lower the TTL the day before, and the afternoon is not held up by a cache expiring somewhere.

What none of them will have at five o'clock

Finished content. Not one of the three routes produces a site with genuinely finished words and pictures in four hours, because that was never a software problem.

Speed to live is the least interesting difference between these three routes. The difference that matters arrives in month eighteen, when somebody has to change something.

Where this sits in the course

If the afternoon plan appeals but you have not settled which route is yours, the full guide to how to make a website makes that decision properly, using maintenance rather than speed as the tiebreaker.

Before you start the clock

• Your page list is written down, and it has four pages or fewer on it.
• Every word and image you need is in one folder before hour one.
• The domain is bought, or its TTL was lowered yesterday.
• You have chosen your route and you are not reconsidering it at hour two.
• If you are hand-coding, the host you picked permits what your site does.
• You have accepted that today's job is live, not finished.