跳到正文
VibeFather
免费注册

用这个模板做的 3 个案例

同一份提示词,不同的 [VARIABLES] 变量。点一个在上方预览。

关于这个模板

这是一个长篇滚动叙事式图解,跟随一次网页请求从用户按下回车键到页面出现在屏幕上的全过程。七个全屏场景分别讲解地址栏、DNS 查询、跨路由器传输、TCP 握手、TLS 加密锁、服务器响应和最终渲染,之后是整个往返过程的快速回放和术语表。每个场景都将一段简短的阅读文字与一个随滚动变化的固定图表配对,每个图表都恰好有一个可交互控制项:输入域名并观察解析器链如何应答,拖动距离滑块查看跳数和延迟的变化,自己逐步执行 SYN、SYN-ACK 和 ACK,切换观察者在 HTTP 和 HTTPS 下分别能看到什么,提高丢包率观察数据包重传,或在缓存已预热的情况下重新加载页面。页眉中的进度条显示数据包当前所处的阶段,旁边是一个实时更新的往返计时器,控制项变化时计时器也会更新。视觉风格兼具编辑感与技术感:深海军蓝页面背景,纸质色调的阅读卡片配以易读的衬线字体,IP 地址、端口和请求头使用等宽字体标注,数据包用亮青色,握手和加密锁用琥珀色。包括抽象点状网络图在内的所有图表均以内联 SVG 绘制,因此构建产物中不含任何照片。本模板适合教师、课程作者、开发者关系推广人员,以及任何想要一步步解释系统工作原理的人。要改编本模板,只需更改发布方、标题、示例域名、页面路径和目标受众,文案和示例数据就会随之重写以保持一致。同样的结构也适用于其他“工作原理”类故事,例如支付、电子邮件投递或部署流水线。

模板提示词

在线演示就是用这份提示词原样做出来的,没有额外补充。其他案例只是改了 [VARIABLES] 变量的值。 提示词保持英文原版,国内常用的 AI 编程工具都能直接理解;下面附中文参考译文。

# How the Internet Works Explainer

Build this website exactly as described below. Replace the [VARIABLES] with your own values; keep everything else.

## Brief
A single-page scrollytelling explainer published by Northbeam Primers that follows one HTTPS request for https://kettleandcrumb.example/recipes/rye-sourdough from a laptop to an origin server and back. Seven full-height scenes (request, DNS lookup, router hops on an abstract dotted map, TCP handshake, TLS and the lock, the server's reply in packets, rendering) each pair three short reading beats with a sticky code-drawn SVG diagram and exactly one hands-on control. A header rail tracks the packet's stage and a running round-trip timer; a fast replay and a 14-term glossary close the story. When the variables change, all copy and sample data are rewritten to fit them; keep everything in src/content.ts.

- Audience: Curious readers who use the web every day but have never seen what happens underneath; also usable by teachers and developer advocates as a lesson page.
- Goal: Make one round trip feel concrete: the reader should finish knowing the seven stages in order, why distance and handshakes add time, and what the lock actually protects, and should have played with every control on the way.
- Tone: Calm, precise and friendly, like a good science editor: short sentences, everyday analogies used sparingly, exact numbers in monospace, no hype and no jokes at the reader's expense.

