Guides
Where the Reference describes what things are, Guides are task-oriented — how to actually get something done. They form a progression from your first PWA through the harder problems, and link back into the Reference and Compatibility data for the authoritative detail.
The learning path
Section titled “The learning path”Work top to bottom: each guide assumes the outcome of the one before it.
Getting startedBuild and ship your first installable PWA — manifest, service worker, installability.
Make it installableBeyond the bar: design the install moment and the launch experience.
Offline strategiesPick a caching strategy per request type; stay useful with no network.
PerformanceMeasure and move LCP, INP, and CLS; make launch feel instant.
AdvancedPush, file access, and platform integration as progressive enhancement.
How guides relate to the rest of the site
Section titled “How guides relate to the rest of the site”Guides are the how. They never restate the facts that live elsewhere:
- For what a thing is and how it behaves, guides link into the Reference.
- For where it works, guides link into the Compatibility data.
That keeps the facts in one place — a guide tells you the steps and cites the
reference entry or support matrix for the detail, so guidance never drifts from the
facts. Every guide carries sources and a lastVerified date, and is written to stay
current: it teaches a durable task, not a dated announcement.