week-3/
Week 3: Signal + State
"How does an interface remember what a user asked it to do?"
Curriculum content for this week is coming soon.
What you'll learn
- Refactor portfolio styles into a token-driven system using `variables.css`
- Implement theme state with `data-theme` instead of presentation-only classes
- Persist user preferences with `localStorage`
- Apply a preference hierarchy (user choice -> system -> default)
- Use `matchMedia` for system preference detection
- Respect `prefers-reduced-motion` in both CSS and JavaScript decisions
- Prepare Project 1 for submission as a coherent signal-and-state system
Select a file from the sidebar to view its contents.