Hoopy by Michael Rork Get Pockets by HoopyGet Pockets

Case study · Holocene Calendar

Twelve thousand years of human history, where scroll distance is time.

The Holocene calendar adds ten thousand years to the count, so all of human civilization sits on one continuous scale. I built a timeline of it that refuses to cheat: a century is always the same length on screen, whether it was a busy one or not.

Role
Design and build, solo
Built with
HTML, CSS and vanilla JavaScript
Status
Live
See it
holocenecalendar.byhoopy.com ↗

The problem

Every timeline I could find squeezed the quiet millennia down so the interesting ones would fit on the page. That’s the one thing that makes deep time impossible to feel. Five thousand years of early farming and the last five hundred years look about the same size, when one is ten times the other.

Why I built it

I heard about the Holocene calendar on a podcast on New Year’s Eve and wanted to see what it actually looked like. Nobody had drawn it honestly, so I did. It started as a rough sketch; what I kept from it was the proportional scroll, because that was the whole idea, and I built everything else around it.

The opening: Holocene Era and the common era side by side in the header.
Around 11,550 HE, where events crowd together and overlapping eras spread into lanes.

How I built it

  • Proportional by default. The page is built at 5 pixels per year, so a century is always 500 pixels. The scale is adjustable from half a pixel to 20 pixels a year, and changing it keeps you at the same moment in time instead of throwing you somewhere else.
  • Events as data. The 162 core events, across twelve categories, live in JSON datasets that load and merge at startup, so adding a set of events is adding a file. Points, ranges and whole ages are three different kinds of event, and each draws differently.
  • Overlap that stays readable. When empires and eras overlap, their range bars spread into side-by-side lanes, up to fifteen of them, instead of drawing on top of each other. On a phone there are fewer lanes, so cards aren’t pushed off the screen.
  • Two calendars at once. The header shows the year in both the Holocene Era and the common era as you scroll. Type a year in either and it jumps there.
  • Fast on a long page. A dozen thousand years is a very tall document. Scroll and hover work run through requestAnimationFrame and expensive style lookups are read once and cached, so it stays smooth.
  • No framework. About three thousand lines of plain JavaScript. It didn’t need one.
Around 7,000 HE. At true scale most of the early Holocene is quiet, and that’s the point.

Stack

  • HTML
  • CSS
  • JavaScript, no framework
  • JSON datasets

Have something that needs building, or a role I'd fit?

michael@byhoopy.com

Burlington, Vermont · LinkedIn