Skip to content

Draft: Connect each project and publication back to the lab vision #5

Description

@kcarnold

Draft proposal for the summer student backlog — open for the director's review before anyone picks it up. Suggested label: content.

Why

src/pages/vision.md lays out a compelling thesis: AI should help people think better and more deeply, not cede thinking to the machine for the sake of speed. But the Projects and Publications pages read as standalone descriptions — a visitor can't easily see how each piece of work advances that vision.

What to do

For each project (src/pages/projects.astro and the per-project pages) and each publication (publications array in src/pages/publications.astro), add a short framing sentence that ties it to the vision — e.g. how "interaction-required suggestions" or "intentionally-incomplete suggestions (Questions, Rhetorical Moves)" embody thinking better, not faster.

Consider a short intro paragraph at the top of the Projects page that states the throughline before listing the work.

Notes

  • This is mostly writing, grounded in the existing abstracts — good for a student who knows the research.
  • Keep it concise; one or two sentences per item, not a rewrite.

Done when

  • Each project and publication has a clear tie to the vision.
  • Reviewed/approved by the lab director.

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions