Build Your Own Web

Build this website with blocks

Try another way to build: snap together HTML, CSS and behavior blocks, change their fields, and watch your website update. Start with this lesson’s project or try a code example below.

Want to keep what you build? Web Studio holds a drawing, blocks and code in one project that you can share on the class site and publish as your own website.

Lesson 6 · Project studio · 2–4 sessions after the foundations

Make a place for your ideas.

Choose a website with a real purpose. Each starter is a working, commented project with its own tutorial, repair guide, challenges, and a finished reference version.

Finish line: an original version of one starter that someone else can actually use. Download a ZIP, extract it, open the whole folder in VS Code, and begin with README-FIRST.md.

Start with a design brief

Before you change a single colour, finish these four sentences and save them as design-brief.md in your project folder. Use invented contact details for any practice site.

My audience is:
They come here to:
The three tasks they should be able to complete are:
I will know the site works when:

Sketch the route

Draw the home page and its destinations on paper and label the links. A visitor should be able to predict where each link goes, recognise the page they land on, and find their way back. If you cannot draw it, the site is not designed yet.

Then draw the home page again in Web Studio: drag out the header, the main area and the cards, and it writes the grid layout for you. Starting from a pack instead? Unzip it, then choose Open my own files in the studio’s Code tab and select its index.html, style.css, script.js and images.

Give content a hierarchy

One main action per page. Descriptive headings. A readable text width. A consistent spacing scale. Use CSS to express what matters most — and keep the HTML meaningful enough that the page still makes sense with the CSS switched off.

Draftsman's wooden drafting board with T-square, triangle, and architectural blueprints
Architectural Blueprints: Planning Before Building Before constructing a building, architects draft floor plans, elevations, and structural details on drafting boards using T-squares. In web design, drafting wireframes and writing a design brief establishes user routes, component hierarchies, and responsive grid layouts before coding begins. Credit: Wikimedia Commons · Public domain · source
The Bauhaus workshop building in Dessau designed by Walter Gropius featuring glass curtain walls
The Bauhaus Design Studio (Dessau, 1925) The Bauhaus studio united art, craft, and industrial technology under the principle that form follows function. Modern design systems, clean typography, modular card layouts, and intuitive user experiences originate from the functionalist disciplines developed in Bauhaus workshops. Credit: Bauhaus Dessau / Wikimedia Commons · Public domain · source

Your starter shelf

Five studios available.

A pack is a small course

Open thisUse it for
README-FIRST.mdSetup, guided changes, and visible checkpoints
index.html / style.css / script.jsYour editable website source
challenges.mdExtensions to take once the baseline works
troubleshooting.mdSymptoms, causes, and repairs
reference/A finished version to inspect after your own attempt
credits.txtSource and reuse information — add credits for your own media

Keep the extracted source folder. Change one thing at a time, and save a backup before a big experiment. These packs are plain browser HTML, CSS, and JavaScript: no framework, no build step, no account.

Portfolio studio

Show what you make

A portfolio helps a visitor understand your work and how it developed. Choose three pieces, not every file you have ever made. The explanation of a project is as much of the work as the project.

  1. Replace the example projects with three of your own. For each one write a title, a two-sentence description, the tools you used, and one thing you learned.
  2. Inspect the category values in the project markup and make your new categories agree with the filter buttons in script.js.
  3. Add an image you made or are allowed to share. Put it in an assets folder and write alt text carrying the useful information.
  4. Link to the real project or a local project page. Test each link from the portfolio, then test getting back home.
Test: try every filter, including a category with no work in it. Keep every title readable at 375px. Make sure a visitor can tell what you contributed.

Extend: add a case-study page — problem, first attempt, feedback, revision, result.

Business studio

Help someone take the next step

Choose a fictional service, such as a bicycle repair workshop. Decide what a visitor needs before you make anything beautiful. Use invented contact details.

  1. Replace the example name, introduction, service descriptions, and opening information with consistent invented content.
  2. Write one clear primary action, such as "Explore repairs", and point it at a real section of the page.
  3. Inspect the form labels and validation. Submit a valid practice enquiry and read the local preview — the pack does not send messages, and it does not pretend to.
  4. Write in your README what a deployed contact form would need: a configured receiving service, spam protection, somewhere the message is stored, appropriate handling of personal data, and a tested confirmation and failure state.
