How this documentation is compiled, sourced, and corrected

🗂️ Where the data comes from

Every record on this site — each hospital, school, university, and religious-site incident, and each historical massacre entry — is entered by hand into a Google Sheets workbook, one row per incident or event. Nothing here is scraped or generated automatically from a news feed. A row is added when a specific attack, casualty count, or historical detail can be tied to at least one cited source.

Those sheets sync to CSV files in this project's public repository, and a build script turns each row into a page — the same source data a reader sees on the record page is the same data that page was generated from, with no editorial step in between that isn't visible in the underlying file. The full dataset is published in the open, not held back:

🔗 Sourcing standard

Each incident carries one or two source fields. Where the source is a link, it's shown on the record page as a clickable citation you can follow directly. Where a contributor noted a source that isn't a URL — a named outlet or a report without a working link — that note is now shown as attributed text on the incident rather than dropped, so a reader can see a source was recorded even when it isn't clickable.

Incident rows also carry added_by and reviewed_by fields, shown in the page sidebar when populated, so a record's provenance inside the project — who logged it, who checked it — is visible alongside the external source.

🌍 Translation

German and Arabic versions of each record are produced by machine translation, run automatically over the English source text. They are not currently reviewed by a human fluent in the target language before publishing. This is a deliberate tradeoff for a small open project covering three languages, and it's disclosed here rather than presented as editorial translation work.

If you read German or Arabic and notice a mistranslation that changes the meaning of a figure or a claim, please report it using the contact details below — corrections to translated text are handled the same way as corrections to the underlying data.

✅ Corrections

If a figure, date, or attribution on this site is wrong, or a source link is broken, email contact@palgenopedia.org with the page URL and what should change. Corrections are made at the source — in the underlying spreadsheet row — so the fix is permanent rather than a one-off edit to a single page, and it carries through to every language version of that record automatically.