Course site UX backlog

Tracking issue for the course-site UX backlog.

These ideas were raised in a planning session on 2026-06-11, against the old static site (the netcup portal + course/ frontend). That site is a dead snapshot — course-v2 is the source of truth — so each item has been re-scoped for the Next.js app rather than carried over as-is. Recovered notes: course-development/2026-06-11-course-chat-notes.md in Anna's working copy.

Each child is deliberately sized to be one PR.

Backlog

• #3 — Site footer (docs, jobs, imprint)
• #4 — Path selector: decide what it means, then build or drop it
• #5 — Per-module quizzes
• #6 — Module completion screen with forward look and resources
• #7 — Reset progress, per module and all
• #8 — Per-section note-taking

Suggested order

#3 is the smallest and touches nothing else — a good warm-up. #7 is next: progress lives entirely in localStorage (lib/progress.ts), so it is self-contained, and having a reset makes testing every other item easier. #6 is high value for low effort, because the forward-look and resources data already exists in the manifest and markdown; it only needs surfacing.

#5 and #8 both extend what is stored client-side, so they should agree on a pattern — whoever does one first sets the convention. #4 needs a decision before any code, and closing it as "not needed" is a legitimate outcome.

Constraints that apply to all of these

• There are no accounts and no server state. Progress is per-browser localStorage. Anything that stores user data is one cleared browser away from gone, and the UI should not imply otherwise.
• Readers have existing localStorage data, so any change to the stored shape must tolerate the old one.
• ## headings in the content markdown are structural — each becomes a navigable, individually tracked section. Changing how sections are split changes readers' stored progress.

This is a tracking issue rather than a standalone change; start by reading child issues #3–#8 and the stated localStorage constraints. For progress-related work, inspect lib/progress.ts and the recovered planning notes at course-development/2026-06-11-course-chat-notes.md. Done means the backlog items are individually resolved or explicitly closed, with each child delivered as one PR.