Draft proposal for the summer student backlog — open for the director's review before anyone picks it up. Suggested label: content.
Why
Right now the research is communicated mostly through academic abstracts on the Publications page and a single screenshot on the home page. There's no accessible, plain-language explanation of what the tools do or what we learned — the kind of thing a prospective student, collaborator, or family member could read and understand.
What to add (any subset is a useful contribution)
- A short, jargon-free "what this is and what we found" summary for each project, written for a general audience.
- A demo: an annotated screenshot series or a short screen-recording / GIF of the writing tool in action (the home page currently has just one static image).
- Optionally, a simple "news" or "updates" section for milestones (e.g. "published at In2Writing 2025", "now integrated with Google Docs").
Notes
- Demos can live in
public/ and be referenced from the relevant project page.
- Pair this with the vision-connection issue so the plain-language summaries also carry the "think better, not faster" framing.
Done when
- At least one project has a plain-language summary and a demo (image series or clip).
- Reviewed/approved by the lab director.
Draft proposal for the summer student backlog — open for the director's review before anyone picks it up. Suggested label:
content.Why
Right now the research is communicated mostly through academic abstracts on the Publications page and a single screenshot on the home page. There's no accessible, plain-language explanation of what the tools do or what we learned — the kind of thing a prospective student, collaborator, or family member could read and understand.
What to add (any subset is a useful contribution)
Notes
public/and be referenced from the relevant project page.Done when