Build and deploy your first website

A real site, on a real address, built with help and understood by you. No framework, no build step, no prior experience.

beginner10 minChecked 2026-09-06

What you will be able to do

Publish a working, accessible static site and understand every file in it.

Before you start

  • A text editor.
  • A free hosting account.
  • No coding experience required.

What a website actually is

Three files and a folder. HTML for structure, CSS for appearance, optionally JavaScript for behaviour. A static host serves them. Everything else in modern web development is an optimisation of that.

Starting here rather than with a framework means you can read your own site, which matters more than it sounds.

Where AI helps and where it does not

It helps with: the initial structure, CSS you would otherwise look up, explaining what a line does, and finding why something is not centred.

It does not replace: deciding what the site is for, checking it works on a phone, and reading the result with your own eyes.

Accessibility from the first line

Alt text on images. Real heading levels in order. Sufficient contrast. Keyboard reachability. Retro-fitting these is tedious; including them from the start costs nothing.

Step by step

  1. Make a folder with index.html and style.css.
  2. Write the structure first: header, main, footer, and headings in order.
  3. Ask for CSS for a specific effect, and ask it to explain what each rule does.
  4. Add real content. Placeholder text hides layout problems.
  5. Check it at a phone width by narrowing the browser window.
  6. Tab through it with the keyboard. Every link and button must be reachable and visibly focused.
  7. Drag the folder onto a static host and open the address.
Explain-as-you-go build request
Write the HTML and CSS for a single-page site about a London neighbourhood.

Requirements: semantic HTML with one h1 and correct heading order, readable at 320px wide, contrast that meets WCAG AA, visible focus styles, alt text on every image, no framework and no build step.

After the code, explain in plain English what each CSS rule does and which line I would change to alter the spacing between sections.

What good looks like

  • It reads well on a phone-width window.
  • You can tab through it and always see where you are.
  • You can explain what every file does.
  • The address loads for someone else.

What it cannot do

  • A static site cannot store user data without a service behind it.
  • Generated CSS may use techniques you have not met. Ask before shipping code you cannot read.

When it goes wrong

Looks right on desktop, broken on mobile.
Check the viewport meta tag, and use relative units rather than fixed pixel widths.
Generated code references files that do not exist.
Common. Check every src and href resolves before wondering why an image is missing.

Privacy and data handling

Anything in the folder becomes public when you deploy. Check for stray drafts, notes and API keys before dragging it anywhere.

Sources3 referenced
  1. HTML: structuring the web

    MDN Web Docs · reference documentation · link checked 2026-09-06

  2. Web Content Accessibility Guidelines 2.2

    W3C · standard · link checked 2026-09-06

  3. Deploy a site — Netlify documentation

    Netlify · official product documentation · link checked 2026-09-06

Links are checked at build time. If one has moved, tell us.

Written by
BLACK LDN
Last checked
2026-09-06
Content state
editorial

Product behaviour changes. If something here no longer matches the documentation, send a correction.

Read next

Building something9 min

Turn a small idea into a working app

The discipline is not technical. It is refusing to build the second feature before the first one works.

intermediate

Checked 2026-09-06

Next: Turn a small idea into a working app