your-name.github.io/web-design-pathway.html
<section id="website-blocks">

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.

<body id="intro">

Beginner to independent creator · Grades 6–12 · No coding experience required

A website you understand. A world you can build.

Learn HTML, CSS, and JavaScript by making a home for your ideas. Start with three files. Finish with a site you can explain, change, and publish yourself.

AI is optional. Every build has written steps, commented code, checkpoints, and repairs. A browser and Visual Studio Code are enough for the core projects.

Three files. Three jobs.

Switch the layers off and on. The page's content survives even when its decoration and its behavior do not.

index.html + style.css + script.js

My creation station

A place for the things I make.

GamesSimulationsArt

Lead movable type arranged in a compositor's metal composing stick
Separation of Concerns: Structure vs. Presentation In traditional printing, the physical metal characters (structure) were completely separate from ink, paper, and binding (presentation). Modern web engineering formalizes this division of labor into three distinct files: HTML provides the semantic skeleton, CSS provides the visual design tokens, and JavaScript manages interactive behavior. Credit: Willi Heidelbach / Wikimedia Commons · CC BY-SA 3.0 · source
William Caslon's 1734 broadsheet type specimen showing font hierarchies and weights
William Caslon's Typographic Hierarchy (1734) Caslon's specimen sheet demonstrated how identical text gains distinct emphasis and readability through modular typographic hierarchy. Cascading Style Sheets (CSS) brings this exact discipline to digital devices, adapting font weights, rem sizes, and fluid layouts across screens of any dimension. Credit: William Caslon / Wikimedia Commons · Public domain · source
<section id="studio">

Build it here first, then make it yours

Every idea in this course can start in Web Studio, right here on the class site, with nothing to install. It is one project you can build three ways, and every way writes the same three real files.

  1. Draw the layout

    Drag out boxes and containers, drop in text and images, and move them like layers in a paint program. Everything snaps to a 12-column CSS Grid, and you watch the grid-column code write itself.

    Draw to code
  2. Add behavior with blocks

    Bring your page into blocks and snap on events: clicks, counters, filters, animation.

    Blocks
  3. Polish the real files

    Read and edit index.html, style.css and script.js with a live preview, the way the lessons below teach.

    Code
  4. Share it on the class site

    Hand in your submission file. Your teacher reviews it and publishes it in the class showcase.

    Class showcase
  5. Publish it as your own website

    Download the same files as a ZIP and upload them to your own GitHub Pages site. When you are ready, switch to VS Code and Git.

    Your own site

The lessons explain what the studio writes. Open the studio beside any lesson and try each idea in your own project.

<section id="workflow">

Work like a web designer

Your repeatable routine

  1. Read and predict. Say out loud what one change should do before you make it.
  2. Edit and save. Change your own source files in VS Code — never only the browser's inspector.
  3. Run and inspect. Refresh, then compare the result against your prediction.
  4. Explain and keep evidence. Write down what worked, what broke, and the repair that fixed it.

That loop is the whole job. Professional web developers repeat it hundreds of times a day; the only thing that changes is the size of the change.

Choose how you learn

Start from nothing: type the lesson examples into a new folder. Start with support: download the Foundations pack and follow README-FIRST.md.

No paid tools, AI account, or framework is required. The core packs run locally after download. Online references and publishing need an internet connection; WebXR has extra browser and device requirements.

Plan for 45–75 minutes per foundation lesson, then 2–4 sessions for your chosen project. Take the creative and XR extensions once your core site works.

Margaret Hamilton standing next to the stacked printouts of the Apollo Guidance Computer source code
Margaret Hamilton & The Discipline of Software Engineering (MIT, 1969) Margaret Hamilton standing beside the printed listings of the Apollo Guidance Computer source code, which she and her team at MIT developed for NASA's Apollo missions. Hamilton pioneered the term “software engineering” to demand the same rigorous discipline, test-driven predictability, and thorough documentation for software that traditional engineering demanded for physical machines. Credit: NASA / Draper Laboratory / Wikimedia Commons · Public domain · source
Grace Hopper at the UNIVAC computer console examining printed program output
Grace Hopper at the UNIVAC Console (c. 1960) Rear Admiral Grace Hopper at the console of the UNIVAC I computer. A pioneer of machine-independent programming languages and the creator of the first compiler (the A-0 System), Hopper championed human-readable source code over raw machine instructions. Her team famously taped an actual moth into their Harvard Mark II logbook, popularizing the term “debugging” for finding and fixing defects in program code. Credit: Smithsonian Institution / Wikimedia Commons · CC BY 2.0 · source
<ol class="web-route">

