1.1free~10 min

What the web actually is

Artifact: A clear mental model: URL → file → render

1. Principle

A website exists because something handed the browser a file. That is the whole thing.

There are exactly four steps:

  1. You type a URL or click a link.
  2. Your browser asks a server for the file at that URL.
  3. The server sends back the file (a chunk of text).
  4. The browser reads the text and renders the page.

Everything you have ever seen on the web is the result of those four steps. The complexity of modern frameworks, deploy pipelines, and CDNs is just making the file richer and getting it to your browser faster. The four steps do not change.

2. Do (you try)

Open your browser and visit any website you use — Wikipedia, a news site, anything.

Right-click anywhere on the page → View page source (or press Ctrl+U on Windows, Cmd+Option+U on Mac).

A new tab opens showing a wall of text. That is the file the browser received. The page you were just looking at is the browser's interpretation of that text.

Spend two minutes scrolling. Do not try to understand it all. Just notice three things:

  1. It starts with <!DOCTYPE html> (or sometimes <!doctype html>) — same as your file from 1.0.
  2. It has <html>, <head>, <body> tags somewhere.
  3. There is a lot of text. Real websites are big files. That's fine — they grew over years.

Now pick one specific phrase from the rendered page (e.g. a headline). Use Ctrl+F in the view-source tab and search for it. It is there. The rendered text and the source text are the same characters.

3. Verify (how you know)

You should be able to answer two questions:

  1. The text you searched for — did you find it in the source? Yes/no. The answer is yes.
  2. Where did the file come from? The address bar of the source tab will start with view-source:https://.... The part after view-source: is the URL the file came from.

If both check out, you have confirmed the model: URL → file → render. Without writing any code.

4. Reference

Locked. Try it yourself first.