Every Group Project Has a Historian (Whether You Hired One or Not)

Every friend-built website has one. They never applied for the job, nobody voted, and it's definitely not on the GitHub README. But somewhere in your crew is the person who remembers that the site's name came from a misheard lyric in a Denny's parking lot outside Columbus, that the comment section was disabled because of the Great Bot Rampage of 2022, and that the admin account is named after a dead hamster.

They're the lore keeper. And if your project loses them, you lose the plot.

The Changelog Nobody Asked For

Lore keepers do a few unglamorous things that keep a group project from dissolving into vibes. They maintain the changelog. They write the postmortems after things break. They keep a running glossary of inside jokes that exactly six people understand — until, one day, you want a seventh person to understand them.

That last part matters more than it sounds. When Priya from your Discord finally agrees to help with the newsletter, she doesn't need a tutorial on React. She needs to know why everyone calls the staging server "Gary." Without that context, every new contributor spends their first month asking questions in the group chat and getting answers like "lol, long story."

Long stories are institutional memory. And institutional memory is the single most underrated feature of any collaborative site.

What Actually Happens When the Lore Keeper Leaves

We've all watched it go down. A project hums along for three years, then the person who knew everything moves to Denver, starts a Masters program, and quietly stops showing up to calls. Six months later, someone asks why the DNS is pointed at a registrar nobody recognizes. Nobody knows. The domain lapses. The site becomes a very expensive lesson.

The technical stuff usually survives a transition — it's documented in the repo, in deploy logs, in code comments. What doesn't survive is the why. Why the site launched on April 1st. Why you deliberately didn't build the mobile app. Why the about page has a typo that everyone has agreed, over years, is now load-bearing.

The Lore Page: A Template You Can Steal

Here's the fix, and it takes one afternoon: add a private (or public, if you're brave) page to your site called Lore, Field Notes, or The Vault. Structure it like this:

1. Origin Story. Two or three paragraphs, written like you're telling a friend. When did this start, what was the joke, who said the thing. Future you will not remember. Write it down anyway.

2. The Glossary. Every inside term, nickname, and acronym, with a one-line definition. "Gary — the staging server, named after the guy who hosted it before us and ghosted. Not a person anymore. Hopefully."

3. Decisions We Made On Purpose. A short list of things that look like mistakes but aren't. "The homepage loads no JavaScript. This is a values statement, not an oversight." This section alone will save you from re-litigating the same argument every eighteen months.

4. Things We Argued About. The resolved debates. Keep it light — this is where the lore keeper's diplomacy skills shine. Record the outcome and the reasoning, not the grudges.

5. The Map. Who owns what. Domains, hosting, the social accounts, the weird email address that receives the Stripe receipts. Names, not just titles.

That's it. No fancy tooling required — a Notion page, a markdown file in the repo, or an actual page on your site all work fine. The format matters less than the habit.

Rotate the Role, Keep the Record

One caution: don't let the lore become a single point of failure any more than you'd let the passwords be. The best setup we've seen is a rotation — the lore page gets a new steward every six months, and handoff is a thirty-minute call where the outgoing keeper walks the incoming one through anything that didn't make it to the page yet.

It's a little like a family passing down a recipe. The dish survives because more than one person knows how it's made.

And honestly? The lore page tends to become everyone's favorite thing on the site. New contributors read it like a novel. Old friends reread it like a yearbook. It's the difference between a project and a shared history — and shared history is the entire reason friends build websites together in the first place.

So this week, check whether your project has a lore keeper. Thank them. Then ask them to write down the taco incident before they forget, because you already have, and someone's going to ask.