Summary
Merged into features/daily-pages-assignments.md
3Questions
0Links
0Comments
0PRs
Open questions
- 1 Visual treatment: separate tab? Collapsed group within the existing list? Filter chip?
- 2 Bulk archival: at what cadence — per-day, per-week? Manual or automatic?
- 3 Counter design: what's the most useful headline number for a teacher who runs daily pages constantly?
Spec body
# Daily pages dashboard decluttering Daily pages are working well — too well. Teachers want to use them every day, which is the right kind of problem, but each cycle creates a fresh batch of submissions cluttering the gradebook. ## Problem Reported 2026-03-06: "The problem with daily pages is it's so good I want to use it everyday. The only problem with that is once they submit it then it's sort of just sitting in my submitted file and the file gets cluttered by the time they start writing on their essays." The dashboard's per-document counters (e.g., "71 papers in progress") are no longer meaningful when most of them are daily-pages instances. The submitted count is similarly diluted — the teacher doesn't actually have 71 essays to grade; most are daily pages that don't need traditional grading. ## Goals (rough) - Daily-pages submissions are visually and structurally separated from essay submissions in the dashboard. - Per-counter breakdowns distinguish "essays to grade" from "daily pages submitted" — the dashboard signal stays meaningful at scale. - A teacher running daily pages every day for a month doesn't have the dashboard turn into a wall of identical-looking entries. - Easy bulk actions on daily pages: archive a day's batch, mark them all as reviewed, etc. ## Non-goals - Hiding daily pages entirely. Teachers want them visible — just organized. - Auto-grading of daily pages without teacher input. See [features/daily-pages-rubric.md](daily-pages-rubric.md) for the criteria conversation. ## Domain notes Depends on daily-pages submissions being a distinguishable type from essay submissions in the data model. May need a `submission.type` enum or a parent AssignmentType marker. Closely related to [features/released-grades-organization.md](released-grades-organization.md) — that spec covers the released side; this one covers the in-progress / submitted side. Both need the AssignmentType model to land first. ## Open questions - [ ] Visual treatment: separate tab? Collapsed group within the existing list? Filter chip? - [ ] Bulk archival: at what cadence — per-day, per-week? Manual or automatic? - [ ] Counter design: what's the most useful headline number for a teacher who runs daily pages constantly? ## Engineering handoff Not ready. Needs scoping decision and UX walkthrough; depends on AssignmentType data model.
Repo sync
No repo sync metadata recorded yet.