Writing history posts
This page is for advocates who like stories. Exponential has an unusually complete, public history: every change since December 2023 is told month by month in the chronicle and recorded in the ledger, and the repository history goes back to 2002. History posts show that the project is alive and explain why features exist.
Contents
The sources
| Source | What it gives you |
|---|---|
| The history | "The story of every change ... since the se7enxweb era began in December 2023", month by month |
| The ledger | The complete record of commits per repository |
| The ecosystem | Changes across the related repositories |
| Who is 7x?, Nearly thirty years | The long timeline |
| Who is 7x?, The eZ Publish years | The years before 2021 |
| Timeline | Key dates with sources |
git log in a clone | Every commit since 2002 |
Each month page opens with In short and ends with related pages; every change carries its commit hash, which
readers can open with git show <hash> (The history, In short).
Post ideas
| Idea | Start from |
|---|---|
| "This month two years ago" | The month page of two years ago |
| "How SQLite came to Exponential" | January 2024 |
| "The month the product got its name" | August 2025 |
| "From PHP 7 to PHP 8.5" | April 2025, December 2025 |
| "The story of Velocity" | Velocity chronicle |
| "A year of releases" | Who is 7x?, The 6.0.x releases |
| "The first outside contribution" | December 2023 |
How to write one
- Read the month page fully, then the commits you will mention (
git show <hash>). - Pick three changes that a reader can still use today.
- For each: what changed, why it mattered, what you can do now. Link the feature page.
- Add one sentence of context: what else happened in the project then.
- End with a link to the month page so readers can read the rest.
The template
# This month in Exponential history: <Month Year>
<One sentence: what the month brought, from the "In short" of the month page.>
## <Change 1>
<What changed and why it mattered.> You can still use it: <feature page>. Commit: `<hash>`.
## <Change 2>
...
## Read more
The full month: <link to the month page>. Every change of that time is in the ledger: <link>.
<Disclosure line.>Rules for history
- Use the chronicle's facts, not your memory of the time.
- The old name in the past tense only: "while the software was still called eZ Publish" (Writing about the history correctly).
- Credit people only as the sources do. Contributors named in the history and on Who is 7x? may be named as there; do not add private details.
- No speculation about why someone did something, unless a source says it.
- Respect earlier companies. eZ Systems' work is part of the code; speak of it with respect (Respecting other projects and companies).
Related pages
- Talking points: longevity and history
- Writing about a release
- The history of Exponential
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.