Web Technologies 2026 · BiUH · Lesson 1

Web Fundamentals

How the web works · browsers and DevTools · HTTP · standards · your environment · the three pillars

webtech.landrock.io

Six parts, one picture

What this lesson covers.

1.1How the web works — history, client/server, URLs, DNS
1.2Browser DevTools — the instrument you diagnose with
1.3HTTP — requests, responses, status codes
1.4Standards and why pages work in every browser
1.5Your development environment
1.6HTML, CSS, JavaScript — the three pillars

Full lessons at webtech.landrock.io/course — these slides are the spine, not the detail.

1.1

How the web works

1989 · CERN

One person, four inventions.

Tim Berners-Lee at CERN
Tim Berners-Lee at CERN, where he proposed the Web in 1989

He wanted researchers to share documents. To make that possible he had to invent everything:

HTMLa way to write the documents
HTTPa way to transmit them
URLa way to address them
The browsera way to read them

All four are still in this room today — and the first website is still online at info.cern.ch.

Thirty-five years, compressed

How it got here.

1989Berners-Lee proposes the Web at CERN
1991the first website goes live
1993Mosaic — the first graphical browser
1995JavaScript: pages can now do things
2004Web 2.0 — everyone can publish, on someone else's land
2010smobile becomes the default surface
2020sthe edge, and machines as an audience

The model everything rests on

Client and server.

The client — your browser

Asks for things. Renders HTML and CSS. Runs JavaScript.

Chrome, Safari, Edge, Firefox

The server

Holds things. Answers requests. Sends back files.

Nginx, Apache, Node

you type an address→ browser asks→ server answers→ browser draws it

Every single thing in this course is a detail of that loop.

A URL is not one thing

It has parts, and each does a job.

https://www.example.com:443/path/to/page?name=value#section
scheme — how to talk host — which machine domain — who owns it port — which door path — which resource query — parameters fragment — never sent to the server

www is just a hostname — a name for one machine, like mail or ftp once were. The fragment is the odd one: the browser keeps it, the server never sees it.

DNS

A domain is a name for a number.

example.com→ browser cache→ OS cache→ your ISP→ 93.184.216.34

Nobody remembers numbers. DNS is the phone book — and like a phone book, it is cached at every level so the lookup usually never leaves your machine.

nslookup example.com     # try it tonight

Lesson 1.2

DevTools

Not a tour. The instrument you will diagnose with all semester.

Open it now — you will use it every day

Three ways in.

Right-click → Inspect
is the single most useful habit in this course.

The panels that matter

Four tabs do almost everything.

Elementsthe page's structure — click any element, edit it live, see its CSS
ConsoleJavaScript, errors, and anything you want to test in one line
Networkevery request: what, how big, how slow, from cache or not
Sourcesthe files themselves, and where to pause the code

Elements answers "why does it look like that". Network answers "why is it slow".

The part that surprises people

You can change anything —
and break nothing.

Edit the HTML. Change a colour. Delete an element. Toggle a CSS rule off. It is your copy, in your browser, and refresh undoes all of it.

Which makes it the safest place to experiment you will ever have. Change it there first, then put it in your file.

Lesson 1.3

HTTP

The conversation between the browser and the server

Every single thing on the web

A request, then a response.

→ the browser asks
GET /index.html HTTP/1.1
Host: example.com

← the server answers
HTTP/1.1 200 OK
Content-Type: text/html

<html>…</html>

That is it. Everything else is detail on top of this exchange.

Methods — what you are asking for

MethodWhat it means
GETgive me this — the one you use thousands of times a day
POSThere is something new (a form, a login, an upload)
PUTreplace what is there
DELETEremove it

The difference that matters: GET puts data in the URL, so it is visible and bookmarkable. POST puts it in the body.

Never put a password in a GET. It ends up in browser history and server logs.

Status codes · the server's one-word answer

