Contribute

Add an event, walk a thread, or trace a life. The forms generate a JSON file you can submit three ways.

Before you start

This atlas is an editorial corpus first, code project second. The validators check that your contribution has the right shape; humans check whether it reads well and is correctly sourced. Both are gates.

Two non-negotiables

Verified figures only. Cross-check dates, locations, and key claims against at least two independent sources before marking verified as true. When in doubt, mark it false — the asset surfaces unverified entries with a small tag.
Wikipedia is the rabbit-hole link, not the source. Your summary should read like the start of an editorial, not an extract of the Wikipedia lead.

Editorial voice

Direct, calibrated, slightly opinionated.
Numbers and named entities over adjectives. "32 million rupees, 5–8% of annual revenue" beats "vast wealth".
No mid-sentence bolding, no emoji.
Don't flatten dynasties for narrative convenience. The Sur dynasty (1540–1556) gets its own file even though it lasted five years; same logic applies to other regional and short-lived polities.

Pick what you want to add

Event

A single historical event — a battle, a treaty, a coronation, a published work. Most contributions start here.

Thread

A curated walk through a sequence of existing events — a causal chain, a thematic argument, or a counterfactual. Needs at least 3 events already in the corpus.

Person

A biographical track — a sequence of locations across someone's life. Each step is either an existing event or a standalone moment (a private location not in the events corpus).

Collection

A set of events that share a property — women in independence, founding moments, rebellions. Cheap to author: pick events explicitly or use a tag selector. No per-member prose.

How submission works

Every form ends with three buttons:

Download JSON — saves the file to your computer. You can attach it to an email, a GitHub issue, or hand it to a friend who'll submit it for you. No GitHub account needed.
Open as Pull Request — opens GitHub's web editor with the file pre-populated in the right folder. You click "Propose new file", a pull request opens, and the validators run automatically. Needs a free GitHub account.
Open as Issue — opens a GitHub issue with the JSON in the body. Use this if your contribution needs editorial discussion before it's ready to merge, or if you want to flag a concern alongside it. Needs a free GitHub account.

The form catches schema errors as you type, so by the time you hit submit your JSON should be ready to merge.

Reporting an error in an existing entry

If you've spotted a wrong date, a misspelled name, or a misplaced pin in something that's already in the atlas, you don't need this form. Open a correction issue on GitHub with the entry id and a one-line description.