The Life Starter
0 of 6 complete0%
Course Library · Lesson 1 of 6
Digital · Guided lesson

Choose a bounded offline asset set

About 29 minutes · 7 reading + 22 practice and checks
Time includes reading, practice, and questions. Extra videos or further study are optional.
See this course’s project requirements

A localhost reference-card app with an explicit asset cache, offline fallback, visible cache version and a controlled update/cleanup test.

Keep your working files in your own notebook or software. Save a private description, checklist, and work link in My Proof.

What to include

  • Create an exact cache inventory and a visible list of excluded offline behavior.
  • Record the local secure context and separate worker registration, installation, and page control.
  • Produce cache-entry evidence and a controlled required-asset failure/repair record.
  • Record actual cached reload and failed-network navigation fallback behavior separately.
  • Produce a controlled update/activation record proving the new version and bounded cache cleanup.
  • Deliver source, policy assertions, version evidence, performed browser tests, and scoped cleanup/limits.

Review and revise

Use these criteria to check your work and choose what to improve.

  • The implementation or declared simulation follows the supplied contract and retains inspectable original inputs.
  • Normal, boundary and rejected cases are recorded with expected versus observed results.
  • The changed case has a correct explanation and does not rely on hidden state.
  • The project includes source, outputs, instructions and honest tool, privacy and verification limits.
Open the full course project
Want more background?
Before you begin

The idea in everyday life

In a fresh dedicated folder place index.html, cards.css, offline.html, sw.mjs, cache-policy.mjs and test-cache.mjs. Serve only that folder with python3 -m http.server 8765 --bind 127.0.0.1 and open http://localhost:8765/index.html.

The idea

Offline support is an explicit promise about selected cached assets, not a promise that every URL or external service works offline.

Follow along

Choose a bounded offline asset set — original worked practice

Offline support is an explicit promise about selected cached assets, not a promise that every URL or external service works offline.

In a fresh dedicated folder place index.html, cards.css, offline.html, sw.mjs, cache-policy.mjs and test-cache.mjs. Serve only that folder with python3 -m http.server 8765 --bind 127.0.0.1 and open http://localhost:8765/index.html.

  1. 1. Step 1

    Read ASSETS in cache-policy.mjs and list the three exact paths.

    You should see: index.html, cards.css, and offline.html are selected.

    Offline support is an explicit promise about selected cached assets, not a promise that every URL or external service works offline.

  2. 2. Step 2

    Open index.html online and inspect its reference-card content.

    You should see: The card and stylesheet load from the local server.

    Offline support is an explicit promise about selected cached assets, not a promise that every URL or external service works offline.

  3. 3. Step 3

    Read the fetch handler: it ignores non-GET and other origins.

    You should see: The offline policy is limited to this local origin and GET resources.

    Offline support is an explicit promise about selected cached assets, not a promise that every URL or external service works offline.

  4. 4. Step 4

    Record the selected files and excluded data/remote services in a cache-scope table.

    You should see: An explicit offline asset and exclusion inventory.

    Offline support is an explicit promise about selected cached assets, not a promise that every URL or external service works offline.

Now change one thing

Add /private.json to the folder without changing ASSETS. Is it cached by the install list?

Your work

What to finish

Create an exact cache inventory and a visible list of excluded offline behavior.

Common mistake

Watch for this

Calling the whole website offline-ready after listing only a few assets.

How can I tell I understand it?

Demonstrate the rule: Offline support is an explicit promise about selected cached assets, not a promise that every URL or external service works offline. Use the supplied variant to distinguish a changed result from a broken implementation.

Try 3 questions

Quick knowledge check

Answer all 3 questions. Get at least 2 right and the lesson completes automatically.

Not yet passed

You’ll get an explanation for each answer. Signed in? Your results save to your account.

1Which file is in this reference app install cache?
2Why ignore requests to another origin here?
3What best describes the offline promise?
0 of 3 answeredApply the lesson to a short question, then review the explanation.
1
Finish this lesson

Pass the check. We’ll save the progress.

Answer all 3 questions above and get at least 2 right. You can review the explanations and try again.

Go to the knowledge check
Tools, templates, and lesson sources

Tools and templates

Tools open in a new tab so you can keep your place here.

Sources and further reading

Explore the references behind this lesson.

developer.mozilla.org — Service_Worker_API
Source & access notes · checked 2026-10-01

Relevant documented module/API behavior inspected during expansion authoring; actual execution evidence is recorded separately. No grant eligibility is established.

Access: Official page retrieved with the web reader on 2026-10-01. Documentation reading does not certify execution in every native tool or browser.

Reuse: Original local practice files, fictional data, worked examples and questions. Concepts paraphrased and linked; source exercises are not copied.

developer.mozilla.org — Cache
Source & access notes · checked 2026-10-01

Relevant documented module/API behavior inspected during expansion authoring; actual execution evidence is recorded separately. No grant eligibility is established.

Access: Official page retrieved with the web reader on 2026-10-01. Documentation reading does not certify execution in every native tool or browser.

Reuse: Original local practice files, fictional data, worked examples and questions. Concepts paraphrased and linked; source exercises are not copied.

Report a problem with this lesson

Tell us what went wrong. Please leave out personal information and private project contents.

No sign-in needed.