How thtopher/muninn-tracker works
ODIN / Muninn is a static, browser-based tracker for a 30-week development plan. The principal workflow is to open the dashboard, navigate phases and weeks, review dates and milestones, and edit fields during a meeting; edits persist in that browser, and a week can be exported as a PDF. The README identifies index.html as the entry point and documents these capabilities, but no source excerpts were provided, so internal calls and implementation details cannot be verified.
Main entry points: index.html Tracker dashboard
Components 8
Tracker
- Tracker dashboard
index.html - Date and countdowns
index.html - Phase navigation
index.html - Week cards
index.html - Inline editing
index.html
Browser persistence
- Browser localStorage
index.html
PDF export
- Week PDF export
index.html
Other components
- Meeting user
Connections 7
- Meeting user → Tracker dashboard: opens
README.md - Tracker dashboard → Date and countdowns: shows
README.md - Tracker dashboard → Phase navigation: provides
README.md - Tracker dashboard → Week cards: shows
README.md - Meeting user → Inline editing: edits fields
README.md - Inline editing → Browser localStorage: auto-saves
README.md - Meeting user → Week PDF export: exports week
README.md