Your course map

Complete the first five lessons in order, then choose a project. Flash history and the creative lab add context and new possibilities. Publish when your project passes testing; WebXR is an optional extension.

Checkpoint completion is stored in this browser only. It is a personal record, not an automatic grade — keep screenshots and notes in your project folder.

Pro Editor Guide: Master Visual Studio Code for Web Development covers your local cockpit — interface navigation, Live Server auto-reloading, Emmet speed-coding, essential extensions, and keyboard shortcuts.

Big picture first (optional): How the web works follows one page request from the address bar to the screen — URLs, DNS, HTTPS, status codes and packets. Read it before Lesson 1, or come back to it when you publish.

Meet the Pioneers of the Web: Trace how four thinkers built the foundations of modern web design: Tim Berners-Lee (inventor of the World Wide Web & HTML), Marc Andreessen (Mosaic, the <img> tag & the visual browser), Håkon Wium Lie (Cascading Style Sheets & web standards), and Brendan Eich (creator of JavaScript & interactivity).

  1. Master Visual Studio Code

    Set up Live Server, learn Emmet abbreviations, master keyboard shortcuts, and split editors.

    Recommended starter
    Your editor cockpit
  2. Set up your first site

    Open a folder in VS Code, connect three files, launch Live Server, and trace network requests.

    Ready when you are
    A working local page
  3. Give the page meaning with HTML

    Write semantic headings, landmarks, accessible forms, figures, and project lists.

    Ready when you are
    A structured website
  4. Design with CSS

    Use design tokens, color systems, dark mode, hover transitions, Flexbox, and Grid.

    Ready when you are
    A layout that adapts
  5. Make it respond with JavaScript

    Connect DOM events, build real-time project search, dark mode toggles, and modal dialogs.

    Ready when you are
    A working interaction
  6. Test, debug, and include everyone

    Repair broken features, inspect DevTools, use the keyboard, and document test evidence.

    Ready when you are
    A tested first release
  7. Choose your website studio

    Build a portfolio, business site, practice store, wiki, or creation hub.

    Ready when you are
    Your own complete site
  8. Explore the Flash era

    Understand browser-game history, why the plugin ended, and how work is preserved.

    Ready when you are
    A historical comparison
  9. Build a home for interactive work

    Understand animation loops, simulation controls, and embedding your creations.

    Ready when you are
    A playable creation
  10. Publish and maintain your website

    Use version control, GitHub Pages, correct paths, and a release checklist.

    Ready when you are
    A shareable website
  11. Extend into WebXR

    Build a 3D gallery with a desktop view and an optional supported-headset mode.

    Ready when you are
    Optional immersive gallery
<section id="projects">

Choose something worth making

Show what you make

A portfolio or creation hub with working games, simulations, filters, and honest project explanations.

Explore creator projects

Help a community

A business information site or a small wiki that helps a real person find one clear answer.

Explore useful websites

Prototype a store

Build a product list and a practice cart, then learn exactly which features need a real service before anyone can pay.

Explore the store project
Draftsman's wooden drafting board with T-square, triangle, and technical blueprint drawings
The Architect's Drafting Table: Plan Before You Code Professional architects draft wireframes and spatial blueprints on drafting boards before laying structural foundations. A successful web project starts with a clear design brief, audience definition, and responsive layout sketch before writing HTML and CSS. Credit: 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: A Home for Human Knowledge (1910) Belgian visionary Paul Otlet created the Mundaneum to gather and classify millions of documents using interconnected index cards, dreaming of a “mechanical collective brain.” Building your own web project joins this century-long tradition: giving your ideas, research, and tools a durable home on the open web. Credit: Mundaneum / Wikimedia Commons · Public domain · source
<section id="toolbox">

Keep these tools on your workbench

<section id="demonstration">

Your final demonstration

Give a classmate your site and three tasks. Watch without telling them where to click. Fix one issue they find, then show the source code responsible for a feature. Submit your folder, your test notes, your credits, and a shareable link if publishing is appropriate.