An era is a named period in a product’s history defined by the team’s dominant strategy, product identity, and turning point. It converts a flat commit log into a narrative about changing bets. section 6.3
Build eras from three compressed signals:
- Directory activity: active date ranges and peak months reveal where attention concentrated. section 6.3
- Directory lifecycles: appearing, disappearing, or going quiet exposes structural transitions. section 6.3
- Large additions and deletions identify concrete commits that opened or closed an era. section 6.3
A product-history timeline
A Ghost history can be read as four eras: “The WordPress Killer,” “The Platform That Wasn’t,” “The Membership Pivot,” and “The Creator Platform.” Each names a strategic bet rather than a directory change. section 6.3
Name each era after the bet the team was making, then explain the turning point that ended it and became the next era’s origin story. section 6.3