## Stack
- Framework: Vite 5 + vanilla TypeScript
- Styling: Tailwind CSS 3.4
- Libraries: vite 5 (MIT), typescript 5 (Apache-2.0), tailwindcss 3.4, postcss, autoprefixer (MIT), gsap 3 (core + ScrollTrigger) (GSAP Standard License (free, commercial use allowed)), lucide (vanilla package) (ISC), @fontsource-variable/space-grotesk (OFL-1.1), @fontsource-variable/source-serif-4 (OFL-1.1), @fontsource/ibm-plex-mono (OFL-1.1)
- Build: `npm run build` → static files in `dist/`. No backend, no server code, no external APIs.
- Setup:
  - Scaffold with the Vite vanilla-ts template. Single entry index.html with <title>[TOPIC] · [BRAND]</title> and <link rel="icon" href="./favicon.svg" type="image/svg+xml">; index.html holds only <div id="app"></div> and the script tag, main.ts builds the DOM from content.ts.
  - vite.config.ts: base './', build.outDir 'dist', build.sourcemap false, default esbuild minification. package.json scripts: dev = vite, build = tsc --noEmit && vite build, preview = vite preview.
  - tailwind.config.ts: content ['./index.html', './src/**/*.ts']; theme.extend.colors with every token from the Design section (ink, panel, raised, grid, hairline, fog, haze, paper, paper-ink, paper-muted, paper-rule, signal, amber, loss); fontFamily display ['Space Grotesk Variable', 'system-ui', 'sans-serif'], serif ['Source Serif 4 Variable', 'Georgia', 'serif'], mono ['IBM Plex Mono', 'ui-monospace', 'monospace'].
  - src/main.ts imports '@fontsource-variable/space-grotesk', '@fontsource-variable/source-serif-4', '@fontsource/ibm-plex-mono/400.css', '@fontsource/ibm-plex-mono/500.css', '@fontsource/ibm-plex-mono/600.css' and './styles.css', then calls gsap.registerPlugin(ScrollTrigger) once.
  - src/styles.css: @tailwind base/components/utilities, CSS variables for the colors, the .dot-grid background (radial-gradient dots 1px #1F2E4D every 22px), the blinking caret keyframes, the .packet-trail dash keyframes, and a @media (prefers-reduced-motion: reduce) block that removes sticky positioning and all animations.
  - src/content.ts holds every string and every number: hero copy, rail stage labels, the seven scenes (kicker, headline, three beats, callout text, control labels), DNS servers and per-step milliseconds, the three route presets with node names, coordinates and per-link milliseconds, handshake numbers, TLS certificate fields, response headers, waterfall labels, recap labels, glossary and footer. Scene modules only read from it. When the variable values change, rewrite the copy and regenerate the sample data in this file to fit them, keeping the same shapes and counts.
  - src/state.ts: a tiny store (get, set, subscribe) holding activeStage (0-7), distance ('city' | 'country' | 'ocean', default 'country'), lossPercent (0 | 5 | 10 | 15 | 20, default 0), warmReload (boolean), dnsCache (Set of looked-up domains, seeded with nothing) and handshakeStep (0-3). Export timeline(state) that returns the cumulative milestones described in the Pages section; the header timer, scene labels, waterfall and recap all read from it.
  - src/scenes/: one module per scene (request.ts, dns.ts, route.ts, tcp.ts, tls.ts, response.ts, render.ts, recap.ts), each exporting mount(sceneEl, store) that builds its SVG, wires its one control, and registers its ScrollTriggers. src/lib/svg.ts has helpers (el(tag, attrs), pathFromPoints, pointAt(path, t) using getPointAtLength); src/lib/motion.ts exports prefersReducedMotion from matchMedia('(prefers-reduced-motion: reduce)').
  - Icons: import individual icons from 'lucide' and render them with createElement(IconNode) so only used icons are bundled; size 18, stroke-width 1.75, color currentColor.
  - public/favicon.svg: the BRAND mark (see header) on a #0A1222 rounded square.
  - Write ASSETS.md at the project root listing the three Fontsource packages and lucide (source npm URL, author, license) and stating that every diagram and illustration is drawn in code in this project.

## Variables
- [BRAND] — Publisher or series name (default: "Northbeam Primers"). The invented publisher of the explainer, shown in the header wordmark, hero kicker, <title> and footer.
- [TOPIC] — Explainer headline (default: "How one web page reaches your laptop"). The question the page answers; used as the hero headline and in the <title>.
- [SITE_DOMAIN] — Example site being loaded (default: "kettleandcrumb.example"). The made-up site the reader 'visits'. Must end in a reserved name (.example or .test, or a subdomain of example.com) so it can never point at a real site. Used in the address bar, DNS records, certificate, headers and the mock page.
- [PAGE_PATH] — Page requested on that site (default: "/recipes/rye-sourdough"). The path in the address bar and in the GET line. The mock page drawn on the laptop in scene 7 shows content that fits this path.
- [AUDIENCE] — Who the page is for (default: "curious readers who use the web every day but have never seen what happens underneath"). Sets vocabulary, analogies and how much jargon each beat uses.
- [CREDIT] — keep a small "Template by VibeFather" link to https://vibefather.ai/t/how-the-internet-works-explainer in the footer (default: yes; delete this line to remove it)

The copy under Pages & Sections is written for the default values. If your values differ, rewrite every headline, paragraph, label and image for them — same length, tone and structure. Layout, colors, type and motion stay as described.
Keep all copy, image paths and links in one content file (for example `src/content.ts`), keyed by section, so the content can be swapped later without touching components.

## Design
### Colors
- ink `#0A1222` — Page background (deep navy) and the header background at 88% opacity
- panel `#0F1A30` — Diagram panels and the hero visual card
- raised `#15233F` — Raised surfaces inside diagrams: laptop lid, server units, node fills, control bar
- grid `#1F2E4D` — Dot grid, landmass dots, inactive links
- hairline `#2B3C61` — 1px borders on panels, chips and rail separators
- fog `#E6ECF7` — Primary text on navy (headlines, hero, glossary terms)
- haze `#95A3BF` — Secondary text and mono labels on navy
- paper `#F2ECDF` — Reading cards (scene beats) and glossary cards
- paper-ink `#18202F` — Body text on paper
- paper-muted `#5A6274` — Kickers, captions and footnotes on paper
- paper-rule `#DDD3C0` — Rules and mono callout borders on paper; callout fill #E9E1D0
- signal `#34E2F2` — The one signal accent: packets, active paths, active rail stage, focus rings, primary buttons (text on it is ink)
- amber `#F4A93B` — Handshake and lock states: TCP arrows, TLS messages, certificate card, lock badge, cache-hit badges
- loss `#FF6B81` — Dropped packets, failed lookups and retransmit labels only

### Typography
- Display: hero headline 64/68px desktop, 40/44px mobile, weight 600, tracking -0.02em; scene headlines 40/46px desktop, 30/36px mobile, weight 600; wordmark 17px weight 600; stage labels in the rail 12px weight 500 uppercase tracking 0.08em: Space Grotesk Variable (@fontsource-variable/space-grotesk) (OFL), weights 500/600/700
- Text: hero deck 21/32px weight 400; beat paragraphs 19/30px desktop, 17/27px mobile, weight 400; emphasis weight 600; glossary definitions 16/25px: Source Serif 4 Variable (@fontsource-variable/source-serif-4) (OFL), weights 400/600
- Mono: IP addresses, ports, headers, DNS records, kickers ('03 · Across the network'), hop and latency labels inside SVG (11-12px), the round-trip timer (15px weight 600, tabular figures), callout blocks 14/22px: IBM Plex Mono (@fontsource/ibm-plex-mono) (OFL), weights 400/500/600

### Layout & motion
- Spacing: 8px base unit. Content container max-width 1280px with 32px side padding (16px on mobile). Scenes have 120px vertical padding on desktop and 72px on mobile, beats are spaced 60vh apart on desktop and 40svh on mobile. Inside cards use 20-30px padding; inside diagrams keep at least 24px between labels and edges.
- Radius: Diagram panels 20px, hero visual card and recap panel 24px, reading cards 16px (14px mobile), callouts and inputs 10px, glossary cards 14px, buttons, chips and the timer pill 999px, packet squares 3px, packet tiles 4px.
- Motion: Scene structure uses CSS position: sticky for the diagram (not GSAP pin), and GSAP ScrollTrigger only to detect which beat is active. One ScrollTrigger per beat card: start 'top 65%', end 'bottom 65%', onToggle when isActive sets that scene's beat index (0-2). A beat change runs a GSAP timeline (0.7s, ease 'power3.inOut') from the current diagram state to that beat's target state with overwrite 'auto', so scrolling back up reverses cleanly.
- Motion: Beat cards: inactive cards sit at opacity 0.45; the active card goes to opacity 1 and translates from y 12px to 0 over 0.4s 'power2.out'.
- Motion: Packets: a 12x12px signal-colored rounded square (rx 3) with a 3px ink stripe across its top third (the 'header'), moved along SVG paths with a GSAP tween on a proxy {t: 0 → 1} that calls path.getPointAtLength(t * length) on update; ease 'none' between nodes, 0.12s pause at each router where the node ring pulses (scale 1 → 1.6, opacity 0.8 → 0 over 0.5s).
- Motion: Dashed trails: every active link is a 1.5px signal path with stroke-dasharray '3 6' revealed behind the packet using a second mask path whose stroke-dashoffset tweens from the path length to 0 in sync with the packet; once revealed, the dashes drift (stroke-dashoffset animates -18 per second, linear, infinite).
- Motion: Header round-trip timer counts up or down to the new milestone with a GSAP tween over 0.6s 'power2.out', rounding to whole milliseconds; the active rail packet dot slides between stage stops over 0.5s 'power3.inOut'.
- Motion: Hero: kicker, headline, deck and buttons fade up 16px in sequence (stagger 0.08s, 0.6s each) on load; the URL in the hero laptop types in at 32ms per character with a 2px signal caret blinking (steps(1) 1s); the hero packet loops along its path every 3.2s forever.
- Motion: Lock: the TLS lock is drawn in SVG; its shackle translates from y -6px (open, rotated -18deg around the right leg) to closed over 0.5s 'back.out(2)' and the badge flashes amber once.
- Motion: Micro-interactions: buttons and chips lift 1px on hover with a 150ms transition; focus-visible gets a 2px signal outline at 2px offset; segmented controls slide a raised thumb under the active option over 0.25s.
- Motion: prefers-reduced-motion: no typing, no looping packets, no drifting dashes, no tweens, no sticky diagrams. Each scene renders its diagram in the final beat state as a normal block after the intro text, beats follow as plain cards, and every control still works with instant (0s) updates.
- Imagery: No photographs and no raster images. Everything visual is inline SVG drawn in code: a neutral, generic laptop (rounded lid, plain window frame with one address field, no logo, no traffic-light buttons, no recognizable OS or browser chrome), a generic server rack (stacked units with LED dots), router nodes (6px circles with a 1.5px ring), an abstract dotted landmass map generated from math (dots on a grid kept inside a few overlapping ellipses with a sine-wobble edge, never traced from real geography), sequence diagrams, packet tiles and a simple mock web page on the laptop screen. Strokes are 1.5px, corners rounded, palette limited to the tokens above. The packet is always an abstract rounded square, never a character. Lucide icons appear only in UI controls.

## Pages & Sections
### [TOPIC] · [BRAND] (`index.html`)
1. **Header with journey rail and round-trip timer (shared, sticky)** — Left: the BRAND mark (20px SVG: a 4px signal dot with two concentric 1.5px arcs opening to the upper right, like a signal) plus the wordmark 'Northbeam Primers'. Center (desktop ≥1024px): the journey rail — seven stage stops labeled 'Request', 'DNS', 'Route', 'TCP', 'TLS', 'Response', 'Render', joined by a 1px hairline; each stop is a 7px ring; stops for stages already passed fill signal, the active stop shows the signal packet square sitting on it and its label turns fog (others haze). Clicking a stop smooth-scrolls to that scene (aria-label 'Go to scene 3: Across the network'). Right: the round-trip timer in a pill (hairline border, radius 999px, padding 6px 12px): Lucide Timer icon, mono label 'ROUND TRIP' haze 11px, value like '62 ms' mono 15px 600 fog with tabular figures. Before scene 1 is reached the timer shows '0 ms' and the rail stops are dim. Timer value = the cumulative milestone of the active stage from timeline(state): Request 0; DNS = dns; Route = dns + oneWay; TCP = dns + 2×oneWay; TLS = dns + 4×oneWay; Response = dns + 6×oneWay + 18 + lost×2×oneWay; Render = Response + 46; during the recap and glossary it shows the Render total. oneWay is 12, 38 or 96 ms from the distance control (default 38); dns is 24 ms. Defaults give 0, 24, 62, 100, 176, 270, 316 ms. Mobile (<1024px): mark only (no wordmark), then a compact label 'Stage 3 of 7 · Route' mono 12px, then the timer value without its label; a 2px signal progress bar along the header's bottom edge shows overall progress.
   Layout: Height 64px, position sticky top 0, z-index 50, background ink at 88% opacity with backdrop-blur 10px, bottom 1px hairline. Inner container max-width 1280px, padding 0 32px desktop / 0 16px mobile, three-part flex with the rail centered (max-width 620px).
   Motion: Active stop and timer update when a scene's first beat becomes active (ScrollTrigger on each scene section, start 'top 50%', end 'bottom 50%'). Timer tweens over 0.6s; packet square slides between stops over 0.5s. Mobile progress bar scaleX is scrubbed from the first scene to the end of the recap.
2. **Hero** — Kicker (mono 12px uppercase haze, tracking 0.08em): 'A Northbeam Primers explainer · 9-minute read · 7 scenes'. Headline (display): 'How one web page reaches your laptop'. Deck (serif, haze): 'You type an address, press Enter, and a recipe appears about a third of a second later. In between, your request asks for directions, crosses a string of machines that each know only the next step, shakes hands twice and comes back sealed. Scroll to follow it the whole way.' Buttons: primary 'Press Enter to start' with Lucide CornerDownLeft (signal fill, ink text, radius 999px, height 48px, padding 0 22px) smooth-scrolls to scene 1; secondary text link 'Jump to the glossary' (fog, underline offset 4px) scrolls to #glossary. Footnote under the buttons (mono 12px haze): 'Written for curious readers who use the web every day but have never seen what happens underneath. Every address on this page is made up; timings are illustrative.' Hero visual (right column, the visual anchor): a panel-colored card (radius 24px, 1px hairline border, .dot-grid background, subtle inner glow: radial-gradient of signal at 8% opacity behind the path) holding one SVG, viewBox 0 0 720 560, width 100%. Contents, back to front: (1) two abstract dotted landmasses in grid color (dots r 1.6 on a 14px grid) filling roughly the left 55% and right 30% of the card with an empty 'ocean' gap between; (2) a generic laptop bottom-left, lid x 40-340 y 250-470 (radius 14, raised fill, hairline stroke), screen inset 10px with a 26px window bar holding one 10px square and an address field pill (x 60-320) where the URL 'https://[SITE_DOMAIN][PAGE_PATH]' types in, mono 11px fog, truncated with an ellipsis; below the bar a page skeleton of three haze lines and one grid-colored image block; base a trapezoid 360px wide and 16px tall; (3) a generic server rack top-right at x 560-680 y 70-270: four 44px units with two LED dots each, one LED blinking signal; (4) a cubic path from the laptop screen's top-right corner to the rack's middle passing through five router nodes at roughly (380,300), (430,220), (500,250), (560,330), (610,290) — a smooth curve through them — drawn as a dashed signal trail with the looping packet; (5) an amber 28px lock badge just left of the rack; (6) mono labels in haze 11px: '192.0.2.10' under the laptop, '203.0.113.42 :443' under the rack, 'hop 4 · +8 ms' beside the third router; (7) a small floating stat card bottom-right (raised fill, radius 12px, padding 14px): label 'ROUND TRIP' mono 11px haze, value '316 ms' in display 28px fog, and a five-segment mini bar (DNS, TCP, TLS, request + wait, paint, widths proportional to 24/76/76/94/46) with TCP and TLS in amber and the rest in signal.
   Layout: Min-height calc(100svh - 64px). Desktop: container max-width 1280px, 12-column grid, gap 48px, text in columns 1-5 vertically centered, visual card in columns 6-12. Headline max-width 11ch. Mobile: single column, text first, visual card full width below it (aspect stays 720:560), side padding 16px, top padding 40px; the stat card shrinks to 70% scale.
   Motion: Load sequence and looping packet as in Design motion; the scroll cue is the primary button, no separate bouncing arrow.
3. **Scene 1 · The request (stage Request)** — Kicker: '01 · The request'. Headline: 'It starts as a line of text'. Beat 1: 'When you press Enter, the browser reads the address the way a mail clerk reads an envelope. https is how to talk, kettleandcrumb.example is who to talk to, and /recipes/rye-sourdough is what to ask for.' Beat 2: 'None of that is a location yet. Machines on the internet find each other by number, not by name, so before a single byte can leave, the browser needs the number behind the name.' Beat 3: 'It writes the message it wants to send, a few lines of plain text called an HTTP request, and puts it on hold.' Callout: 'GET /recipes/rye-sourdough HTTP/1.1' / 'Host: kettleandcrumb.example' / 'Accept: text/html'. Diagram (viewBox 0 0 640 480): a large generic laptop screen (x 40-600, y 40-300, raised fill, radius 16) with the window bar and the address field showing 'https://' + SITE_DOMAIN + PAGE_PATH in mono 16px. Under the field, three bracket lines (1.5px) mark the parts with labels in mono 12px: 'scheme' (signal), 'host' (amber), 'path' (fog). Below the laptop a request card (x 160-480, y 330-440, panel fill, radius 12) shows the GET lines in mono 12px with an amber pill 'waiting for an address' at its top-right. Beat states: beat 1 = URL shown and the three brackets draw in (stagger 0.15s); beat 2 = the host segment glows amber and a dotted line runs from it to a '?' circle labeled 'IP address: unknown'; beat 3 = the request card slides up 24px into view and its amber pill pulses once. Control: three segment chips in the control bar — 'https', 'kettleandcrumb.example', 'recipes/rye-sourdough' (chip text derived from the variables) — clicking one highlights that part of the URL and its bracket and sets the caption to: scheme → 'The protocol: speak HTTP, wrapped in encryption.'; host → 'The name of the machine to reach. It still has to be turned into a number.'; path → 'Which page to ask for once connected.'. Default selected: host.
   Layout: Each scene is a <section id='scene-N'> with padding 120px 0 (desktop) / 72px 0 (mobile). Scene intro (kicker, headline) sits at the top of the left column. Desktop ≥1024px: 12-column grid, gap 56px; left columns 1-5 hold three beat cards stacked with 60vh between them (first beat directly under the headline, last beat followed by 30vh of space); right columns 6-12 hold the diagram panel with position sticky, top 96px, height calc(100svh - 128px). Beat card: paper background, paper-ink serif text, radius 16px, padding 28px 30px, max-width 520px, one 1px paper-rule border, soft shadow 0 20px 40px -24px rgba(0,0,0,0.6). The mono callout (when a beat has one) is a block inside the card: background #E9E1D0, 1px paper-rule border, radius 10px, padding 14px 16px, IBM Plex Mono 14/22px paper-ink, horizontal scroll if needed. Diagram panel: panel background with .dot-grid, radius 20px, 1px hairline border, overflow hidden; SVG fills the top area (flex 1, preserveAspectRatio xMidYMid meet); a control bar docks at the bottom (raised background, top hairline, padding 14px 18px, min-height 64px) holding that scene's single control plus a one-line live caption in mono 12px haze. Mobile <1024px: kicker and headline first, then the diagram panel sticky at top 72px with height 52svh, then the three beat cards scroll up beneath it with 40svh gaps and full width (radius 14px, padding 20px). Under reduced motion nothing is sticky: intro, diagram (final state), then beats.
   Motion: Bracket lines draw with stroke-dashoffset over 0.5s; chip selection moves a raised highlight under the URL segment over 0.25s.
4. **Scene 2 · DNS lookup (stage DNS)** — Kicker: '02 · DNS lookup'. Headline: 'Asking for directions'. Beat 1: 'First the laptop checks its own memory. It has never visited kettleandcrumb.example, so it asks a resolver, a directory service usually run by your internet provider, to find out.' Beat 2: 'The resolver does not know either, but it knows who to ask. A root server points it to the servers for .example, those point it to the site's own nameserver, and that one finally answers: 203.0.113.42.' Beat 3: 'The answer comes with an expiry time, often five minutes to a day. Until then everyone along the way remembers it, which is why a second visit skips this whole step.' Callout: 'kettleandcrumb.example.   300   IN   A   203.0.113.42'. Diagram (viewBox 0 0 640 480): laptop icon-node at (80,240) labeled 'Your laptop · 192.0.2.10'; resolver node at (280,240) labeled 'Resolver (your ISP) · 192.0.2.53'; a column of three server nodes on the right at (520,100) 'Root server', (520,240) '.example servers' (TLD taken from SITE_DOMAIN), (520,380) 'ns1.kettleandcrumb.example' (ns1. + the registrable part of SITE_DOMAIN). Nodes are 64x44 raised rounded rectangles with a 1px hairline and a mono label below. Queries are signal arrows out, answers are amber arrows back, each with a numbered mono badge (1-8) and a millisecond label: laptop→resolver 1 ms, resolver↔root 9 ms, resolver↔TLD 7 ms, resolver↔authoritative 6 ms, resolver→laptop 1 ms (total 24 ms). A result card at the bottom center: '[SITE_DOMAIN] → 203.0.113.42 · 24 ms'. Beat states: beat 1 = a small loop arrow at the laptop marked 'cache: miss' (loss color) then arrow 1 to the resolver; beat 2 = arrows 2-7 play in sequence (0.35s each) with the right-hand servers lighting up in turn; beat 3 = arrow 8 returns, the result card appears and an amber 'TTL 300 s' badge attaches to the resolver. Control: a text input (mono 14px, ink background, hairline border, radius 10px, placeholder 'type a domain', prefilled with SITE_DOMAIN) with a 'Look up' button (Lucide Search) plus three preset chips: SITE_DOMAIN, 'mail.' + SITE_DOMAIN, 'weather.test'. Enter or the button runs the full chain for that domain. The answer for SITE_DOMAIN is always 203.0.113.42; any other accepted domain gets 203.0.113.(20 + (sum of its char codes % 200)). Accepted domains end in .example, .test, .invalid or example.com/.net/.org; anything else shows in loss color: 'This demo only looks up made-up names ending in .example or .test.' and does not animate. A domain already in dnsCache shows only the laptop loop arrow in amber with 'From laptop cache · 0 ms'. Caption shows the last result.
   Layout: Each scene is a <section id='scene-N'> with padding 120px 0 (desktop) / 72px 0 (mobile). Scene intro (kicker, headline) sits at the top of the left column. Desktop ≥1024px: 12-column grid, gap 56px; left columns 1-5 hold three beat cards stacked with 60vh between them (first beat directly under the headline, last beat followed by 30vh of space); right columns 6-12 hold the diagram panel with position sticky, top 96px, height calc(100svh - 128px). Beat card: paper background, paper-ink serif text, radius 16px, padding 28px 30px, max-width 520px, one 1px paper-rule border, soft shadow 0 20px 40px -24px rgba(0,0,0,0.6). The mono callout (when a beat has one) is a block inside the card: background #E9E1D0, 1px paper-rule border, radius 10px, padding 14px 16px, IBM Plex Mono 14/22px paper-ink, horizontal scroll if needed. Diagram panel: panel background with .dot-grid, radius 20px, 1px hairline border, overflow hidden; SVG fills the top area (flex 1, preserveAspectRatio xMidYMid meet); a control bar docks at the bottom (raised background, top hairline, padding 14px 18px, min-height 64px) holding that scene's single control plus a one-line live caption in mono 12px haze. Mobile <1024px: kicker and headline first, then the diagram panel sticky at top 72px with height 52svh, then the three beat cards scroll up beneath it with 40svh gaps and full width (radius 14px, padding 20px). Under reduced motion nothing is sticky: intro, diagram (final state), then beats.
   Motion: Arrows draw with stroke-dashoffset (0.35s each, 'power1.inOut'), a small packet square rides each arrow; server nodes flash their border signal for 0.4s when they answer.
5. **Scene 3 · Across the network (stage Route)** — Kicker: '03 · Across the network'. Headline: 'Hop by hop, never the whole map'. Beat 1: 'With an address in hand, the first message is cut into a packet: a small envelope with a from-address, a to-address and a little data. It leaves your laptop, passes your home router and enters your provider's network.' Beat 2: 'From there it is passed between routers, machines whose only job is forwarding packets. At this distance the trip takes 7 hops and about 38 milliseconds.' (the hop count, distance phrase and ms are live from the distance control: city 'Across town … 4 hops and about 12 milliseconds', country '7 hops and about 38 milliseconds', ocean 'Across an ocean … 10 hops and about 96 milliseconds'). Beat 3: 'No router knows the full route. Each one reads the destination, checks a table and hands the packet to the neighbor that is a little closer. If a link breaks, the next packet simply goes another way.' Callout: 'destination        next hop' / '203.0.113.0/24  →  198.51.100.9' / '0.0.0.0/0        →  198.51.100.1'. Diagram (viewBox 0 0 960 540): the abstract dotted map — a west landmass spanning x 30-570 and an east landmass spanning x 660-940 (grid dots r 1.6 every 14px inside overlapping ellipses with a sine-wobble edge), empty ocean between. Router nodes (r 6, raised fill, 1.5px haze ring; active ones ring signal) with mono 10px labels and a documentation IP (198.51.100.x) shown on hover/focus. Shared start: Laptop (90,360), Home router (140,330), Your ISP (200,300). City route: … Metro exchange (260,330), Data center edge (310,300), Origin server (350,270); link ms [1,3,3,3,2] = 12, 4 hops. Country route (default): … Regional hub (270,240), Backbone A (350,190), Backbone B (440,170), Exchange point (500,210), Data center edge (530,260), Origin server (555,300); link ms [1,3,4,7,8,7,5,3] = 38, 7 hops. Ocean route: … Regional hub (270,240), Backbone A (350,190), Backbone B (440,170), Coastal landing (545,150), Far landing (700,140) via a high arc across the ocean labeled 'undersea cable', Backbone C (770,180), Exchange point (830,230), Data center edge (860,290), Origin server (885,330); link ms [1,3,4,7,8,6,48,7,5,4,3] = 96, 10 hops. The laptop and origin server are small glyphs (laptop: rounded rectangle on a trapezoid; server: two stacked units) instead of circles. Each link shows a mono 10px '+N ms' label at its midpoint once the packet has crossed it. A HUD in the panel's top-left (mono 12px): 'HOP 0/7' and '0 ms' counting up as the packet passes nodes; top-right: '192.0.2.10 → 203.0.113.42'. Beat states: beat 1 = packet travels Laptop → Home router → Your ISP and stops; beat 2 = it continues along the chosen route to the origin server, counters run to the total; beat 3 = the Backbone B node opens a small table popover (raised card, mono 11px) showing the callout's two rows, and the alternate links of the other routes appear faintly dashed in grid color. Control: a three-stop segmented slider 'Server distance' with options 'Same city', 'Same country', 'Across an ocean' (default Same country). Changing it sets store.distance, redraws the route (old path fades out 0.3s, new path reveals 0.8s with the packet), updates the HUD, the beat 2 sentence and the header timer for every later stage. Caption: 'One way: 38 ms · 7 hops'.
   Layout: Each scene is a <section id='scene-N'> with padding 120px 0 (desktop) / 72px 0 (mobile). Scene intro (kicker, headline) sits at the top of the left column. Desktop ≥1024px: 12-column grid, gap 56px; left columns 1-5 hold three beat cards stacked with 60vh between them (first beat directly under the headline, last beat followed by 30vh of space); right columns 6-12 hold the diagram panel with position sticky, top 96px, height calc(100svh - 128px). Beat card: paper background, paper-ink serif text, radius 16px, padding 28px 30px, max-width 520px, one 1px paper-rule border, soft shadow 0 20px 40px -24px rgba(0,0,0,0.6). The mono callout (when a beat has one) is a block inside the card: background #E9E1D0, 1px paper-rule border, radius 10px, padding 14px 16px, IBM Plex Mono 14/22px paper-ink, horizontal scroll if needed. Diagram panel: panel background with .dot-grid, radius 20px, 1px hairline border, overflow hidden; SVG fills the top area (flex 1, preserveAspectRatio xMidYMid meet); a control bar docks at the bottom (raised background, top hairline, padding 14px 18px, min-height 64px) holding that scene's single control plus a one-line live caption in mono 12px haze. Mobile <1024px: kicker and headline first, then the diagram panel sticky at top 72px with height 52svh, then the three beat cards scroll up beneath it with 40svh gaps and full width (radius 14px, padding 20px). Under reduced motion nothing is sticky: intro, diagram (final state), then beats.
   Motion: Packet travel per the Design motion rules (ease none between nodes, 0.12s ring pulse at each router); per-link labels fade in as crossed; the trail keeps drifting after arrival.
6. **Scene 4 · TCP handshake (stage TCP)** — Kicker: '04 · TCP handshake'. Headline: 'Three messages to agree to talk'. Beat 1: 'Packets can arrive late, twice, out of order or not at all. To build a reliable conversation on top of that, the laptop and the server first agree on how they will count what they send.' Beat 2: 'The laptop sends SYN with a starting number. The server replies SYN-ACK: its own starting number, plus yours plus one, to prove it heard. The laptop answers ACK, and the connection is open.' Callout: 'SYN      seq=4100' / 'SYN-ACK  seq=9300  ack=4101' / 'ACK      seq=4101  ack=9301'. Beat 3: 'All of that costs one full round trip before any real data moves: 76 ms at this distance. It is one reason a server close to its readers feels faster, even on a fast connection.' (76 = 2×oneWay, live). Diagram (viewBox 0 0 640 480): a sequence diagram. Two vertical lanes as 1px hairline lines at x 140 and x 500 from y 90 to y 440, each topped by a header card: 'Your laptop' with '192.0.2.10:52814' and 'Origin server' with '203.0.113.42:443' (mono 12px haze). A thin 'time ↓' label in the left margin. Three diagonal amber arrows slanting downward: SYN from laptop (y 130) to server (y 190); SYN-ACK from server (y 210) back to laptop (y 270); ACK from laptop (y 290) to server (y 350). Each arrow carries a mono label pill (raised fill) with its flags and numbers from the callout. After ACK, a signal band (12px tall, radius 6) spans between the lanes at y 400 labeled 'connection open · 1 round trip = 76 ms'. Control: one step button in the control bar whose label cycles 'Send SYN' → 'Send SYN-ACK' → 'Send ACK' → 'Start over' (Lucide Play, last state Lucide RotateCcw); each click draws the next arrow with a packet riding it; 'Start over' clears the arrows. A three-dot step indicator sits next to the button. Caption explains the current step, e.g. 'Server: I hear you. Here is my number, and yours plus one.' Beat states (scroll does not draw arrows, the reader does): beat 1 = lanes and header cards appear; beat 2 = the button gets a 1.5s signal pulse ring if handshakeStep is 0; beat 3 = the round-trip brace (amber bracket on the left margin from y 130 to y 270, label '76 ms') draws in.
   Layout: Each scene is a <section id='scene-N'> with padding 120px 0 (desktop) / 72px 0 (mobile). Scene intro (kicker, headline) sits at the top of the left column. Desktop ≥1024px: 12-column grid, gap 56px; left columns 1-5 hold three beat cards stacked with 60vh between them (first beat directly under the headline, last beat followed by 30vh of space); right columns 6-12 hold the diagram panel with position sticky, top 96px, height calc(100svh - 128px). Beat card: paper background, paper-ink serif text, radius 16px, padding 28px 30px, max-width 520px, one 1px paper-rule border, soft shadow 0 20px 40px -24px rgba(0,0,0,0.6). The mono callout (when a beat has one) is a block inside the card: background #E9E1D0, 1px paper-rule border, radius 10px, padding 14px 16px, IBM Plex Mono 14/22px paper-ink, horizontal scroll if needed. Diagram panel: panel background with .dot-grid, radius 20px, 1px hairline border, overflow hidden; SVG fills the top area (flex 1, preserveAspectRatio xMidYMid meet); a control bar docks at the bottom (raised background, top hairline, padding 14px 18px, min-height 64px) holding that scene's single control plus a one-line live caption in mono 12px haze. Mobile <1024px: kicker and headline first, then the diagram panel sticky at top 72px with height 52svh, then the three beat cards scroll up beneath it with 40svh gaps and full width (radius 14px, padding 20px). Under reduced motion nothing is sticky: intro, diagram (final state), then beats.
   Motion: Each arrow draws over 0.6s 'power2.inOut' while a packet square rides it; the connection band grows from scaleX 0 over 0.5s after ACK.
7. **Scene 5 · TLS and the lock (stage TLS)** — Kicker: '05 · TLS and the lock'. Headline: 'Sealing the envelope'. Beat 1: 'Right now every packet could be read by anyone along the path: the café Wi-Fi, an office network, any router in between. HTTPS adds one more exchange, called TLS, before the request goes out.' Beat 2: 'The laptop and server swap fresh public keys and combine them into a shared secret only the two of them know. The server also shows a certificate, a signed statement that this key really belongs to kettleandcrumb.example.' Callout: 'Subject   kettleandcrumb.example' / 'Issuer    Demo Root Authority (invented)' / 'Valid     90 days' / 'Key       X25519 + ECDSA P-256'. Beat 3: 'Once the browser checks that signature, the lock closes. From here on the page and its contents are scrambled. Someone watching can still see which server you are talking to, but not what you asked for.' Diagram (viewBox 0 0 640 480), two stacked parts. Top (y 30-240): the same two lanes as scene 4, shorter, with three amber messages: 'ClientHello + key share', 'ServerHello + certificate + Finished', 'Finished'; a certificate card (raised fill, amber 1px border, radius 10, 180x96) beside the server lane listing the callout fields in mono 10px; a 40px lock badge centered between the lanes (amber ring, SVG body and shackle). Bottom (y 260-460): an inspector box titled 'What someone on the same Wi-Fi sees' (mono 11px haze) with a raised background and the packet contents in mono 12px. Control: a segmented toggle 'HTTP' | 'HTTPS' (default HTTPS). HTTP: the inspector shows the readable request in fog — 'GET /recipes/rye-sourdough HTTP/1.1', 'Host: kettleandcrumb.example', 'Cookie: basket=2-loaves; session=7f3a91c2', 'Accept: text/html' — with the cookie line underlined in loss color and the lock badge open; caption 'Readable by every machine on the path.' HTTPS: the inspector shows 'to 203.0.113.42:443 · name: kettleandcrumb.example' in fog (the visible part) and then six lines of 16 hex byte pairs in haze generated from a seeded PRNG (mulberry32 seed 42) so they are identical every load, the lock closed; caption 'Path, headers and cookies are scrambled.' Beat states: beat 1 = lanes appear, lock open, inspector shows the HTTP view dimmed; beat 2 = the three messages draw in sequence and the certificate card slides in from the right 16px; beat 3 = a check mark appears on the certificate and the lock closes; the toggle reflects HTTPS.
   Layout: Each scene is a <section id='scene-N'> with padding 120px 0 (desktop) / 72px 0 (mobile). Scene intro (kicker, headline) sits at the top of the left column. Desktop ≥1024px: 12-column grid, gap 56px; left columns 1-5 hold three beat cards stacked with 60vh between them (first beat directly under the headline, last beat followed by 30vh of space); right columns 6-12 hold the diagram panel with position sticky, top 96px, height calc(100svh - 128px). Beat card: paper background, paper-ink serif text, radius 16px, padding 28px 30px, max-width 520px, one 1px paper-rule border, soft shadow 0 20px 40px -24px rgba(0,0,0,0.6). The mono callout (when a beat has one) is a block inside the card: background #E9E1D0, 1px paper-rule border, radius 10px, padding 14px 16px, IBM Plex Mono 14/22px paper-ink, horizontal scroll if needed. Diagram panel: panel background with .dot-grid, radius 20px, 1px hairline border, overflow hidden; SVG fills the top area (flex 1, preserveAspectRatio xMidYMid meet); a control bar docks at the bottom (raised background, top hairline, padding 14px 18px, min-height 64px) holding that scene's single control plus a one-line live caption in mono 12px haze. Mobile <1024px: kicker and headline first, then the diagram panel sticky at top 72px with height 52svh, then the three beat cards scroll up beneath it with 40svh gaps and full width (radius 14px, padding 20px). Under reduced motion nothing is sticky: intro, diagram (final state), then beats.
   Motion: Messages draw like scene 4 arrows; switching the toggle crossfades the inspector text over 0.25s and HTTPS bytes scramble in (each pair cycles 3 random values over 0.3s before settling; instant under reduced motion); lock closes per Design motion.
8. **Scene 6 · The server answers (stage Response)** — Kicker: '06 · The server answers'. Headline: 'The answer comes back in pieces'. Beat 1: 'The sealed request arrives. The origin server opens it, finds the recipe and builds a reply: a status line, a few headers and 48,213 bytes of HTML.' Callout: 'HTTP/1.1 200 OK' / 'content-type: text/html; charset=utf-8' / 'content-length: 48213' / 'cache-control: max-age=300'. Beat 2: 'That reply is too big for one packet, so it is cut into numbered pieces. They travel back, sometimes by different routes, and the laptop puts them in order using those numbers.' Beat 3: 'If a piece goes missing, the laptop notices the gap and asks again, and the server resends it. Raise the packet loss to see what that costs.' Diagram (viewBox 0 0 640 480): server rack at right (x 500-600, y 80-260) with a response card fanning out of it (the callout lines in mono 11px); laptop glyph at left (x 40-200, y 300-420); between them three gently curved paths (top, middle, bottom) in grid color. Twelve packet tiles (28x20, radius 4, signal outline, mono 10px numbers 1-12) leave the server in order, alternating across the three paths, and land in a 4×3 reassembly grid drawn on the laptop screen in numerical order. A HUD top-left: 'PACKETS 12 · LOST 0 · RESENT 0'. Control: a slider 'Packet loss' with steps 0%, 5%, 10%, 15%, 20% (default 0%) and tick labels. lost = round(12 × p / 100) → 0, 1, 1, 2, 2; the lost tiles are taken in order from [7, 2, 10, 4]. Changing it replays the transfer: lost tiles turn loss color halfway along their path and fade out, their grid slot shows a dashed loss outline labeled 'gap', a small amber 'resend' arrow fires from the laptop to the server and the tile is re-sent last, filling its slot. Each lost packet adds 2×oneWay to the Response milestone. Caption: 'Transfer: 94 ms' at 0% (2×oneWay + 18 ms server time), e.g. '170 ms · 1 packet resent' at 5% on the default distance. Beat states: beat 1 = response card fans out of the rack; beat 2 = the transfer plays with the current loss value; beat 3 = the slider handle pulses once and the HUD highlights.
   Layout: Each scene is a <section id='scene-N'> with padding 120px 0 (desktop) / 72px 0 (mobile). Scene intro (kicker, headline) sits at the top of the left column. Desktop ≥1024px: 12-column grid, gap 56px; left columns 1-5 hold three beat cards stacked with 60vh between them (first beat directly under the headline, last beat followed by 30vh of space); right columns 6-12 hold the diagram panel with position sticky, top 96px, height calc(100svh - 128px). Beat card: paper background, paper-ink serif text, radius 16px, padding 28px 30px, max-width 520px, one 1px paper-rule border, soft shadow 0 20px 40px -24px rgba(0,0,0,0.6). The mono callout (when a beat has one) is a block inside the card: background #E9E1D0, 1px paper-rule border, radius 10px, padding 14px 16px, IBM Plex Mono 14/22px paper-ink, horizontal scroll if needed. Diagram panel: panel background with .dot-grid, radius 20px, 1px hairline border, overflow hidden; SVG fills the top area (flex 1, preserveAspectRatio xMidYMid meet); a control bar docks at the bottom (raised background, top hairline, padding 14px 18px, min-height 64px) holding that scene's single control plus a one-line live caption in mono 12px haze. Mobile <1024px: kicker and headline first, then the diagram panel sticky at top 72px with height 52svh, then the three beat cards scroll up beneath it with 40svh gaps and full width (radius 14px, padding 20px). Under reduced motion nothing is sticky: intro, diagram (final state), then beats.
   Motion: Tiles leave every 0.08s and travel 0.9s with 'power1.inOut'; landing tiles settle into their grid slot with a 4px drop; resend arrows draw over 0.4s.
9. **Scene 7 · Back on your screen (stage Render)** — Kicker: '07 · Back on your screen'. Headline: 'From bytes to a page'. Beat 1: 'The browser reads the HTML from top to bottom and starts drawing before it has everything. Text arrives first, then the styles that lay it out.' Beat 2: 'Along the way it finds more to fetch, a stylesheet and a drawing of the loaf, and each one repeats a shorter version of the trip, usually over the connection that is already open.' Beat 3: 'About a third of a second after you pressed Enter, the recipe is readable. Reload it and most of the trip is skipped: the address is cached, the connection is reused and much of the page is already on your laptop.' Diagram (viewBox 0 0 640 480): top part a large laptop screen (x 60-580, y 30-290) with the window bar and URL, showing a mock recipe page for the default site drawn in SVG: site name 'Kettle & Crumb' in a small display wordmark, title 'Rye Sourdough, Slow and Simple', a code-drawn loaf illustration (an amber-brown oval with three scored lines and a paper-colored plate ellipse), an ingredients list of four short lines ('500 g dark rye flour', '400 g water', '100 g active starter', '10 g salt') and a signal button shape 'Save recipe'. Bottom part (y 310-460): a waterfall chart with five rows (mono 11px labels left, bars right on a 0 to total ms scale with 4 tick marks): 'DNS 24', 'TCP 76', 'TLS 76', 'Request + wait 94', 'Paint 46' — bars amber for handshakes (TCP, TLS), signal for the rest, total line '316 ms' at the right. All numbers come from timeline(state). Beat states: beat 1 = page paints in layers: plain black-on-white text lines (0.3s), then styles (colors and layout snap in, 0.3s); beat 2 = the loaf illustration fades in last and a short secondary bar appears in the waterfall labeled 'loaf.svg 18 ms (same connection)'; beat 3 = the total line draws in and the reload button pulses. Control: a toggle button 'Reload (warm cache)' / 'First visit (cold)'. Warm: DNS 0 (amber 'cached' badge), TCP 0 and TLS 0 ('connection reused' badge), Request + wait 2×oneWay + 18 = 94, Paint 30, total 124 ms; bars tween to the new widths and the page repaints instantly. Caption: 'First visit: 316 ms' or 'Reload: 124 ms · 61% faster' (computed). Warm reload does not change the header timer, which always shows the first-visit trip.
   Layout: Each scene is a <section id='scene-N'> with padding 120px 0 (desktop) / 72px 0 (mobile). Scene intro (kicker, headline) sits at the top of the left column. Desktop ≥1024px: 12-column grid, gap 56px; left columns 1-5 hold three beat cards stacked with 60vh between them (first beat directly under the headline, last beat followed by 30vh of space); right columns 6-12 hold the diagram panel with position sticky, top 96px, height calc(100svh - 128px). Beat card: paper background, paper-ink serif text, radius 16px, padding 28px 30px, max-width 520px, one 1px paper-rule border, soft shadow 0 20px 40px -24px rgba(0,0,0,0.6). The mono callout (when a beat has one) is a block inside the card: background #E9E1D0, 1px paper-rule border, radius 10px, padding 14px 16px, IBM Plex Mono 14/22px paper-ink, horizontal scroll if needed. Diagram panel: panel background with .dot-grid, radius 20px, 1px hairline border, overflow hidden; SVG fills the top area (flex 1, preserveAspectRatio xMidYMid meet); a control bar docks at the bottom (raised background, top hairline, padding 14px 18px, min-height 64px) holding that scene's single control plus a one-line live caption in mono 12px haze. Mobile <1024px: kicker and headline first, then the diagram panel sticky at top 72px with height 52svh, then the three beat cards scroll up beneath it with 40svh gaps and full width (radius 14px, padding 20px). Under reduced motion nothing is sticky: intro, diagram (final state), then beats.
   Motion: Bars grow from width 0 with 'power2.out' over 0.6s, stagger 0.06s; numbers count up with the bars; reload toggle re-tweens bars over 0.4s.
10. **Recap: the whole trip at speed** — Kicker: 'Recap'. Headline (display, centered): 'The whole trip in four seconds'. Sub (serif, haze, centered, max-width 620px): 'Same request, start to finish, played back fast. The rail above lights up as it goes.' A full-width panel holds one SVG (viewBox 0 0 1200 380): laptop glyph at left (80,250), resolver node above it (220,90), a compressed strip of the current route's routers along a gentle arc across the middle, origin server at right (1120,250). Five labeled zones along the bottom in mono 11px with stage colors: 'DNS 24 ms', 'TCP 76 ms', 'TLS 76 ms', 'Request + response 94 ms', 'Paint 46 ms'. Replay sequence (4s total, scaled by stage duration with a minimum of 0.4s per stage): packet to resolver and back; three amber TCP ticks across the arc; three amber TLS ticks with the lock closing; request out in signal; twelve tiles back (resent tiles included if loss > 0); the laptop screen fills. The header rail's active stop advances in sync, then returns to Render. Under the panel a centered row of four stat blocks (display 40px fog value, mono 11px haze label): '316 ms' ROUND TRIP, '7' HOPS EACH WAY, '2' HANDSHAKES, '12' PACKETS BACK — all live from the store. Button: 'Replay the trip' (signal outline, Lucide RotateCcw). The replay runs once automatically the first time the panel is 50% in view.
   Layout: Section padding 140px 0 desktop / 80px 0 mobile, container max-width 1200px. Panel: panel background, .dot-grid, radius 24px, 1px hairline, padding 24px. Stats in a 4-column grid with 1px hairline dividers (2×2 on mobile). On mobile the SVG keeps its aspect ratio and scrolls horizontally inside the panel if narrower than 640px (the panel itself never overflows the page).
   Motion: One master GSAP timeline built from the stage durations; skipped entirely under reduced motion, where the panel shows the finished state and the button is hidden.
11. **Glossary** — id='glossary'. Kicker '14 terms', headline 'Words you picked up on the way'. Fourteen cards, each with the term in mono 15px 600 paper-ink, a scene tag pill (mono 10px, e.g. 'Scene 2') and a one- or two-sentence definition in serif 16px: URL — 'The full address you type: how to connect, which machine, which page.'; IP address — 'The number that identifies a machine on the network, such as 203.0.113.42.'; DNS — 'The internet's directory, which turns names into IP addresses.'; Resolver — 'The server that chases down a DNS answer for you and remembers it.'; TTL — 'How long an answer may be reused before someone has to ask again.'; Packet — 'A small envelope of data with a from-address and a to-address.'; Router — 'A machine that forwards packets one step closer to their destination.'; Hop — 'One router-to-router step on a packet's trip.'; Latency — 'The time a packet takes to travel, mostly set by distance.'; TCP — 'The rules that number packets, resend missing ones and keep them in order.'; Handshake — 'A short exchange that sets up a connection before data flows.'; TLS — 'The encryption layer that puts the S in HTTPS.'; Certificate — 'A signed statement that a key belongs to a particular site name.'; Round trip — 'There and back again: the time for a message and its reply.'. Clicking a card's scene tag scrolls to that scene.
   Layout: Section padding 120px 0, container max-width 1200px. Headline left-aligned in fog on navy. Cards in a 3-column grid (2 columns at 768-1023px, 1 column on mobile), gap 16px; each card paper background, radius 14px, padding 20px 22px, 1px paper-rule border.
   Motion: Cards fade up 12px in batches as they enter (ScrollTrigger.batch, stagger 0.05s); none under reduced motion.
12. **Footer** — Left: mark + 'Northbeam Primers' and a line in serif haze: 'Short visual explainers about the machines we use every day. Words by Ines Okafor, diagrams by Tomás Reyes.' Middle: a mono 12px note: 'Every IP address here comes from ranges reserved for documentation (192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24), and every domain ends in .example or .test. Timings are illustrative.' Right: links 'Back to top' (Lucide ArrowUp), 'Glossary', and plain text 'Next primer: How email finds its inbox · in progress'. Bottom row: '© Northbeam Primers' in mono 11px haze, and the optional [CREDIT] link at the far right if provided.
   Layout: Top 1px hairline, padding 56px 0 40px, container max-width 1280px, 3-column grid (stacked on mobile, gap 28px). Links fog, underline on hover.

## Assets
- image: No raster images, no downloads. Every visual — hero composition, laptop, server rack, router nodes, abstract dotted map, sequence diagrams, certificate card, packet tiles, mock recipe page and loaf drawing, waterfall chart — is inline SVG generated in TypeScript inside this project. The dotted landmasses are produced by a deterministic function (grid points kept inside overlapping ellipses with a sine-wobble edge), not traced from any map data.
- image: public/favicon.svg: the BRAND signal mark (4px signal dot plus two concentric arcs) on a #0A1222 rounded square, drawn by hand in SVG.
- icon: lucide (ISC), vanilla package, imported per icon and rendered with createElement: CornerDownLeft, Timer, Search, Play, RotateCcw, ArrowUp, Lock, LockOpen, Check. 18px, stroke-width 1.75, currentColor. Laptops, servers, routers and the lock badge inside diagrams are custom SVG, not icons.
- font: Self-hosted via npm: @fontsource-variable/space-grotesk, @fontsource-variable/source-serif-4 and @fontsource/ibm-plex-mono (weights 400, 500, 600), all OFL-1.1, imported in src/main.ts so Vite bundles the woff2 files into dist/.
- image: ASSETS.md at the project root: a table (path or package, source URL, author, license) with rows for the three Fontsource packages (https://www.npmjs.com/package/<name>, Fontsource / original type designers, OFL-1.1) and lucide (https://www.npmjs.com/package/lucide, Lucide Contributors, ISC), plus a line stating that all diagrams and illustrations are original code-drawn SVG in this project.

## Don'ts
- No backend of any kind: no server code, API routes, databases, auth, forms that submit anywhere or third-party APIs. No real DNS lookups, pings or network calls from the browser; every lookup, route and timing is computed from src/content.ts.
- Fonts only from the three Fontsource packages; never load fonts from fonts.googleapis.com, fonts.gstatic.com, Adobe Fonts or any other CDN, and no commercial fonts.
- No CDN script or link tags, no analytics, no remote images: every font, icon and script is bundled locally.
- Production build must be minified with no source maps (build.sourcemap false) and no src/ folder copied into dist/; dist/ stays well under 20 MB.
- Use relative paths (Vite base './'); internal links are in-page anchors or ./index.html, never a bare directory.
- Must work at 1440x900 and 390x844 with zero console errors and no horizontal page scroll.
- Respect prefers-reduced-motion: no typing, looping packets, drifting dashes, tweens or sticky diagrams; show each scene's final diagram state as a static figure with its control still usable.
- Exactly one interactive control per scene; do not add extra sliders, toggles or settings panels.
- Never name real companies, internet providers, cloud or CDN providers, browsers, operating systems or certificate authorities, and never show their logos; use generic labels such as 'Your ISP', 'Resolver', 'Root server', 'Origin server' and 'Demo Root Authority (invented)'.
- Do not draw a real browser's or operating system's chrome (no traffic-light buttons, tab shapes, icons or toolbars of a recognizable product); the laptop and window frame stay neutral and generic, with no logo on the lid.
- No real domain names and no real public IP addresses: domains end in .example or .test (or are example.com subdomains) and are built from [SITE_DOMAIN]; IPs come only from 192.0.2.0/24, 198.51.100.0/24 and 203.0.113.0/24.
- Do not copy copy, analogies, diagrams or illustration style from existing networking explainers, comics, courses or textbooks; use only the wording and diagrams described here.
- No real map tiles, map libraries, GeoJSON or traced country and coastline outlines; the map is abstract and generated in code.
- No mascot, character or guide figure, and no people illustrations; the packet is always an abstract rounded square.
- No code or components from Aceternity UI, Tailwind Plus / Tailwind UI or any paid template; build every effect from scratch. No React or other framework: vanilla TypeScript modules only.
- No dependency outside the listed libraries and licenses; no placeholder-image services, stock photos or brand logos.
- Keep all copy in US English in src/content.ts; when the variable values change, rewrite the copy, the mock page on the laptop, the DNS server names, headers and certificate subject to fit the new values instead of leaving the defaults.
- No SEO extras: no meta descriptions, Open Graph tags, JSON-LD or sitemaps; a plain <title> with [BRAND] and the SVG favicon are enough.
- No mention of VibeFather anywhere in the site except the optional credit link in the footer.

---
— Prompt by VibeFather · https://vibefather.ai/t/how-the-internet-works-explainer · CC BY-NC 4.0 (non-commercial; commercial use needs a VibeFather Pro license) · Request removal: https://vibefather.ai/takedown
中文参考译文(帮助理解,复制给 AI 时请用上面的英文原版)
# 互联网工作原理讲解站

完全按照以下描述构建此网站。将 [VARIABLES] 替换为你自己的值;其余内容保持不变。

## 简介
由 Northbeam Primers 发布的一个单页滚动叙事式讲解页面,追踪一次从笔记本电脑到源服务器再返回的、针对 https://kettleandcrumb.example/recipes/rye-sourdough 的 HTTPS 请求。七个全高场景(请求、DNS 查询、抽象点状地图上的路由器跳转、TCP 握手、TLS 与锁、服务器以数据包形式的回复、渲染),每个场景将三个简短的阅读节拍与一个粘性代码绘制的 SVG 图表以及恰好一个动手控件配对。一个头部轨道追踪数据包所处的阶段和一个运行中的往返计时器;一个快速重放和一份 14 词术语表为故事收尾。当变量变化时,所有文案和示例数据都会被重写以适配它们;将所有内容保留在 src/content.ts 中。

- 受众:每天使用网络但从未见过底层发生什么的好奇读者;也可供教师和开发者倡导者用作课程页面。
- 目标:让一次往返变得具体可感:读者最终应能按顺序了解七个阶段,理解为什么距离和握手会增加时间,以及锁究竟保护了什么,并且应在此过程中玩过每一个控件。
- 语气:冷静、精确且友好,像一位优秀的科学编辑:短句, sparingly 使用日常类比,精确数字用等宽字体,不炒作,不开以读者为代价的玩笑。

## 技术栈
- 框架:Vite 5 + 原生 TypeScript
- 样式:Tailwind CSS 3.4
- 库:vite 5(MIT)、typescript 5(Apache-2.0)、tailwindcss 3.4、postcss、autoprefixer(MIT)、gsap 3(核心 + ScrollTrigger)(GSAP Standard License(免费,允许商业使用))、lucide(原生包)(ISC)、@fontsource-variable/space-grotesk(OFL-1.1)、@fontsource-variable/source-serif-4(OFL-1.1)、@fontsource/ibm-plex-mono(OFL-1.1)
- 构建:`npm run build` → 静态文件输出到 `dist/`。无后端、无服务端代码、无外部 API。
- 设置:
  - 使用 Vite vanilla-ts 模板搭建脚手架。单一入口 index.html,包含 <title>[TOPIC] · [BRAND]</title> 和 <link rel="icon" href="./favicon.svg" type="image/svg+xml">;index.html 仅包含 <div id="app"></div> 和 script 标签,main.ts 从 content.ts 构建 DOM。
  - vite.config.ts:base './',build.outDir 'dist',build.sourcemap false,默认 esbuild 压缩。package.json 脚本:dev = vite,build = tsc --noEmit && vite build,preview = vite preview。
  - tailwind.config.ts:content ['./index.html', './src/**/*.ts'];theme.extend.colors 包含设计部分的所有令牌(ink、panel、raised、grid、hairline、fog、haze、paper、paper-ink、paper-muted、paper-rule、signal、amber、loss);fontFamily display ['Space Grotesk Variable', 'system-ui', 'sans-serif'],serif ['Source Serif 4 Variable', 'Georgia', 'serif'],mono ['IBM Plex Mono', 'ui-monospace', 'monospace']。
  - src/main.ts 导入 '@fontsource-variable/space-grotesk'、'@fontsource-variable/source-serif-4'、'@fontsource/ibm-plex-mono/400.css'、'@fontsource/ibm-plex-mono/500.css'、'@fontsource/ibm-plex-mono/600.css' 和 './styles.css',然后调用一次 gsap.registerPlugin(ScrollTrigger)。
  - src/styles.css:@tailwind base/components/utilities,颜色的 CSS 变量,.dot-grid 背景(径向渐变点 1px #1F2E4D 每 22px),闪烁光标关键帧,.packet-trail 虚线关键帧,以及一个 @media (prefers-reduced-motion: reduce) 块,移除粘性定位和所有动画。
  - src/content.ts 保存每个字符串和每个数字:hero 文案、轨道阶段标签、七个场景(kicker、headline、三个节拍、标注文本、控件标签)、DNS 服务器和每步毫秒数、三个路由预设及其节点名称、坐标和每链路毫秒数、握手数字、TLS 证书字段、响应头、瀑布图标签、回顾标签、术语表和页脚。场景模块仅从中读取。当变量值变化时,重写文案并重新生成此文件中的示例数据以适配它们,保持相同的形状和数量。
  - src/state.ts:一个小型存储(get、set、subscribe),持有 activeStage(0-7)、distance('city' | 'country' | 'ocean',默认 'country')、lossPercent(0 | 5 | 10 | 15 | 20,默认 0)、warmReload(布尔值)、dnsCache(已查找域名的 Set,初始为空)和 handshakeStep(0-3)。导出 timeline(state),返回 Pages 部分描述的累积里程碑;头部计时器、场景标签、瀑布图和回顾都从中读取。
  - src/scenes/:每个场景一个模块(request.ts、dns.ts、route.ts、tcp.ts、tls.ts、response.ts、render.ts、recap.ts),每个导出 mount(sceneEl, store),构建其 SVG、连接其一个控件并注册其 ScrollTriggers。src/lib/svg.ts 有辅助函数(el(tag, attrs)、pathFromPoints、pointAt(path, t) 使用 getPointAtLength);src/lib/motion.ts 从 matchMedia('(prefers-reduced-motion: reduce)') 导出 prefersReducedMotion。
  - 图标:从 'lucide' 导入单个图标并用 createElement(IconNode) 渲染,以便仅打包使用的图标;大小 18,描边宽度 1.75,颜色 currentColor。
  - public/favicon.svg:BRAND 标记(见头部)在 #0A1222 圆角方块上。
  - 在项目根目录编写 ASSETS.md,列出三个 Fontsource 包和 lucide(源 npm URL、作者、许可证),并声明本项目中的每个图表和插图均以代码绘制。

## 变量
- [BRAND] — 发布者或系列名称(默认:“Northbeam Primers”)。该解释页面的虚构发布者,显示在页眉字标、主视觉引导语、<title> 和页脚中。
- [TOPIC] — 解释页面标题(默认:“How one web page reaches your laptop”)。页面所回答的问题;用作主视觉标题和 <title> 中的标题。
- [SITE_DOMAIN] — 正在加载的示例站点(默认:“kettleandcrumb.example”)。读者“访问”的虚构站点。必须以保留名称结尾(.example 或 .test,或 example.com 的子域名),以确保它永远不会指向真实站点。用于地址栏、DNS 记录、证书、标头和模拟页面。
- [PAGE_PATH] — 在该站点上请求的页面(默认:“/recipes/rye-sourdough”)。地址栏和 GET 行中的路径。场景 7 中笔记本电脑上绘制的模拟页面显示与此路径匹配的内容。
- [AUDIENCE] — 页面的目标读者(默认:“curious readers who use the web every day but have never seen what happens underneath”)。决定词汇、类比以及每个节拍使用多少术语。
- [CREDIT] — 在页脚保留一个小型“Template by VibeFather”链接,指向 https://vibefather.ai/t/how-the-internet-works-explainer(默认:是;删除此行以移除它)

“页面与区块”下的文案是为默认值编写的。如果你的值不同,请为它们重写每个标题、段落、标签和图像——保持相同的长度、语气和结构。布局、颜色、字体和动效保持所述不变。
将所有文案、图像路径和链接放在一个内容文件中(例如 `src/content.ts`),按区块作为键,以便之后可以在不触及组件的情况下替换内容。

## 设计
### 颜色
- ink `#0A1222` — 页面背景(深海军蓝)以及 88% 不透明度的页头背景
- panel `#0F1A30` — 图表面板和主视觉卡片
- raised `#15233F` — 图表内部的凸起表面:笔记本电脑上盖、服务器单元、节点填充、控制栏
- grid `#1F2E4D` — 点阵网格、陆地点、非活动链接
- hairline `#2B3C61` — 面板、标签和轨道分隔线上的 1px 边框
- fog `#E6ECF7` — 海军蓝背景上的主文本(标题、主视觉、术语表词条)
- haze `#95A3BF` — 海军蓝背景上的次要文本和等宽标签
- paper `#F2ECDF` — 阅读卡片(场景节拍)和术语表卡片
- paper-ink `#18202F` — 纸张背景上的正文文本
- paper-muted `#5A6274` — 纸张背景上的引导语、说明文字和脚注
- paper-rule `#DDD3C0` — 纸张背景上的分隔线和等宽标注边框;标注填充色 #E9E1D0
- signal `#34E2F2` — 唯一的信号强调色:数据包、活动路径、活动轨道阶段、焦点环、主按钮(其上的文本为 ink)
- amber `#F4A93B` — 握手和锁定状态:TCP 箭头、TLS 消息、证书卡片、锁徽章、缓存命中徽章
- loss `#FF6B81` — 仅用于丢弃的数据包、失败的查找和重传标签

### 字体排印
- 展示字体:主视觉标题桌面端 64/68px,移动端 40/44px,字重 600,字距 -0.02em;场景标题桌面端 40/46px,移动端 30/36px,字重 600;字标 17px 字重 600;轨道中的阶段标签 12px 字重 500 大写字母 字距 0.08em:Space Grotesk Variable (@fontsource-variable/space-grotesk) (OFL),字重 500/600/700
- 文本:主视觉副标题 21/32px 字重 400;节拍段落桌面端 19/30px,移动端 17/27px,字重 400;强调字重 600;术语表定义 16/25px:Source Serif 4 Variable (@fontsource-variable/source-serif-4) (OFL),字重 400/600
- 等宽字体:IP 地址、端口、头部、DNS 记录、引导语('03 · Across the network')、SVG 内的跳数和延迟标签(11-12px)、往返计时器(15px 字重 600,表格数字)、标注块 14/22px:IBM Plex Mono (@fontsource/ibm-plex-mono) (OFL),字重 400/500/600

### 布局与动效
- 间距:8px 基础单位。内容容器最大宽度 1280px,两侧内边距 32px(移动端 16px)。场景在桌面端有 120px 垂直内边距,移动端 72px,节拍在桌面端间隔 60vh,移动端 40svh。卡片内部使用 20-30px 内边距;图表内部标签与边缘之间至少保持 24px。
- 圆角:图表面板 20px,主视觉卡片和回顾面板 24px,阅读卡片 16px(移动端 14px),标注和输入框 10px,术语表卡片 14px,按钮、标签和计时器胶囊 999px,数据包方块 3px,数据包瓦片 4px。
- 动效:场景结构使用 CSS position: sticky 实现图表(而非 GSAP pin),GSAP ScrollTrigger 仅用于检测哪个节拍处于活动状态。每个节拍卡片一个 ScrollTrigger:start 'top 65%',end 'bottom 65%',onToggle 时当 isActive 设置该场景的节拍索引(0-2)。节拍变化运行一个 GSAP 时间线(0.7s,ease 'power3.inOut'),从当前图表状态过渡到该节拍的目标状态,overwrite 'auto',因此向上滚动时能干净地反向播放。
- 动效:节拍卡片:非活动卡片处于不透明度 0.45;活动卡片变为不透明度 1,并在 0.4s 'power2.out' 内从 y 12px 平移到 0。
- 动效:数据包:一个 12x12px 信号色圆角方块(rx 3),顶部三分之一处有一条 3px ink 条纹(即"头部"),通过 GSAP 补间在代理 {t: 0 → 1} 上沿 SVG 路径移动,在 update 时调用 path.getPointAtLength(t * length);节点之间 ease 'none',在每个路由器处暂停 0.12s,此时节点环脉冲(scale 1 → 1.6,opacity 0.8 → 0,持续 0.5s)。
- 动效:虚线轨迹:每条活动链接是一条 1.5px 信号色路径,stroke-dasharray '3 6',使用第二条遮罩路径在数据包后方显现,其 stroke-dashoffset 与数据包同步从路径长度补间到 0;一旦显现,虚线漂移(stroke-dashoffset 以每秒 -18 线性无限动画)。
- 动效:页头往返计时器通过 GSAP 补间在 0.6s 'power2.out' 内向上或向下计数到新的里程碑,四舍五入到整毫秒;活动轨道数据包点在 0.5s 'power3.inOut' 内在阶段站点之间滑动。
- 动效:主视觉:引导语、标题、副标题和按钮在加载时依次淡入上移 16px(stagger 0.08s,每个 0.6s);主视觉笔记本电脑中的 URL 以每字符 32ms 的速度打字输入,2px 信号色光标闪烁(steps(1) 1s);主视觉数据包每 3.2s 沿其路径无限循环。
- 动效:锁定:TLS 锁在 SVG 中绘制;其锁梁从 y -6px(打开,绕右腿旋转 -18deg)在 0.5s 'back.out(2)' 内平移到闭合,徽章闪烁琥珀色一次。
- 动效:微交互:按钮和标签在悬停时上浮 1px,过渡 150ms;focus-visible 获得 2px 信号色轮廓,偏移 2px;分段控件在活动选项下方滑动一个凸起滑块,持续 0.25s。
- 动效:prefers-reduced-motion:无打字、无循环数据包、无漂移虚线、无补间、无粘性图表。每个场景在介绍文本之后以最终节拍状态将图表渲染为普通块,节拍作为普通卡片跟随,每个控件仍然以即时(0s)更新工作。
- 图像:无照片,无栅格图像。所有视觉元素均为代码绘制的内联 SVG:一台中性、通用的笔记本电脑(圆角上盖、带一个地址栏的普通窗口框架、无标志、无交通灯按钮、无可识别的操作系统或浏览器界面)、一个通用服务器机架(堆叠单元带 LED 点)、路由器节点(6px 圆带 1.5px 环)、一张由数学生成的抽象点状陆地地图(网格上的点保持在几个重叠椭圆内,边缘带正弦摆动,绝不描摹真实地理)、序列图、数据包瓦片以及笔记本电脑屏幕上的简单模拟网页。描边为 1.5px,圆角,调色板限于上述令牌。数据包始终是抽象圆角方块,绝不是字符。Lucide 图标仅出现在 UI 控件中。

## 页面与区块
### [TOPIC] · [BRAND] (`index.html`)
1. **带旅程轨道和往返计时器的页眉(共享,粘性)** — 左侧:BRAND 标记(20px SVG:一个 4px 信号点,带两条同心 1.5px 弧线向右上张开,像信号一样)加上字标 'Northbeam Primers'。中间(桌面端 ≥1024px):旅程轨道——七个阶段站点,标签为 'Request'、'DNS'、'Route'、'TCP'、'TLS'、'Response'、'Render',由一条 1px 细线连接;每个站点是一个 7px 圆环;已通过阶段的站点填充信号色,活动站点显示信号数据包方块停在其上,其标签变为雾色(其他为薄雾色)。点击站点平滑滚动到该场景(aria-label 'Go to scene 3: Across the network')。右侧:胶囊形往返计时器(细线边框,圆角 999px,内边距 6px 12px):Lucide Timer 图标,等宽标签 'ROUND TRIP' 薄雾色 11px,数值如 '62 ms' 等宽 15px 600 雾色,使用表格数字。到达场景 1 之前,计时器显示 '0 ms',轨道站点变暗。计时器值 = 来自 timeline(state) 的活动阶段的累计里程碑:Request 0;DNS = dns;Route = dns + oneWay;TCP = dns + 2×oneWay;TLS = dns + 4×oneWay;Response = dns + 6×oneWay + 18 + lost×2×oneWay;Render = Response + 46;在回顾和术语表期间显示 Render 总计。oneWay 根据距离控件为 12、38 或 96 ms(默认 38);dns 为 24 ms。默认值给出 0、24、62、100、176、270、316 ms。移动端(<1024px):仅标记(无字标),然后紧凑标签 'Stage 3 of 7 · Route' 等宽 12px,然后计时器数值不带标签;页眉底边一条 2px 信号进度条显示总体进度。
   布局:高度 64px,position sticky top 0,z-index 50,背景墨色 88% 不透明度,backdrop-blur 10px,底部 1px 细线。内部容器最大宽度 1280px,内边距桌面 0 32px / 移动 0 16px,三部分 flex,轨道居中(最大宽度 620px)。
   动效:当场景的第一个节拍变为活动时,活动站点和计时器更新(每个场景 section 上的 ScrollTrigger,start 'top 50%',end 'bottom 50%')。计时器在 0.6s 内补间;数据包方块在站点间滑动 0.5s。移动端进度条 scaleX 从第一个场景到回顾结束被擦洗。
2. **首屏** — 引导语(等宽 12px 大写薄雾色,字距 0.08em):'A Northbeam Primers explainer · 9-minute read · 7 scenes'。标题(展示字体):'How one web page reaches your laptop'。导语(衬线,薄雾色):'You type an address, press Enter, and a recipe appears about a third of a second later. In between, your request asks for directions, crosses a string of machines that each know only the next step, shakes hands twice and comes back sealed. Scroll to follow it the whole way.' 按钮:主按钮 'Press Enter to start' 带 Lucide CornerDownLeft(信号填充,墨色文字,圆角 999px,高度 48px,内边距 0 22px)平滑滚动到场景 1;次要文本链接 'Jump to the glossary'(雾色,下划线偏移 4px)滚动到 #glossary。按钮下方脚注(等宽 12px 薄雾色):'Written for curious readers who use the web every day but have never seen what happens underneath. Every address on this page is made up; timings are illustrative.' 首屏视觉(右列,视觉锚点):一个面板色卡片(圆角 24px,1px 细线边框,.dot-grid 背景,微妙内发光:路径后方信号色 8% 不透明度的 radial-gradient)包含一个 SVG,viewBox 0 0 720 560,宽度 100%。内容,从后到前:(1) 两个抽象点状陆块,网格色(点在 14px 网格上 r 1.6),填充卡片大约左侧 55% 和右侧 30%,中间有空白的"海洋"间隙;(2) 左下角一个通用笔记本电脑,盖子 x 40-340 y 250-470(圆角 14,凸起填充,细线描边),屏幕内缩 10px,带一个 26px 窗口栏,包含一个 10px 方块和一个地址字段胶囊(x 60-320),其中 URL 'https://[SITE_DOMAIN][PAGE_PATH]' 以等宽 11px 雾色输入,用省略号截断;栏下方是页面骨架,三条薄雾色线和一块网格色图像块;底座是 360px 宽、16px 高的梯形;(3) 右上角一个通用服务器机架,位于 x 560-680 y 70-270:四个 44px 单元,每个带两个 LED 点,一个 LED 闪烁信号色;(4) 一条立方体路径从笔记本电脑屏幕右上角到机架中部,经过五个路由器节点,大约在 (380,300)、(430,220)、(500,250)、(560,330)、(610,290)——一条穿过它们的平滑曲线——绘制为虚线信号轨迹,带循环数据包;(5) 机架左侧一个琥珀色 28px 锁徽章;(6) 薄雾色等宽标签 11px:笔记本电脑下方 '192.0.2.10',机架下方 '203.0.113.42 :443',第三个路由器旁 'hop 4 · +8 ms';(7) 右下角一个小浮动统计卡片(凸起填充,圆角 12px,内边距 14px):标签 'ROUND TRIP' 等宽 11px 薄雾色,数值 '316 ms' 展示字体 28px 雾色,以及一个五段迷你条(DNS、TCP、TLS、request + wait、paint,宽度与 24/76/76/94/46 成比例),TCP 和 TLS 为琥珀色,其余为信号色。
   布局:最小高度 calc(100svh - 64px)。桌面:容器最大宽度 1280px,12 列网格,间距 48px,文本在第 1-5 列垂直居中,视觉卡片在第 6-12 列。标题最大宽度 11ch。移动:单列,文本在前,视觉卡片全宽在其下方(宽高比保持 720:560),侧边内边距 16px,顶部内边距 40px;统计卡片缩小到 70% 比例。
   动效:加载序列和循环数据包如设计动效中所述;滚动提示是主按钮,没有单独弹跳箭头。
3. **场景 1 · 请求(阶段 Request)** — 引导语:'01 · The request'。标题:'It starts as a line of text'。节拍 1:'When you press Enter, the browser reads the address the way a mail clerk reads an envelope. https is how to talk, kettleandcrumb.example is who to talk to, and /recipes/rye-sourdough is what to ask for.' 节拍 2:'None of that is a location yet. Machines on the internet find each other by number, not by name, so before a single byte can leave, the browser needs the number behind the name.' 节拍 3:'It writes the message it wants to send, a few lines of plain text called an HTTP request, and puts it on hold.' 标注:'GET /recipes/rye-sourdough HTTP/1.1' / 'Host: kettleandcrumb.example' / 'Accept: text/html'。图表(viewBox 0 0 640 480):一个大通用笔记本电脑屏幕(x 40-600,y 40-300,凸起填充,圆角 16),带窗口栏和地址字段显示 'https://' + SITE_DOMAIN + PAGE_PATH 等宽 16px。字段下方,三条括号线(1.5px)标记各部分,等宽 12px 标签:'scheme'(信号色)、'host'(琥珀色)、'path'(雾色)。笔记本电脑下方一个请求卡片(x 160-480,y 330-440,面板填充,圆角 12)以等宽 12px 显示 GET 行,右上角一个琥珀色胶囊 'waiting for an address'。节拍状态:节拍 1 = 显示 URL,三条括号绘制进入(错开 0.15s);节拍 2 = 主机段发琥珀色光,一条虚线从它延伸到标有 'IP address: unknown' 的 '?' 圆圈;节拍 3 = 请求卡片向上滑入 24px 进入视图,其琥珀色胶囊脉冲一次。控件:控制栏中三个分段芯片——'https'、'kettleandcrumb.example'、'recipes/rye-sourdough'(芯片文本来自变量)——点击一个高亮 URL 的该部分及其括号,并将说明设置为:scheme → 'The protocol: speak HTTP, wrapped in encryption.';host → 'The name of the machine to reach. It still has to be turned into a number.';path → 'Which page to ask for once connected.'。默认选中:host。
   布局:每个场景是一个 <section id='scene-N'>,内边距 120px 0(桌面)/ 72px 0(移动)。场景介绍(引导语、标题)位于左列顶部。桌面 ≥1024px:12 列网格,间距 56px;左列 1-5 容纳三个节拍卡片堆叠,之间 60vh(第一个节拍直接在标题下方,最后一个节拍后跟 30vh 空间);右列 6-12 容纳图表面板,position sticky,top 96px,高度 calc(100svh - 128px)。节拍卡片:纸色背景,纸墨色衬线文本,圆角 16px,内边距 28px 30px,最大宽度 520px,一条 1px 纸规则边框,柔和阴影 0 20px 40px -24px rgba(0,0,0,0.6)。等宽标注(当节拍有时)是卡片内的块:背景 #E9E1D0,1px 纸规则边框,圆角 10px,内边距 14px 16px,IBM Plex Mono 14/22px 纸墨色,需要时水平滚动。图表面板:面板背景带 .dot-grid,圆角 20px,1px 细线边框,溢出隐藏;SVG 填充顶部区域(flex 1,preserveAspectRatio xMidYMid meet);控制栏停靠在底部(凸起背景,顶部细线,内边距 14px 18px,最小高度 64px)容纳该场景的单个控件加上一行等宽 12px 薄雾色实时说明。移动 <1024px:引导语和标题在前,然后图表面板粘性在 top 72px,高度 52svh,然后三个节拍卡片在其下方向上滚动,40svh 间隙,全宽(圆角 14px,内边距 20px)。在减少动效下没有粘性:介绍、图表(最终状态)、然后节拍。
   动效:括号线条通过 stroke-dashoffset 在 0.5s 内绘制;chip 选择在 0.25s 内将凸起高亮移动到 URL 段下方。
4. **场景 2 · DNS 查询(stage DNS)** — 引题:'02 · DNS lookup'。标题:'Asking for directions'。节拍 1:'First the laptop checks its own memory. It has never visited kettleandcrumb.example, so it asks a resolver, a directory service usually run by your internet provider, to find out.' 节拍 2:'The resolver does not know either, but it knows who to ask. A root server points it to the servers for .example, those point it to the site's own nameserver, and that one finally answers: 203.0.113.42.' 节拍 3:'The answer comes with an expiry time, often five minutes to a day. Until then everyone along the way remembers it, which is why a second visit skips this whole step.' 标注:'kettleandcrumb.example.   300   IN   A   203.0.113.42'。图示(viewBox 0 0 640 480):笔记本电脑图标节点位于 (80,240),标签为 'Your laptop · 192.0.2.10';解析器节点位于 (280,240),标签为 'Resolver (your ISP) · 192.0.2.53';右侧一列三个服务器节点分别位于 (520,100) 'Root server'、(520,240) '.example servers'(TLD 取自 SITE_DOMAIN)、(520,380) 'ns1.kettleandcrumb.example'(ns1. + SITE_DOMAIN 的可注册部分)。节点为 64x44 的凸起圆角矩形,带 1px 细线和下方等宽标签。查询为向外的信号箭头,应答为向回的琥珀色箭头,每个箭头带编号等宽徽章(1-8)和毫秒标签:laptop→resolver 1 ms,resolver↔root 9 ms,resolver↔TLD 7 ms,resolver↔authoritative 6 ms,resolver→laptop 1 ms(总计 24 ms)。底部中央的结果卡片:'[SITE_DOMAIN] → 203.0.113.42 · 24 ms'。节拍状态:节拍 1 = 笔记本电脑处出现一个小循环箭头,标记为 'cache: miss'(loss 颜色),然后箭头 1 指向解析器;节拍 2 = 箭头 2-7 依次播放(每个 0.35s),右侧服务器依次亮起;节拍 3 = 箭头 8 返回,结果卡片出现,一个琥珀色 'TTL 300 s' 徽章附着到解析器上。控件:一个文本输入框(等宽 14px,ink 背景,细线边框,圆角 10px,占位符 'type a domain',预填 SITE_DOMAIN)带一个 'Look up' 按钮(Lucide Search)以及三个预设 chip:SITE_DOMAIN、'mail.' + SITE_DOMAIN、'weather.test'。按 Enter 或点击按钮会为该域名运行完整链路。SITE_DOMAIN 的答案始终为 203.0.113.42;任何其他被接受的域名得到 203.0.113.(20 + (sum of its char codes % 200))。被接受的域名以 .example、.test、.invalid 或 example.com/.net/.org 结尾;其他任何内容以 loss 颜色显示:'This demo only looks up made-up names ending in .example or .test.' 并且不播放动画。已在 dnsCache 中的域名只显示笔记本电脑处的琥珀色循环箭头,并显示 'From laptop cache · 0 ms'。说明文字显示最后一次结果。
   布局:每个场景是一个 `<section id='scene-N'>`,内边距为 120px 0(桌面)/ 72px 0(移动端)。场景引言(引题、标题)位于左栏顶部。桌面 ≥1024px:12 列网格,间距 56px;左列 1-5 放置三张节拍卡片堆叠,彼此间隔 60vh(第一节拍紧接标题下方,最后一节拍后留 30vh 空间);右列 6-12 放置图示面板,position sticky,top 96px,高度 calc(100svh - 128px)。节拍卡片:paper 背景,paper-ink 衬线文字,圆角 16px,内边距 28px 30px,最大宽度 520px,一条 1px paper-rule 边框,柔和阴影 0 20px 40px -24px rgba(0,0,0,0.6)。等宽标注(当节拍有时)是卡片内的一个块:背景 #E9E1D0,1px paper-rule 边框,圆角 10px,内边距 14px 16px,IBM Plex Mono 14/22px paper-ink,必要时水平滚动。图示面板:panel 背景带 .dot-grid,圆角 20px,1px 细线边框,overflow hidden;SVG 填充顶部区域(flex 1,preserveAspectRatio xMidYMid meet);控制栏停靠在底部(raised 背景,顶部细线,内边距 14px 18px,最小高度 64px),容纳该场景的单个控件以及一行等宽 12px haze 的实时说明文字。移动端 <1024px:先显示引题和标题,然后图示面板 sticky 在 top 72px,高度 52svh,接着三张节拍卡片在其下方滚动上来,间隔 40svh,全宽(圆角 14px,内边距 20px)。在减少动效下没有任何 sticky:引言、图示(最终状态),然后是节拍。
   动效:箭头通过 stroke-dashoffset 绘制(每个 0.35s,'power1.inOut'),一个小数据包方块沿每个箭头移动;服务器节点在应答时其边框信号闪烁 0.4s。
5. **场景 3 · 穿越网络(stage Route)** — 引题:'03 · Across the network'。标题:'Hop by hop, never the whole map'。节拍 1:'With an address in hand, the first message is cut into a packet: a small envelope with a from-address, a to-address and a little data. It leaves your laptop, passes your home router and enters your provider's network.' 节拍 2:'From there it is passed between routers, machines whose only job is forwarding packets. At this distance the trip takes 7 hops and about 38 milliseconds.'(跳数、距离短语和毫秒数来自距离控件的实时值:城市 'Across town … 4 hops and about 12 milliseconds',国家 '7 hops and about 38 milliseconds',海洋 'Across an ocean … 10 hops and about 96 milliseconds')。节拍 3:'No router knows the full route. Each one reads the destination, checks a table and hands the packet to the neighbor that is a little closer. If a link breaks, the next packet simply goes another way.' 标注:'destination        next hop' / '203.0.113.0/24  →  198.51.100.9' / '0.0.0.0/0        →  198.51.100.1'。图示(viewBox 0 0 960 540):抽象点状地图——一个西部陆块横跨 x 30-570,一个东部陆块横跨 x 660-940(网格点 r 1.6,每 14px 一个,位于带正弦波动边缘的重叠椭圆内),中间是空海洋。路由器节点(r 6,raised 填充,1.5px haze 环;活动节点环为 signal),带等宽 10px 标签,悬停/聚焦时显示文档 IP(198.51.100.x)。共享起点:Laptop (90,360)、Home router (140,330)、Your ISP (200,300)。城市路线:… Metro exchange (260,330)、Data center edge (310,300)、Origin server (350,270);链路毫秒 [1,3,3,3,2] = 12,4 跳。国家路线(默认):… Regional hub (270,240)、Backbone A (350,190)、Backbone B (440,170)、Exchange point (500,210)、Data center edge (530,260)、Origin server (555,300);链路毫秒 [1,3,4,7,8,7,5,3] = 38,7 跳。海洋路线:… Regional hub (270,240)、Backbone A (350,190)、Backbone B (440,170)、Coastal landing (545,150)、Far landing (700,140) 经一条横跨海洋的高弧线,标记为 'undersea cable'、Backbone C (770,180)、Exchange point (830,230)、Data center edge (860,290)、Origin server (885,330);链路毫秒 [1,3,4,7,8,6,48,7,5,4,3] = 96,10 跳。笔记本电脑和源服务器是小字形(笔记本电脑:梯形上的圆角矩形;服务器:两个堆叠单元)而非圆形。每条链路在数据包穿过后在链路中点显示等宽 10px 的 '+N ms' 标签。面板左上角的 HUD(等宽 12px):'HOP 0/7' 和 '0 ms',随数据包经过节点而递增;右上角:'192.0.2.10 → 203.0.113.42'。节拍状态:节拍 1 = 数据包从 Laptop → Home router → Your ISP 行进并停止;节拍 2 = 它沿所选路线继续到源服务器,计数器运行到总计;节拍 3 = Backbone B 节点打开一个小表格弹出层(raised 卡片,等宽 11px),显示标注的两行,其他路线的备选链路以 grid 颜色的淡虚线出现。控件:一个三档分段滑块 'Server distance',选项为 'Same city'、'Same country'、'Across an ocean'(默认 Same country)。更改它会设置 store.distance,重绘路线(旧路径淡出 0.3s,新路径随数据包在 0.8s 内显现),更新 HUD、节拍 2 句子以及所有后续阶段的头部计时器。说明文字:'One way: 38 ms · 7 hops'。
   Layout: 每个场景是一个 `<section id='scene-N'>`,内边距为 120px 0(桌面端)/ 72px 0(移动端)。场景引言(kicker、headline)位于左栏顶部。桌面端 ≥1024px:12 列网格,间距 56px;左栏第 1-5 列放置三张 beat 卡片,卡片之间间隔 60vh(第一张 beat 紧接在 headline 下方,最后一张 beat 之后留 30vh 空间);右栏第 6-12 列放置图表面板,position sticky,top 96px,高度 calc(100svh - 128px)。Beat 卡片:paper 背景,paper-ink 衬线字体文本,圆角 16px,内边距 28px 30px,max-width 520px,1px paper-rule 边框,柔和阴影 0 20px 40px -24px rgba(0,0,0,0.6)。mono callout(当某个 beat 有时)是卡片内的一个块:背景 #E9E1D0,1px paper-rule 边框,圆角 10px,内边距 14px 16px,IBM Plex Mono 14/22px paper-ink,必要时水平滚动。图表面板:panel 背景带 .dot-grid,圆角 20px,1px hairline 边框,overflow hidden;SVG 填充顶部区域(flex 1,preserveAspectRatio xMidYMid meet);控制栏停靠在底部(raised 背景,顶部 hairline,内边距 14px 18px,min-height 64px),放置该场景的单个控件以及一行 mono 12px haze 的实时说明文字。移动端 <1024px:先显示 kicker 和 headline,然后图表面板 sticky 在 top 72px,高度 52svh,接着三张 beat 卡片在其下方向上滚动,间隔 40svh,全宽(圆角 14px,内边距 20px)。在 reduced motion 下没有任何 sticky:引言、图表(最终状态)、然后是 beats。
   Motion: 数据包按照 Design motion 规则移动(节点之间 ease none,每个路由器处 0.12s 环形脉冲);每条链路的标签在被穿过时淡入;到达后轨迹继续漂移。
6. **Scene 4 · TCP handshake(stage TCP)** — Kicker: '04 · TCP handshake'。Headline: 'Three messages to agree to talk'。Beat 1: 'Packets can arrive late, twice, out of order or not at all. To build a reliable conversation on top of that, the laptop and the server first agree on how they will count what they send.' Beat 2: 'The laptop sends SYN with a starting number. The server replies SYN-ACK: its own starting number, plus yours plus one, to prove it heard. The laptop answers ACK, and the connection is open.' Callout: 'SYN      seq=4100' / 'SYN-ACK  seq=9300  ack=4101' / 'ACK      seq=4101  ack=9301'。Beat 3: 'All of that costs one full round trip before any real data moves: 76 ms at this distance. It is one reason a server close to its readers feels faster, even on a fast connection.'(76 = 2×oneWay,实时)。图表(viewBox 0 0 640 480):一个序列图。两条垂直泳道为 1px hairline 线,位于 x 140 和 x 500,从 y 90 到 y 440,每条顶部有一个头部卡片:'Your laptop' 带 '192.0.2.10:52814' 和 'Origin server' 带 '203.0.113.42:443'(mono 12px haze)。左边距有一个细的 'time ↓' 标签。三个对角琥珀色箭头向下倾斜:SYN 从 laptop(y 130)到 server(y 190);SYN-ACK 从 server(y 210)回到 laptop(y 270);ACK 从 laptop(y 290)到 server(y 350)。每个箭头携带一个 mono 标签胶囊(raised 填充),上面有来自 callout 的标志和数字。ACK 之后,一个信号带(12px 高,圆角 6)在 y 400 处横跨两条泳道之间,标签为 'connection open · 1 round trip = 76 ms'。控件:控制栏中一个步骤按钮,其标签循环 'Send SYN' → 'Send SYN-ACK' → 'Send ACK' → 'Start over'(Lucide Play,最后状态为 Lucide RotateCcw);每次点击绘制下一个箭头,并有一个数据包骑在其上;'Start over' 清除箭头。按钮旁边有一个三点步骤指示器。说明文字解释当前步骤,例如 'Server: I hear you. Here is my number, and yours plus one.' Beat 状态(滚动不绘制箭头,由读者绘制):beat 1 = 泳道和头部卡片出现;beat 2 = 如果 handshakeStep 为 0,按钮获得 1.5s 信号脉冲环;beat 3 = 往返括号(左边距的琥珀色括号,从 y 130 到 y 270,标签 '76 ms')绘制进来。
   Layout: 每个场景是一个 `<section id='scene-N'>`,内边距为 120px 0(桌面端)/ 72px 0(移动端)。场景引言(kicker、headline)位于左栏顶部。桌面端 ≥1024px:12 列网格,间距 56px;左栏第 1-5 列放置三张 beat 卡片,卡片之间间隔 60vh(第一张 beat 紧接在 headline 下方,最后一张 beat 之后留 30vh 空间);右栏第 6-12 列放置图表面板,position sticky,top 96px,高度 calc(100svh - 128px)。Beat 卡片:paper 背景,paper-ink 衬线字体文本,圆角 16px,内边距 28px 30px,max-width 520px,1px paper-rule 边框,柔和阴影 0 20px 40px -24px rgba(0,0,0,0.6)。mono callout(当某个 beat 有时)是卡片内的一个块:背景 #E9E1D0,1px paper-rule 边框,圆角 10px,内边距 14px 16px,IBM Plex Mono 14/22px paper-ink,必要时水平滚动。图表面板:panel 背景带 .dot-grid,圆角 20px,1px hairline 边框,overflow hidden;SVG 填充顶部区域(flex 1,preserveAspectRatio xMidYMid meet);控制栏停靠在底部(raised 背景,顶部 hairline,内边距 14px 18px,min-height 64px),放置该场景的单个控件以及一行 mono 12px haze 的实时说明文字。移动端 <1024px:先显示 kicker 和 headline,然后图表面板 sticky 在 top 72px,高度 52svh,接着三张 beat 卡片在其下方向上滚动,间隔 40svh,全宽(圆角 14px,内边距 20px)。在 reduced motion 下没有任何 sticky:引言、图表(最终状态)、然后是 beats。
   Motion: 每个箭头在 0.6s 内以 'power2.inOut' 绘制,同时一个数据包方块骑在其上;连接带在 ACK 之后从 scaleX 0 开始,在 0.5s 内增长。
7. **Scene 5 · TLS and the lock(stage TLS)** — Kicker: '05 · TLS and the lock'。Headline: 'Sealing the envelope'。Beat 1: 'Right now every packet could be read by anyone along the path: the café Wi-Fi, an office network, any router in between. HTTPS adds one more exchange, called TLS, before the request goes out.' Beat 2: 'The laptop and server swap fresh public keys and combine them into a shared secret only the two of them know. The server also shows a certificate, a signed statement that this key really belongs to kettleandcrumb.example.' Callout: 'Subject   kettleandcrumb.example' / 'Issuer    Demo Root Authority (invented)' / 'Valid     90 days' / 'Key       X25519 + ECDSA P-256'。Beat 3: 'Once the browser checks that signature, the lock closes. From here on the page and its contents are scrambled. Someone watching can still see which server you are talking to, but not what you asked for.' 图表(viewBox 0 0 640 480),两个堆叠部分。顶部(y 30-240):与 scene 4 相同的两条泳道,更短,带有三条琥珀色消息:'ClientHello + key share'、'ServerHello + certificate + Finished'、'Finished';服务器泳道旁有一个证书卡片(raised 填充,琥珀色 1px 边框,圆角 10,180x96),以 mono 10px 列出 callout 字段;两条泳道之间居中有一个 40px 锁徽章(琥珀色环,SVG 锁体和锁梁)。底部(y 260-460):一个检查器框,标题为 'What someone on the same Wi-Fi sees'(mono 11px haze),带有 raised 背景,数据包内容以 mono 12px 显示。控件:一个分段切换 'HTTP' | 'HTTPS'(默认 HTTPS)。HTTP:检查器以 fog 显示可读请求——'GET /recipes/rye-sourdough HTTP/1.1'、'Host: kettleandcrumb.example'、'Cookie: basket=2-loaves; session=7f3a91c2'、'Accept: text/html'——其中 cookie 行以 loss 颜色加下划线,锁徽章打开;说明文字 'Readable by every machine on the path.' HTTPS:检查器以 fog 显示 'to 203.0.113.42:443 · name: kettleandcrumb.example'(可见部分),然后以 haze 显示六行 16 个十六进制字节对,由种子 PRNG(mulberry32 seed 42)生成,因此每次加载都相同,锁关闭;说明文字 'Path, headers and cookies are scrambled.' Beat 状态:beat 1 = 泳道出现,锁打开,检查器显示变暗的 HTTP 视图;beat 2 = 三条消息依次绘制,证书卡片从右侧滑入 16px;beat 3 = 证书上出现对勾,锁关闭;切换反映 HTTPS。
   布局:每个场景是一个 `<section id='scene-N'>`,内边距为 120px 0(桌面端)/ 72px 0(移动端)。场景引言(kicker、headline)位于左栏顶部。桌面端 ≥1024px:12 列网格,间距 56px;左栏第 1-5 列放置三张 beat 卡片,卡片之间间隔 60vh(第一张 beat 卡片紧接在 headline 下方,最后一张 beat 卡片之后留 30vh 空间);右栏第 6-12 列放置图表面板,使用 position sticky,top 96px,高度 calc(100svh - 128px)。Beat 卡片:paper 背景,paper-ink 衬线字体文本,圆角 16px,内边距 28px 30px,最大宽度 520px,1px paper-rule 边框,柔和阴影 0 20px 40px -24px rgba(0,0,0,0.6)。mono 标注框(当某个 beat 有时)是卡片内的一个块:背景 #E9E1D0,1px paper-rule 边框,圆角 10px,内边距 14px 16px,IBM Plex Mono 14/22px paper-ink,必要时水平滚动。图表面板:panel 背景配 .dot-grid,圆角 20px,1px 细线边框,overflow hidden;SVG 填充顶部区域(flex 1,preserveAspectRatio xMidYMid meet);控制栏停靠在底部(raised 背景,顶部细线,内边距 14px 18px,最小高度 64px),容纳该场景的单个控件以及一行 mono 12px haze 的实时说明文字。移动端 <1024px:先显示 kicker 和 headline,然后图表面板以 top 72px 粘性定位,高度 52svh,接着三张 beat 卡片在其下方滚动上来,间隔 40vh,全宽(圆角 14px,内边距 20px)。在 reduced motion 下没有任何粘性定位:引言、图表(最终状态),然后是 beats。
   动效:消息像场景 4 的箭头一样绘制;切换开关时,检查器文本在 0.25s 内交叉淡入淡出,HTTPS 字节乱序进入(每对在 0.3s 内循环 3 个随机值后稳定;在 reduced motion 下即时完成);锁按 Design motion 关闭。
8. **场景 6 · 服务器应答(stage Response)** — Kicker:'06 · The server answers'。Headline:'The answer comes back in pieces'。Beat 1:'The sealed request arrives. The origin server opens it, finds the recipe and builds a reply: a status line, a few headers and 48,213 bytes of HTML.' 标注框:'HTTP/1.1 200 OK' / 'content-type: text/html; charset=utf-8' / 'content-length: 48213' / 'cache-control: max-age=300'。Beat 2:'That reply is too big for one packet, so it is cut into numbered pieces. They travel back, sometimes by different routes, and the laptop puts them in order using those numbers.' Beat 3:'If a piece goes missing, the laptop notices the gap and asks again, and the server resends it. Raise the packet loss to see what that costs.' 图表(viewBox 0 0 640 480):服务器机架在右侧(x 500-600,y 80-260),带一张从其中展开的响应卡片(标注框各行以 mono 11px 呈现);笔记本电脑图形在左侧(x 40-200,y 300-420);两者之间有三条轻微弯曲的路径(上、中、下),使用 grid 颜色。十二个数据包方块(28x20,圆角 4,signal 描边,mono 10px 数字 1-12)按顺序离开服务器,交替经过三条路径,并按数字顺序落入绘制在笔记本电脑屏幕上的 4×3 重组网格。左上角 HUD:'PACKETS 12 · LOST 0 · RESENT 0'。控件:一个滑块 'Packet loss',步进为 0%、5%、10%、15%、20%(默认 0%)并带刻度标签。lost = round(12 × p / 100) → 0, 1, 1, 2, 2;丢失的方块按顺序从 [7, 2, 10, 4] 中选取。更改它会重放传输:丢失的方块在路径中途变为 loss 颜色并淡出,其网格槽位显示一个虚线 loss 轮廓,标注为 'gap',一个小的琥珀色 'resend' 箭头从笔记本电脑射向服务器,该方块最后被重新发送,填充其槽位。每个丢失的数据包会给 Response 里程碑增加 2×oneWay。说明文字:0% 时为 'Transfer: 94 ms'(2×oneWay + 18 ms 服务器时间),例如默认距离下 5% 时为 '170 ms · 1 packet resent'。Beat 状态:beat 1 = 响应卡片从机架中展开;beat 2 = 使用当前 loss 值播放传输;beat 3 = 滑块手柄脉冲一次,HUD 高亮。
   布局:每个场景是一个 `<section id='scene-N'>`,内边距为 120px 0(桌面端)/ 72px 0(移动端)。场景引言(kicker、headline)位于左栏顶部。桌面端 ≥1024px:12 列网格,间距 56px;左栏第 1-5 列放置三张 beat 卡片,卡片之间间隔 60vh(第一张 beat 卡片紧接在 headline 下方,最后一张 beat 卡片之后留 30vh 空间);右栏第 6-12 列放置图表面板,使用 position sticky,top 96px,高度 calc(100svh - 128px)。Beat 卡片:paper 背景,paper-ink 衬线字体文本,圆角 16px,内边距 28px 30px,最大宽度 520px,1px paper-rule 边框,柔和阴影 0 20px 40px -24px rgba(0,0,0,0.6)。mono 标注框(当某个 beat 有时)是卡片内的一个块:背景 #E9E1D0,1px paper-rule 边框,圆角 10px,内边距 14px 16px,IBM Plex Mono 14/22px paper-ink,必要时水平滚动。图表面板:panel 背景配 .dot-grid,圆角 20px,1px 细线边框,overflow hidden;SVG 填充顶部区域(flex 1,preserveAspectRatio xMidYMid meet);控制栏停靠在底部(raised 背景,顶部细线,内边距 14px 18px,最小高度 64px),容纳该场景的单个控件以及一行 mono 12px haze 的实时说明文字。移动端 <1024px:先显示 kicker 和 headline,然后图表面板以 top 72px 粘性定位,高度 52svh,接着三张 beat 卡片在其下方滚动上来,间隔 40vh,全宽(圆角 14px,内边距 20px)。在 reduced motion 下没有任何粘性定位:引言、图表(最终状态),然后是 beats。
   动效:方块每 0.08s 离开一个,以 'power1.inOut' 在 0.9s 内移动;落位的方块以 4px 下落稳定到其网格槽位;重发箭头在 0.4s 内绘制完成。
9. **场景 7 · 回到你的屏幕(stage Render)** — Kicker:'07 · Back on your screen'。Headline:'From bytes to a page'。Beat 1:'The browser reads the HTML from top to bottom and starts drawing before it has everything. Text arrives first, then the styles that lay it out.' Beat 2:'Along the way it finds more to fetch, a stylesheet and a drawing of the loaf, and each one repeats a shorter version of the trip, usually over the connection that is already open.' Beat 3:'About a third of a second after you pressed Enter, the recipe is readable. Reload it and most of the trip is skipped: the address is cached, the connection is reused and much of the page is already on your laptop.' 图表(viewBox 0 0 640 480):顶部是一个大的笔记本电脑屏幕(x 60-580,y 30-290),带窗口栏和 URL,显示默认站点的模拟食谱页面,以 SVG 绘制:站点名称 'Kettle & Crumb' 以小号展示字体字标呈现,标题 'Rye Sourdough, Slow and Simple',一个代码绘制的面包插图(一个琥珀棕色椭圆,带三条割痕和一个纸色盘子椭圆),四行简短配料列表('500 g dark rye flour'、'400 g water'、'100 g active starter'、'10 g salt')以及一个 signal 按钮形状 'Save recipe'。底部(y 310-460):一个瀑布图,包含五行(左侧 mono 11px 标签,右侧条形,使用 0 到总毫秒刻度,带 4 个刻度标记):'DNS 24'、'TCP 76'、'TLS 76'、'Request + wait 94'、'Paint 46' — 握手(TCP、TLS)的条形为琥珀色,其余为 signal,总计行 '316 ms' 在右侧。所有数字来自 timeline(state)。Beat 状态:beat 1 = 页面分层绘制:先是纯黑白文本行(0.3s),然后是样式(颜色和布局瞬间到位,0.3s);beat 2 = 面包插图最后淡入,瀑布图中出现一个短的次级条形,标注为 'loaf.svg 18 ms (same connection)';beat 3 = 总计行绘制出来,重新加载按钮脉冲。控件:一个切换按钮 'Reload (warm cache)' / 'First visit (cold)'。热缓存:DNS 0(琥珀色 'cached' 徽章),TCP 0 和 TLS 0('connection reused' 徽章),Request + wait 2×oneWay + 18 = 94,Paint 30,总计 124 ms;条形补间到新宽度,页面立即重绘。说明文字:'First visit: 316 ms' 或 'Reload: 124 ms · 61% faster'(计算得出)。热重载不会改变头部计时器,它始终显示首次访问的行程。
   布局:每个场景是一个 `<section id='scene-N'>`,内边距为 120px 0(桌面端)/ 72px 0(移动端)。场景引言(kicker、headline)位于左栏顶部。桌面端 ≥1024px:12 列网格,间距 56px;左侧第 1-5 列放置三张节拍卡(beat card)纵向堆叠,彼此间隔 60vh(第一张节拍卡紧接标题下方,最后一张节拍卡之后留 30vh 空间);右侧第 6-12 列放置图示面板,position sticky,top 96px,height calc(100svh - 128px)。节拍卡:paper 背景,paper-ink 衬线字体文本,圆角 16px,内边距 28px 30px,最大宽度 520px,1px paper-rule 边框,柔和阴影 0 20px 40px -24px rgba(0,0,0,0.6)。等宽字体标注框(当某个节拍有标注框时)是卡片内的一个块级元素:背景 #E9E1D0,1px paper-rule 边框,圆角 10px,内边距 14px 16px,IBM Plex Mono 14/22px paper-ink,必要时水平滚动。图示面板:panel 背景配 .dot-grid,圆角 20px,1px 细线边框,overflow hidden;SVG 填充顶部区域(flex 1,preserveAspectRatio xMidYMid meet);控制栏停靠在底部(raised 背景,顶部细线,内边距 14px 18px,最小高度 64px),容纳该场景的单个控件,外加一行等宽 12px haze 的实时说明文字。移动端 <1024px:先显示 kicker 和 headline,然后图示面板 sticky 在 top 72px、高度 52svh,接着三张节拍卡在其下方向上滚动,间隔 40vh,全宽(圆角 14px,内边距 20px)。在减少动态效果(reduced motion)下没有任何 sticky:引言、图示(最终状态),然后是节拍卡。
   动效:条形从宽度 0 开始,以 'power2.out' 在 0.6s 内增长,stagger 0.06s;数字随条形一起递增;重新加载开关以 0.4s 重新补间条形。
10. **回顾:全程高速回放** — Kicker:'Recap'。Headline(display,居中):'The whole trip in four seconds'。Sub(衬线,haze,居中,最大宽度 620px):'Same request, start to finish, played back fast. The rail above lights up as it goes.' 一个全宽面板容纳一个 SVG(viewBox 0 0 1200 380):左侧笔记本电脑图标(80,250),其上方解析器节点(220,90),中间沿平缓弧线排列当前路由路径的压缩路由器条带,右侧源服务器(1120,250)。底部沿水平方向有五个带标签的区域,等宽 11px,使用各阶段颜色:'DNS 24 ms'、'TCP 76 ms'、'TLS 76 ms'、'Request + response 94 ms'、'Paint 46 ms'。回放序列(总计 4s,按阶段时长缩放,每阶段最少 0.4s):数据包发往解析器并返回;弧线上三次琥珀色 TCP 刻度;三次琥珀色 TLS 刻度并伴随锁闭合;请求以 signal 色发出;十二个数据块返回(若 loss > 0 则包含重发的数据块);笔记本电脑屏幕填满。页眉导轨的活动停靠点同步推进,然后返回 Render。面板下方是一行居中的四个统计块(display 40px fog 数值,等宽 11px haze 标签):'316 ms' ROUND TRIP、'7' HOPS EACH WAY、'2' HANDSHAKES、'12' PACKETS BACK — 全部实时来自 store。按钮:'Replay the trip'(signal 描边,Lucide RotateCcw)。当面板首次有 50% 进入视口时,回放自动运行一次。
   布局:区块内边距 140px 0 桌面端 / 80px 0 移动端,容器最大宽度 1200px。面板:panel 背景,.dot-grid,圆角 24px,1px 细线,内边距 24px。统计块采用 4 列网格,1px 细线分隔(移动端 2×2)。移动端上 SVG 保持宽高比,若窄于 640px 则在面板内水平滚动(面板本身绝不溢出页面)。
   动效:一条由各阶段时长构建的主 GSAP 时间线;在减少动态效果下完全跳过,此时面板显示完成状态,按钮隐藏。
11. **术语表** — id='glossary'。Kicker '14 terms',headline 'Words you picked up on the way'。十四张卡片,每张包含等宽 15px 600 paper-ink 的术语、一个场景标签胶囊(等宽 10px,例如 'Scene 2')以及一句或两句衬线 16px 的定义:URL — 'The full address you type: how to connect, which machine, which page.';IP address — 'The number that identifies a machine on the network, such as 203.0.113.42.';DNS — 'The internet's directory, which turns names into IP addresses.';Resolver — 'The server that chases down a DNS answer for you and remembers it.';TTL — 'How long an answer may be reused before someone has to ask again.';Packet — 'A small envelope of data with a from-address and a to-address.';Router — 'A machine that forwards packets one step closer to their destination.';Hop — 'One router-to-router step on a packet's trip.';Latency — 'The time a packet takes to travel, mostly set by distance.';TCP — 'The rules that number packets, resend missing ones and keep them in order.';Handshake — 'A short exchange that sets up a connection before data flows.';TLS — 'The encryption layer that puts the S in HTTPS.';Certificate — 'A signed statement that a key belongs to a particular site name.';Round trip — 'There and back again: the time for a message and its reply.'。点击卡片的场景标签会滚动到该场景。
   布局:区块内边距 120px 0,容器最大宽度 1200px。Headline 在 navy 上以 fog 色左对齐。卡片采用 3 列网格(768-1023px 为 2 列,移动端 1 列),间距 16px;每张卡片 paper 背景,圆角 14px,内边距 20px 22px,1px paper-rule 边框。
   动效:卡片进入时以 12px 淡入上移,分批触发(ScrollTrigger.batch,stagger 0.05s);减少动态效果下无动效。
12. **页脚** — 左侧:标志 + 'Northbeam Primers' 以及一行衬线 haze 文字:'Short visual explainers about the machines we use every day. Words by Ines Okafor, diagrams by Tomás Reyes.' 中间:一条等宽 12px 注释:'Every IP address here comes from ranges reserved for documentation (192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24), and every domain ends in .example or .test. Timings are illustrative.' 右侧:链接 'Back to top'(Lucide ArrowUp)、'Glossary',以及纯文本 'Next primer: How email finds its inbox · in progress'。底部行:等宽 11px haze 的 '© Northbeam Primers',以及最右侧可选的 [CREDIT] 链接(若提供)。
   布局:顶部 1px 细线,内边距 56px 0 40px,容器最大宽度 1280px,3 列网格(移动端堆叠,间距 28px)。链接为 fog 色,悬停时下划线。

## 资产
- 图片:不使用任何栅格图像,也不进行任何下载。所有视觉元素——主视觉构图、笔记本电脑、服务器机架、路由器节点、抽象点阵地图、时序图、证书卡片、数据包图块、模拟食谱页面与面包图形、瀑布图——均为在本项目内用 TypeScript 生成的内联 SVG。点阵陆地轮廓由确定性函数生成(保留在相互重叠的椭圆内部的网格点,边缘带正弦波动),并非从任何地图数据描摹而来。
- 图片:public/favicon.svg:BRAND 信号标记(4px 信号点加两道同心弧),置于 #0A1222 圆角方块上,以 SVG 手工绘制。
- 图标:lucide(ISC),vanilla 包,按图标逐个导入并用 createElement 渲染:CornerDownLeft、Timer、Search、Play、RotateCcw、ArrowUp、Lock、LockOpen、Check。18px,stroke-width 1.75,currentColor。示意图中的笔记本电脑、服务器、路由器和锁徽标为自定义 SVG,并非图标。
- 字体:通过 npm 自托管:@fontsource-variable/space-grotesk、@fontsource-variable/source-serif-4 和 @fontsource/ibm-plex-mono(字重 400、500、600),均为 OFL-1.1,在 src/main.ts 中导入,以便 Vite 将 woff2 文件打包进 dist/。
- 图片:项目根目录下的 ASSETS.md:一张表(路径或包、来源 URL、作者、许可证),行包括三个 Fontsource 包(https://www.npmjs.com/package/<name>,Fontsource / 原字体设计师,OFL-1.1)和 lucide(https://www.npmjs.com/package/lucide,Lucide Contributors,ISC),另有一行说明所有示意图和插图均为本项目内原创的代码绘制 SVG。

## 不要做
- 任何形式的后端都不要:不要服务器代码、API 路由、数据库、认证、会向任何地方提交的表单或第三方 API。浏览器中不要进行真实的 DNS 查询、ping 或网络调用;每一次查询、路由和计时都由 src/content.ts 计算得出。
- 字体只能来自三个 Fontsource 包;绝不能从 fonts.googleapis.com、fonts.gstatic.com、Adobe Fonts 或任何其他 CDN 加载字体,也不要用商业字体。
- 不要 CDN 脚本或 link 标签,不要分析统计,不要远程图片:每个字体、图标和脚本都在本地打包。
- 生产构建必须压缩且不生成 source map(build.sourcemap false),并且不把 src/ 文件夹复制进 dist/;dist/ 要远小于 20 MB。
- 使用相对路径(Vite base './');内部链接是页内锚点或 ./index.html,绝不能是裸目录。
- 必须在 1440x900 和 390x844 下正常工作,控制台零报错,页面无横向滚动。
- 尊重 prefers-reduced-motion:不要打字效果、循环数据包、漂移虚线、补间动画或粘性图表;将每个场景的最终图表状态显示为静态图形,其控件仍可使用。
- 每个场景恰好一个交互控件;不要添加额外的滑块、开关或设置面板。
- 绝不要提及真实公司、互联网服务提供商、云或 CDN 提供商、浏览器、操作系统或证书颁发机构的名称,也绝不要显示它们的标志;使用通用标签,例如 'Your ISP'、'Resolver'、'Root server'、'Origin server' 和 'Demo Root Authority (invented)'。
- 不要绘制真实浏览器或操作系统的界面外壳(不要交通灯按钮、标签页形状、图标或可识别产品的工具栏);笔记本电脑和窗口边框保持中性通用,顶盖上不要有标志。
- 不要真实域名,也不要真实公网 IP 地址:域名以 .example 或 .test 结尾(或是 example.com 的子域名),并由 [SITE_DOMAIN] 构建;IP 只能来自 192.0.2.0/24、198.51.100.0/24 和 203.0.113.0/24。
- 不要复制现有网络科普、漫画、课程或教材中的文案、类比、图表或插画风格;只使用此处描述的措辞和图表。
- 不要真实地图瓦片、地图库、GeoJSON 或描摹的国家和海岸线轮廓;地图是抽象的,由代码生成。
- 不要吉祥物、角色或引导人物,也不要人物插画;数据包始终是一个抽象的圆角方块。
- 不要来自 Aceternity UI、Tailwind Plus / Tailwind UI 或任何付费模板的代码或组件;每个效果都从零构建。不要 React 或其他框架:只用原生 TypeScript 模块。
- 不要所列库和许可证之外的依赖;不要占位图服务、图库照片或品牌标志。
- 所有文案保持为 src/content.ts 中的美式英语;当变量值变化时,重写文案、笔记本电脑上的模拟页面、DNS 服务器名称、标头和证书主题以适配新值,而不是保留默认值。
- 不要 SEO 附加项:不要 meta 描述、Open Graph 标签、JSON-LD 或站点地图;一个包含 [BRAND] 的普通 <title> 和 SVG favicon 就足够了。
- 除页脚中可选的署名链接外,网站中任何地方都不要提及 VibeFather。

---
— Prompt by VibeFather · https://vibefather.ai/t/how-the-internet-works-explainer · CC BY-NC 4.0 (non-commercial; commercial use needs a VibeFather Pro license) · Request removal: https://vibefather.ai/takedown

个人项目可免费使用(CC BY-NC 4.0)。 商业用途需要 Pro.

DESIGN.md

单独的设计规范:配色、字体、间距和动效。可以把这套视觉用到你已有的项目上。

---
name: "How the Internet Works Explainer"
colors:
  ink: "#0A1222"
  panel: "#0F1A30"
  raised: "#15233F"
  grid: "#1F2E4D"
  hairline: "#2B3C61"
  fog: "#E6ECF7"
  haze: "#95A3BF"
  paper: "#F2ECDF"
  paper_ink: "#18202F"
  paper_muted: "#5A6274"
  paper_rule: "#DDD3C0"
  signal: "#34E2F2"
  amber: "#F4A93B"
  loss: "#FF6B81"
typography:
  display_hero_headline_64_68px_desktop_40_44px_mobile_weight_600_tracking_0_02em_scene_headlines_40_46px_desktop_30_36px_mobile_weight_600_wordmark_17px_weight_600_stage_labels_in_the_rail_12px_weight_500_uppercase_tracking_0_08em: { family: "Space Grotesk Variable (@fontsource-variable/space-grotesk)", weights: [500, 600, 700] }
  text_hero_deck_21_32px_weight_400_beat_paragraphs_19_30px_desktop_17_27px_mobile_weight_400_emphasis_weight_600_glossary_definitions_16_25px: { family: "Source Serif 4 Variable (@fontsource-variable/source-serif-4)", weights: [400, 600] }
  mono_ip_addresses_ports_headers_dns_records_kickers_03_across_the_network_hop_and_latency_labels_inside_svg_11_12px_the_round_trip_timer_15px_weight_600_tabular_figures_callout_blocks_14_22px: { family: "IBM Plex Mono (@fontsource/ibm-plex-mono)", weights: [400, 500, 600] }
spacing: "8px base unit. Content container max-width 1280px with 32px side padding (16px on mobile). Scenes have 120px vertical padding on desktop and 72px on mobile, beats are spaced 60vh apart on desktop and 40svh on mobile. Inside cards use 20-30px padding; inside diagrams keep at least 24px between labels and edges."
radius: "Diagram panels 20px, hero visual card and recap panel 24px, reading cards 16px (14px mobile), callouts and inputs 10px, glossary cards 14px, buttons, chips and the timer pill 999px, packet squares 3px, packet tiles 4px."
---

# How the Internet Works Explainer — Design System

Apply this design system to an existing project. It describes the look and feel only; for the full site, use prompt.md.

## Colors
- **ink** `#0A1222` — Page background (deep navy) and the header background at 88% opacity
- **panel** `#0F1A30` — Diagram panels and the hero visual card
- **raised** `#15233F` — Raised surfaces inside diagrams: laptop lid, server units, node fills, control bar
- **grid** `#1F2E4D` — Dot grid, landmass dots, inactive links
- **hairline** `#2B3C61` — 1px borders on panels, chips and rail separators
- **fog** `#E6ECF7` — Primary text on navy (headlines, hero, glossary terms)
- **haze** `#95A3BF` — Secondary text and mono labels on navy
- **paper** `#F2ECDF` — Reading cards (scene beats) and glossary cards
- **paper-ink** `#18202F` — Body text on paper
- **paper-muted** `#5A6274` — Kickers, captions and footnotes on paper
- **paper-rule** `#DDD3C0` — Rules and mono callout borders on paper; callout fill #E9E1D0
- **signal** `#34E2F2` — The one signal accent: packets, active paths, active rail stage, focus rings, primary buttons (text on it is ink)
- **amber** `#F4A93B` — Handshake and lock states: TCP arrows, TLS messages, certificate card, lock badge, cache-hit badges
- **loss** `#FF6B81` — Dropped packets, failed lookups and retransmit labels only

## Typography
- **Display: hero headline 64/68px desktop, 40/44px mobile, weight 600, tracking -0.02em; scene headlines 40/46px desktop, 30/36px mobile, weight 600; wordmark 17px weight 600; stage labels in the rail 12px weight 500 uppercase tracking 0.08em** — Space Grotesk Variable (@fontsource-variable/space-grotesk) (OFL), weights 500/600/700. Self-host the font files.
- **Text: hero deck 21/32px weight 400; beat paragraphs 19/30px desktop, 17/27px mobile, weight 400; emphasis weight 600; glossary definitions 16/25px** — Source Serif 4 Variable (@fontsource-variable/source-serif-4) (OFL), weights 400/600. Self-host the font files.
- **Mono: IP addresses, ports, headers, DNS records, kickers ('03 · Across the network'), hop and latency labels inside SVG (11-12px), the round-trip timer (15px weight 600, tabular figures), callout blocks 14/22px** — IBM Plex Mono (@fontsource/ibm-plex-mono) (OFL), weights 400/500/600. Self-host the font files.

## Spacing & shape
- Spacing: 8px base unit. Content container max-width 1280px with 32px side padding (16px on mobile). Scenes have 120px vertical padding on desktop and 72px on mobile, beats are spaced 60vh apart on desktop and 40svh on mobile. Inside cards use 20-30px padding; inside diagrams keep at least 24px between labels and edges.
- Radius: Diagram panels 20px, hero visual card and recap panel 24px, reading cards 16px (14px mobile), callouts and inputs 10px, glossary cards 14px, buttons, chips and the timer pill 999px, packet squares 3px, packet tiles 4px.

## Motion
- Scene structure uses CSS position: sticky for the diagram (not GSAP pin), and GSAP ScrollTrigger only to detect which beat is active. One ScrollTrigger per beat card: start 'top 65%', end 'bottom 65%', onToggle when isActive sets that scene's beat index (0-2). A beat change runs a GSAP timeline (0.7s, ease 'power3.inOut') from the current diagram state to that beat's target state with overwrite 'auto', so scrolling back up reverses cleanly.
- Beat cards: inactive cards sit at opacity 0.45; the active card goes to opacity 1 and translates from y 12px to 0 over 0.4s 'power2.out'.
- Packets: a 12x12px signal-colored rounded square (rx 3) with a 3px ink stripe across its top third (the 'header'), moved along SVG paths with a GSAP tween on a proxy {t: 0 → 1} that calls path.getPointAtLength(t * length) on update; ease 'none' between nodes, 0.12s pause at each router where the node ring pulses (scale 1 → 1.6, opacity 0.8 → 0 over 0.5s).
- Dashed trails: every active link is a 1.5px signal path with stroke-dasharray '3 6' revealed behind the packet using a second mask path whose stroke-dashoffset tweens from the path length to 0 in sync with the packet; once revealed, the dashes drift (stroke-dashoffset animates -18 per second, linear, infinite).
- Header round-trip timer counts up or down to the new milestone with a GSAP tween over 0.6s 'power2.out', rounding to whole milliseconds; the active rail packet dot slides between stage stops over 0.5s 'power3.inOut'.
- Hero: kicker, headline, deck and buttons fade up 16px in sequence (stagger 0.08s, 0.6s each) on load; the URL in the hero laptop types in at 32ms per character with a 2px signal caret blinking (steps(1) 1s); the hero packet loops along its path every 3.2s forever.
- Lock: the TLS lock is drawn in SVG; its shackle translates from y -6px (open, rotated -18deg around the right leg) to closed over 0.5s 'back.out(2)' and the badge flashes amber once.
- Micro-interactions: buttons and chips lift 1px on hover with a 150ms transition; focus-visible gets a 2px signal outline at 2px offset; segmented controls slide a raised thumb under the active option over 0.25s.
- prefers-reduced-motion: no typing, no looping packets, no drifting dashes, no tweens, no sticky diagrams. Each scene renders its diagram in the final beat state as a normal block after the intro text, beats follow as plain cards, and every control still works with instant (0s) updates.

## Imagery
No photographs and no raster images. Everything visual is inline SVG drawn in code: a neutral, generic laptop (rounded lid, plain window frame with one address field, no logo, no traffic-light buttons, no recognizable OS or browser chrome), a generic server rack (stacked units with LED dots), router nodes (6px circles with a 1.5px ring), an abstract dotted landmass map generated from math (dots on a grid kept inside a few overlapping ellipses with a sine-wobble edge, never traced from real geography), sequence diagrams, packet tiles and a simple mock web page on the laptop screen. Strokes are 1.5px, corners rounded, palette limited to the tokens above. The packet is always an abstract rounded square, never a character. Lucide icons appear only in UI controls.

## Tone
Calm, precise and friendly, like a good science editor: short sentences, everyday analogies used sparingly, exact numbers in monospace, no hype and no jokes at the reader's expense.

---
— Prompt by VibeFather · https://vibefather.ai/t/how-the-internet-works-explainer · CC BY-NC 4.0 (non-commercial; commercial use needs a VibeFather Pro license) · Request removal: https://vibefather.ai/takedown

改成你自己的

  • 学校计算机教师:将 BRAND 设为你的院系,AUDIENCE 设为中学生,并简化术语表和阅读段落文案以匹配课程内容。
  • 撰写入门文档的开发者关系推广人员:保留七个场景,将 TOPIC 设为你的平台的请求流程,并将 SITE_DOMAIN 指向一个保留的演示主机。
  • 支付课程作者:复用场景结构来讲解银行卡授权,重写每个段落,并为每个场景设置一个控制项,例如拒付开关。
  • 电子邮件送达率讲解者:将 PAGE_PATH 放在一边,把各阶段重新命名为发送、中继和收件箱投递,并保留往返计时器作为总投递时间。

互联网工作原理图解:常见问题

在“互联网工作原理图解”的每个场景中,我实际上能做些什么?

七个场景中的每一个都将一段简短的阅读文字与一个固定图表和恰好一个控制项配对。你可以输入域名并观察解析器链如何应答,拖动距离滑块改变跳数和延迟,逐步执行 SYN、SYN-ACK 和 ACK,切换观察者在 HTTP 和 HTTPS 下分别能看到什么,提高丢包率观察数据包重传,或在缓存已预热的情况下重新加载。进度条和往返计时器会随着你的操作实时更新。

“互联网工作原理图解”可以免费使用吗?Pro 能让我获得什么?

“互联网工作原理图解”是一个免费模板。其提示词和所有 DESIGN.md 在 CC BY-NC 4.0 许可下可免费用于个人非商业用途。商业和客户项目需要使用 Pro,Pro 会员还可获得完整提示词和演示的源代码。无论哪种情况,简介、技术栈和变量都会在页面上公开展示。

怎么用 AI 做一个互联网工作原理图解?

复制本页的提示词,或者运行 npx vibefather add how-the-internet-works-explainer,把 [BRAND]、[TOPIC]、[AUDIENCE]、[PAGE_PATH] 换成你自己的内容,再粘贴到 Claude Code、Codex、Cursor 等 AI 编程工具里。在线演示就是用这份提示词原样做出来的。