200
OK — here it is
301 / 302
it moved — go here instead
304
unchanged — use your cached copy
404
I looked. It is not here. Your mistake
403
it exists, you may not have it
500
I broke. My mistake

4xx is your fault. 5xx is theirs.

Knowing which is which is half of debugging a deployment.

Lesson 1.4

Standards

Why a page you write works in a browser you have never used

Nobody owns the web

That is the whole point.

HTML, CSS and HTTP are agreements, not products. The W3C and WHATWG write them down; browser makers implement them.

Which is why a file you write tonight opens on a phone in Brazil, a kiosk in Berlin and a browser that does not exist yet.

Compare: a document from a 2005 word processor. Standards are why the web does not rot.

Progressive enhancement

Build so it degrades well.

1 · It works

Plain HTML. Readable by anything, including a screen reader and a search engine.

2 · It looks right

CSS on top. Better, but nothing depended on it.

3 · It feels good

JavaScript last. If it fails, the page still works.

The order is not aesthetic. Each layer assumes the one below it might be all there is.

Two free tools, no excuse not to use them

Check your work.

Both answer questions that are otherwise guesswork, in about ten seconds.

A validator will find the unclosed tag you have been staring at for twenty minutes.

Lesson 1.5

Your environment

Editor · browser · local server · version control

Four things, and that is all

VS Codefree, everywhere, and what most of the industry uses
A browser with DevToolsChrome or Edge — you will live in here
A local serverthe Live Server extension for VS Code
Gitso today's work survives tomorrow's mistake

Set this up once, properly. You will use the same loop — edit, save, look — for the next nine weeks.

Naming files · boring, and it will save you

Three rules.

Rule one causes the single most common "it works on my machine" failure in this course.

Git · three words for now

git addchoose — which changes count
git commitrecord — save them, with a message
git pushsend up — put them where the world can see

No branches. No merging. Those arrive when you need them — and not before.

Lesson 1.6

The three pillars

HTML · CSS · JavaScript — and why they are separate

The house

structure

HTML

HyperText Markup Language

The walls, rooms and doors.

What the thing is.

presentation

CSS

Cascading Style Sheets

Paint, furniture, light.

What it looks like.

behaviour

JavaScript

…no relation to Java

Plumbing and electricity.

What it does.

A house with no paint is still a house. A page with no CSS still works.

Every acronym in this course, spelled out

They all mean something.

HTMLHyperText Markup Language "HyperText" = text with links in it. Markup = you mark up plain text to say what each part is.
CSSCascading Style Sheets "Cascading" = when rules conflict, they fall through in a defined order. That order is a real topic in lesson 3.
HTTPHyperText Transfer Protocol The rules for moving that hypertext between machines. The S in HTTPS is Secure.
URLUniform Resource Locator A single agreed format for saying where a thing is.
DNSDomain Name System Turns a name people can remember into a number machines can route to.

Notice how many start with "HyperText". Links were the whole idea — everything else was built to serve them.

And the odd one out

JavaScript has nothing
to do with Java.

It was called LiveScript. It was renamed in 1995 because Java was popular and the marketing department wanted the association.

Two entirely different languages, one confusing name, thirty years of students asking the same question.

Why keep them apart?

Separation of concerns.

That last one is why this matters to you
in about three weeks.

All three, on one page

<!-- HTML: what it is -->
<button id="go">Click me</button>

/* CSS: what it looks like */
#go { background: #c2410c; color: white; }

// JavaScript: what it does
document.getElementById('go')
  .addEventListener('click', () => alert('Hello'));

Three languages, three jobs, one button.

When it goes wrong — and it will

Which of the three is broken?

What you seeWhere to look
text in the wrong place, tags showingHTML — an unclosed tag
it looks unstyledCSS — check the <link> path
the button does nothingJavaScript — open the Console
an image is missingthe path, almost always

The Console tells you which file and which line. Read the error before you change anything.

Lesson 1 · done

What you should be able to say now.

webtech.landrock.io/course

The full lessons, with the detail these slides skip.

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