Yes. Use date_estimated and outcome_notes columns. Conditional selector mappings render an Estimated date note or a Contested outcome banner only on pages where those columns are non-empty. The infobox shows the best available figures, and the notes section captures the historiographical disagreement transparently.

Use an engagement_type column with values like battle, siege, blockade, or naval engagement. Conditional sections render whichever fields apply: walls and defenders for sieges, ships and admirals for naval engagements. One template serves the whole catalog without forcing every event into a land-battle mold.

Update the casualties column in the source row. The next cache refresh propagates the new figure into the infobox, narrative, and JSON-LD. If multiple estimates exist, store them as a JSON array with provenance and render them as a labeled list under a Casualty estimates heading on the page.

Yes. Era-specific blocks render conditionally based on the war or date column. An ancient battle page shows phalanx and legion units, a modern battle page shows divisions and armored brigades. The template adapts via the data, so one layout serves Salamis and Stalingrad without compromise.

An image_url column per row points at a hero map or painting in the media library or a CDN, typically from a public-domain atlas or a licensed historical archive. The meta mapping for og:image picks up the same URL so the share card and the page hero match. Caption and credit live in their own columns.

Schema.org has no dedicated Battle type, so the page uses Event with extra JSON-LD for belligerents, commanders, and outcome. Search engines treat the page as a rich historical Event, and the custom JSON-LD gives downstream pipelines and APIs clean access to the structured engagement data.

The page is static, but a structured submission form can feed a moderated corrections column. Approved corrections land in the relevant column with a citation. Editorial control stays with the sheet owner, and the editorial team reviews submissions against primary sources before they reach the live page.

Because every page is built from a unique row, visible content varies by battle. Generic war-context paragraphs come from battle-specific fields, not a shared block. Schedule a quarterly review of any columns that risk repetition (campaign summaries, generic outcome sentences) and tighten them at the data layer.