The big picture
Step by step
The lecture happens Lecture
A different guest speaker each week. Nothing is recorded or shared, but it's all assessable.
Everyone dumps their notes Google Docs
Classmates paste whatever they wrote into one shared Google Doc, linked from the site. Rough notes are fine. The more people contribute, the fewer gaps there are.
Claude merges them Claude
I give that week's notes to Claude. It combines overlapping notes, fills gaps from other people's versions and writes one structured page: speaker and topic, contributors, numbered sections, a one-page summary and key takeaways.
The week is added to the site Laptop
The new week goes into the site's single HTML file with a speaker photo, a card on the home page and an entry in the search index.
Publish GitHub Pages
Pushing to GitHub updates the live site within a minute.
Read, search, print Browser
Each week has its own view with a table of contents. Search works across every week as you type, and each one-page summary prints cleanly for revision.
The pieces
Google Docs
The input: one doc anyone in the class can paste into.
Everyone already knows how to use it. No sign-up, no friction.
Claude
Merges many partial notes into one complete, consistent write-up.
Turns 20 fragments into one set of notes in minutes, not hours.
A single HTML file
Every week, photo and script lives in one file. JavaScript switches between weeks without reloading.
Nothing to build, nothing to break, trivial to host.
Home-made search
A few dozen lines of JavaScript index every section on load and show highlighted matches as you type. Press / to jump to it.
Instant search with no search service or library.
GitHub Pages
Free hosting, updated with every push.
Zero cost for a class resource.
Trade-offs I chose
- The merge step is manual (me plus Claude) rather than automated, so I can check each week's write-up for errors before it goes live.
- One file is simple but grows every week. It's fine for a semester and wouldn't scale to a whole degree.