Test: submit with required fields missing, then with valid practice content. The page must say the preview was not sent. Check the services section without touching a mouse.

Extend: add a frequently asked questions section built from <details> and <summary>.

Store studio

Model products and a cart

Use fictional products to learn how data becomes an interface. This is a classroom prototype: no payments, no orders, no real customer data.

  1. Find the product data in script.js. Change a name and a price, keeping every product ID unique.
  2. Trace the Add to cart event through to the cart data and the displayed total. Explain why the total is calculated from the data and never read back from the text already on screen.
  3. Add two of one product and one of another. Work out the expected total on paper before you compare it with the cart.
  4. Remove the last item. Design an empty-cart message that tells the visitor what to do next.
Test: add twice, increase and decrease a quantity, remove an item, and empty the cart. Verify totals to the cent. The page must never claim a purchase happened.

Extend: add a product category filter that does not clear the cart.

Wiki studio

Organise what your class knows

A useful wiki helps someone find a clear answer and follow a related idea. This pack is a static collection of articles: visitors read it, they do not edit it.

  1. Read the existing article structure and choose a small topic, such as classroom tools or local habitats.
  2. Write three original articles, each with a descriptive heading, a short explanation, a useful example, and its sources.
  3. Add each article to the navigation and search data using the same identifier as its page or section, then test the direct link to an article.
  4. Connect two articles with a meaningful related link, and explain why that connection helps the reader.
Test: search in uppercase and lowercase, with a partial title, and with a word that matches nothing. Open an article URL directly and press Back. Keyboard users must be able to reach every article link.

Extend: add a glossary and link a term inside an article to its definition.

Denis Diderot and Jean le Rond d'Alembert's 1751 Encyclopédie engraved plate detailing arts and crafts taxonomy
Diderot & d'Alembert's Encyclopédie (Paris, 1751) The Enlightenment milestone of collaborative information architecture. Diderot and d'Alembert organized thousands of articles and detailed copperplate engravings with cross-references (renvois) across scientific disciplines. A class wiki inherits this grand tradition: creating structured, cross-referenced articles so readers can navigate and synthesize knowledge. Credit: Bibliothèque nationale de France / Wikimedia Commons · Public domain · source
Paul Otlet at the Mundaneum surrounded by floor-to-ceiling rows of card catalog drawers in Brussels
Paul Otlet's Mundaneum: The Physical Knowledge Web (1910) Belgian visionary Paul Otlet created the Mundaneum to gather and classify the world's knowledge across 12 million index cards. Otlet designed cross-linking classification codes and envisioned a future where researchers could search this global repository through electric screens—the direct precursor to modern wikis, search engines, and hypertext networks. Credit: Mundaneum / Wikimedia Commons · Public domain · source

Creation hub studio

Give your games and simulations a home

A catalog page helps visitors discover your creations, launch them, and understand their controls. This pack ships with a working original game and a working original simulation.

  1. Run the included game and simulation before you edit anything. Write down their controls and what each one demonstrates.
  2. Inspect the folders. Keep each creation's HTML, CSS, JavaScript, and assets together so its relative links keep working.
  3. Duplicate one creation's folder to start your own version, then add the new entry to the hub's project data with a unique path.
  4. Write a title, instructions, category, credits, and a short explanation of what it taught you. Test opening it directly and launching it from the hub.
Test: launch every creation, operate its controls with the keyboard, and return home. Confirm the game can restart and the simulation responds to a changed input.

Extend: add a third creation and let visitors filter by game, simulation, or art.

Know what the browser can own

Every studio above stops at a real boundary. Knowing where that boundary is — and saying so out loud — is part of understanding how websites actually work.

A static site can genuinely doA real shared service also needs
Page navigation, search, local forms, a practice cartA server or configured service to receive submissions and orders
Local preferences saved in one browserAccounts, authentication, and a database for shared private data
Wiki articles stored as filesShared editing, permissions, revision history, and moderation
Product information and price calculationsA payment provider and server-side order verification for real checkout

Never put a secret key in public JavaScript, and never treat a hidden button as protection — anything the browser receives, the visitor can read and change. For this course, finish the local prototype and describe which service a future version would need.

Project review

Invite someone who did not help build the project. Give them the three tasks from your design brief without pointing at the buttons. Record where they hesitate, and make one change because of what you saw.