Portfolio
Describe a project, filter your work by category, and explain one design decision.
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.
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.
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: 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.
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.
Five studios available.
Describe a project, filter your work by category, and explain one design decision.
Help a visitor find a service, understand the opening information, and preview an enquiry.
Add products, change quantities, remove items, and verify a total that is calculated from data.
Search for an article, follow a related link, and return to the index without getting lost.
Find a creation, play or explore it, and come back — with a real game and simulation included.
| Open this | Use it for |
|---|---|
README-FIRST.md | Setup, guided changes, and visible checkpoints |
index.html / style.css / script.js | Your editable website source |
challenges.md | Extensions to take once the baseline works |
troubleshooting.md | Symptoms, causes, and repairs |
reference/ | A finished version to inspect after your own attempt |
credits.txt | Source 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.
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.
script.js.Extend: add a case-study page — problem, first attempt, feedback, revision, result.
Choose a fictional service, such as a bicycle repair workshop. Decide what a visitor needs before you make anything beautiful. Use invented contact details.
Extend: add a frequently asked questions section built from <details> and <summary>.
Use fictional products to learn how data becomes an interface. This is a classroom prototype: no payments, no orders, no real customer data.
script.js. Change a name and a price, keeping every product ID unique.Extend: add a product category filter that does not clear the cart.
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.
Extend: add a glossary and link a term inside an article to its definition.
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.
Extend: add a third creation and let visitors filter by game, simulation, or art.
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 do | A real shared service also needs |
|---|---|
| Page navigation, search, local forms, a practice cart | A server or configured service to receive submissions and orders |
| Local preferences saved in one browser | Accounts, authentication, and a database for shared private data |
| Wiki articles stored as files | Shared editing, permissions, revision history, and moderation |
| Product information and price calculations | A 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.
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.