Summary
Old-school writing portfolio — drafts and iterations over time
3Questions
0Links
0Comments
0PRs
Open questions
- 1 What's the right granularity — per-document, per-submission, per-draft? Likely per-submission with drill-down to drafts.
- 2 AI-generated narrative ("your writing has improved on argument structure") vs. raw history? Probably both; let the teacher pick.
- 3 Who can see it — student, teacher, parents? Different defaults probably.
Spec body
# Student growth portfolio
A portfolio view that shows a student's writing evolution over time — drafts, iterations, revisions across submissions — analogous to old-school writing portfolios that demonstrate growth.
## Problem
Today a student's submission history is flat: a list of "what got submitted." It doesn't tell a story about how the student's writing has grown. Teachers used to keep physical portfolios for exactly this reason — they show a process, not just outputs.
Yawp has all the underlying material (every keystroke is in revision history, every submission is preserved, the GA-graded categories track over time) but doesn't surface the through-line.
## Goals (rough)
- A view per student that shows their writing trajectory — submissions over time, with the visible drafts/revisions feeding each one.
- Surface signals like "your thesis statements have gotten more specific over the semester" — an evolution narrative, not just a list.
- Useful for parent-teacher conferences, end-of-term review, and (potentially) college essay portfolios.
## Non-goals
- Replacing the gradebook. This is a separate, narrative-focused surface.
- Public-facing portfolio (like a student-shared link). Internal teacher/student/parent view first.
## Dependencies
- [features/revision-flow.md](revision-flow.md) — draft chains need to be first-class for "iterations" to be visible.
- [features/student-submission-history.md](student-submission-history.md) — basic submission-history surfacing has to work before a richer portfolio view makes sense.
## Connections
Could connect to the broader video-summary idea Kevin mentioned previously. An end-of-semester "here's how your writing grew" video would be in the same space.
## Open questions
- [ ] What's the right granularity — per-document, per-submission, per-draft? Likely per-submission with drill-down to drafts.
- [ ] AI-generated narrative ("your writing has improved on argument structure") vs. raw history? Probably both; let the teacher pick.
- [ ] Who can see it — student, teacher, parents? Different defaults probably.
## Engineering handoff
Not ready. Idea-stage. Depends on revision-flow and student-submission-history shipping first.Repo sync
No repo sync metadata recorded yet.