Web Technologies 2026 · BiUH · The assignment

What You Hand In

Two projects · two repositories · one folder · one place to submit

webtech.landrock.io

The whole assignment, on one slide

Two projects. They share nothing.

1 · The learning website2 · Your personal project
Whatthe site we built together, lesson by lessona website of your own choosing
Folderweb-projects/my-siteweb-projects/your-project
Gitits own repositoryits own repository
GitHubits own remote repositoryits own remote repository
Liveonline, at its own addressonline, at its own address
LanguageEnglish · the site and its descriptionEnglish · the site and its description
webtech.landrock.ioits own entry · 5 imagesits own entry · 5 images

Two of everything. If one thing holds both projects, something has gone wrong.

On your computer

One folder. Two projects inside it.

web-projects/          ← just a folder · no Git here
├── my-site/           ← project 1 · a Git repository
│   ├── .git/
│   ├── index.html
│   ├── quotes.html
│   ├── project.html
│   ├── machine.html
│   ├── nav.html · nav.js
│   └── style.css
└── my-portfolio/      ← project 2 · a Git repository
    ├── .git/
    ├── index.html
    └── …
  • Call the outer folder web-projects, webtech or github — your choice
  • Name project 2's folder after your project
  • More folders in there later? Fine. These two at least.

The outer folder only holds things. Git lives one level down — once in each project.

The one mistake to avoid

git init inside each project — never in the outer folder.

Right · two repositories

A .git folder in my-site, another in your project. Each has its own history and its own GitHub repository.

Wrong · one for both

A .git folder in web-projects. Now both projects are one repository: one history, one GitHub repository, mixed together.

cd web-projects
git status     → fatal: not a git repository     ✓ right — no Git out here
cd my-site
git status     → On branch main                   ✓ right — Git in here

Ran git init in the outer folder by mistake? Don't delete anything — ask, and we fix it together.

On GitHub

Two folders, two repositories.

On your computerOn GitHub
web-projects/my-sitegithub.com/your-name/my-site
web-projects/my-portfoliogithub.com/your-name/my-portfolio

Each folder is pushed on its own. Pushing my-site never updates your project.

Project 1

The learning website.

The site we built together — fourteen items, from the first page to the site online. Handed in, not presented.

Project 1 · on the site · items 1–8

Eight things the site must have.

ItemWhere
1Index page with a hero image and an overview of the siteindex.html
2Quotes page with at least 15 quotesquotes.html
3DRY navigation — written once, put into every page by JavaScriptnav.html · nav.js
4Project page with a list of at least 5 project ideasproject.html
5Quotes page styled, with a hero that shows a random quotequotes.html · style.css
6Useless machine page — a minimal digital toymachine.html
7Machine page with an interactive gamemachine.html · machine.js
8The whole site styled and finalisedevery page

Finalised means: every link works, every image loads, nothing is a placeholder, and it works on a phone.

Project 1 · around the site · items 9–14

Six things: your tools, GitHub — and the site online.

9A code agent (AI) set up in VS Code
10Git installed — git --version answers
11The website folder initialised — git init inside my-site
12A GitHub account
13The remote repository connected, and the code pushed
14The site live at a real address — anyone with the link can open it

Items 10–13 prove themselves: if my-site is on GitHub with your commits, they are done. Item 14: the link opens.

Project 2

Your personal project.

A website of your own choosing — in its own folder, with its own repository. The one you present and defend.

Project 2 · what it has to be

Eight requirements.

Pagesat least four, with working navigation between them
Contentyour own words and images, or properly sourced. AI text is edited — and owned — by you
Structuresemantic HTML
Layoutresponsive: it works on a phone
Behaviourat least one thing that responds to the user
Livereachable at a real address
Historya Git history that shows it grow, week by week
Identityan Open Graph image, a favicon and an app icon

In full: the Your Project deck. Not required: a server or a database.

Both projects · putting them online

Both sites go live — each at its own address.

Learning websitehttps://your-name.github.io/my-site/
Personal projecthttps://your-name.github.io/my-portfolio/

Which host, and why: webtech.landrock.io/toolkit#ship. Before you hand in, open both links on campus Wi-Fi and on mobile data.

Hand in

Both projects go on webtech.landrock.io — in your account.

Two entries, already waiting on your dashboard. Text, two links and five images in each.

Hand in · the steps

Once per project — so twice.

  1. Sign in at webtech.landrock.io with your Canvas account — you land on your Dashboard
  2. Both entries are already there: Learning HTML and Untitled personal project
  3. Edit — fill in the text and both links, upload the five images, then Save changes
  4. Again for the other project — the dashboard ticks off what is still missing

Learning HTML keeps its name; give your personal project its own. Change both entries any time — keep them up to date as the sites grow.

Hand in · per project · the text

Five fields, and a status.

On the formWhat goes in
Titlepersonal project: three or four words · Learning HTML: fixed
Short descriptionone sentence, 10–20 words: what it is
Long description3–5 paragraphs: what it is, who it is for, how you built it
GitHub repositorythis project's repository — https://github.com/your-name/…
Live sitewhere it runs — required for both projects: https://your-name.github.io/…
StatusCompleted — when it is done

Everything in English — the title and both descriptions. Two entries, two GitHub URLs. Each entry links to its own repository — never the same one twice.

Hand in · per project · on the Edit page

Five images per project — ten in all.

On the formSizeLearning websitePersonal project
Cover image1200 × 630, under 100 KB
Desktop screenshot1920 × 1080
Mobile screenshot375 × 812
App icon180 × 180, PNG
Favicon32 × 32, PNG

The upload accepts up to 1 MB for the two icons and 5 MB for the others. Smaller is better.

Hand in · the images

Where each one comes from.

Cover image made by you: any tool with a 1200 × 630 canvas — Figma, Canva, Photopea, Keynote. The site's name, readable at thumbnail size
Desktop screenshot your homepage in the browser: DevTools → Ctrl+Shift+P (⌘⇧P) → Capture screenshot
Mobile screenshot DevTools → device toolbar Ctrl+Shift+M (⌘⇧M) → 375 × 812 → Capture screenshot
App icon apple-touch-icon.png — the same icon at 180 × 180, square corners: the phone rounds them
Favicon the icon you made in lesson 4 — favicon-32.png, already in your folder

DevTools screenshots have no browser bars and no desktop behind them — that is the point.

Before you hand in

Check all eight.

webtech.landrock.io

The whole assignment

← → navigate · F fullscreen · P print · Copy never turns the page