The knowledge base.

A chapter opens with an answer-first summary because most visitors arrive already holding a specific question, often the same one a search engine surfaced, and should not have to read past several paragraphs of context to find out whether the page addresses it. Below that summary sits the data ledger, a table of the countable facts a chapter makes claims about — dates, casualty ranges, administrative details — kept separate from the prose so a reader can check a number without re-reading an argument to find it. The sourced sections come next and carry the actual argument, each one narrower than the chapter as a whole and each one citing the specific work it draws on, rather than pointing to a single bibliography at the bottom and asking the reader to guess which source supports which sentence.

After the sourced sections comes a short FAQ block addressing questions the chapter's prose does not answer directly — a scale question, a comparison to another empire, a common objection — followed by the source list itself. This order is fixed across every chapter in every language precisely so that a reader who has learned to navigate one chapter already knows how to navigate all of them: the summary for orientation, the ledger for figures, the sections for argument, the FAQ for the loose ends, the sources for verification. A reference work that reorganised itself from page to page would cost readers time on every visit; this one does not.

A chapter is where a claim gets its argument and its citation; it is the only place in the archive where a reader should expect a sourced case to be made. The glossary is not a set of small chapters — it exists so that a term like 'genocide,' 'settler colonialism' or 'extractive economy' has one fixed, careful definition instead of being redefined slightly differently every time a chapter needs it, which would let small inconsistencies accumulate across dozens of pages. An answer page exists for a different reason again: it takes a single question, states the answer plainly in the first sentence, and then supports that answer with the same kind of sourced material a chapter would carry, but scoped to one question rather than to one empire or event.

The practical rule for a writer, a researcher or anyone trying to locate the right page is this: if the material argues something and needs sources, it belongs on a chapter; if it fixes the meaning of a term so every other page can use it consistently, it belongs in the glossary; if it exists to answer one direct question a reader is likely to type into a search box, it belongs on an answer page. Material that tries to do more than one of these jobs at once is usually a sign that it has been placed on the wrong kind of page, and the archive's structure exists in part to prevent that drift.

A teacher building a lesson typically starts at an event chapter for the sourced narrative, pulls the ledger for the figures worth putting on a slide, and checks the glossary for any term students are likely to contest, before assigning the chapter's own sources as further reading. A journalist working against a deadline goes straight to the ledger and the sourced section that covers the specific claim in question, because that is where the citation sits, and treats the chapter's opening summary as a starting point rather than a quotable conclusion. A student writing coursework should cite the specific chapter and section used, by title and archive name, exactly as they would cite any other secondary source, and should then go on to read the monograph or primary source the chapter itself cites — the chapter is a map to that literature, not a replacement for reading it.

That last point states the archive's own limit plainly: it is a starting point for locating and organising a question, not a substitute for the peer-reviewed monographs, archival records and academic journals its chapters cite. A chapter can tell a reader that a death-toll estimate exists and where it comes from; it cannot carry the full argument, caveats and counter-evidence that the cited academic work develops over hundreds of pages. Treating this reference as the last stop in a research process, rather than the first, is the one use of it the archive explicitly does not recommend.

Where should I start if I only have one specific question?

Try an answer page first if the question is phrased simply and directly — that is exactly what those pages are built for. If no answer page covers it, go to the event or empire chapter most likely to contain it and use its data ledger and section headings to find the relevant part quickly.

How do I cite a chapter in academic or school work?

Cite it as you would any other reference work: the chapter title, the archive name, and the URL, alongside the retrieval date if your citation style requires one. Because chapters are living documents that get corrected, a retrieval date lets a reader know which version you consulted.

Is it acceptable to cite a chapter instead of the academic sources it lists?

For a quick fact check or general orientation, yes; for substantive academic or school work, the chapter should be treated as a route to the underlying monographs and journal articles it cites, and those should be the works actually referenced in the final citation list wherever possible.

Why isn't everything just kept on one long page per empire?

Because a single long page forces every reader — someone checking one date and someone reading for background — through the same undivided text. Splitting empire chapters, event chapters, thematic pages, the glossary and answer pages lets each reader open the layer built for their actual question instead of scrolling through material meant for someone else's.

What should I do if a chapter doesn't cover the specific angle I need?

Check whether a thematic page covers it instead, since thematic pages exist precisely for questions that cut across more than one empire or event chapter; if neither covers it, the chapter's own cited sources are the next place to look, since they will typically go into more depth than any single reference page can.