Everything from the last three lessons, on one site of your own: the problem you investigated and pitched, explained well enough that someone who knows nothing about it would understand why it matters.
Getting started: the Web Page Builder appears on the build steps further down, already holding a Home page with a heading and a sentence on it. Blocks and code both count — use whichever gets you there.
Say the deliverable out loud: the site is the outcome, not the method. A student who builds entirely with blocks has met the outcome exactly as well as one who types.
Five short build beats rather than one long run. Hold the class at the end of the menu beat: links that do not work are the thing that sinks this project.
Aim for this shape:
Keep the writing short and use real details from your investigation. Two well-written pages beat four thin ones.
Put the shape on the board and leave it there — it is the mark scheme for the rest of the lesson.
The most common failure is a good home page and nothing else. The second page matters more than the styling does.
The builder below opens on a Home page with a heading and one sentence already on it. Make them yours.
Use the Your web page tab to see it as a reader would.
Circulate for content, not for tags: is the problem named in words a stranger would follow? Vagueness here is the thing to push on, not block choice.
Look for: a heading that names a topic ("Litter") rather than a problem ("Litter in the park beside our school"). The second one is the lesson.
A site is more than one page.
Here is what a second page looks like before you fill it in:
{"blocks": {"languageVersion": 0, "blocks": [{"type": "web_page", "fields": {"NAME": "Data", "BG": "lightblue", "FG": "navy", "FONT": "sans-serif"}, "x": 10, "y": 10}]}}
Look for: content dropped beside the new page block rather than inside its content mouth. It renders nowhere, and the give-away is a page that previews empty.
Names matter here: the menu in the next step uses them, and a page called "Page" tells a reader nothing.
A reader needs to get between your pages.
Checkpoint — stop here until this works. Two pages, and links that go both ways. Do not start styling until they do.
Hold the whole class at this checkpoint. Anyone without two linked pages needs help now, not at the end; anyone past it can start styling early.
Keep the predict habit going even here: say where it goes before you click it. A link that opens the wrong page is far easier to spot when someone has just committed to an answer.
Look for: a menu on Home only. The reader reaches page two and is stranded, which is exactly the sort of thing testing catches and reading does not.
You're previewing this lesson. Get full access to this lesson and hundreds more — each one ready to teach, with interactive activities, printable resources and pupil progress tracking built in.