Yes. Add a parent_slug column for protocols and annexes. The main treaty page renders from its own row, and protocols link back via a list mapping that filters the sheet by parent_slug. The Kyoto Protocol can sit as a child of the UNFCCC while still having its own page with its own signatories and clauses.

Use a treaty_type column with values like bilateral, plurilateral, or multilateral. Conditional sections render whichever fields apply: simple party list for bilaterals, full ratification table with reservations for multilaterals. One template serves both a US-UK extradition treaty and the UN Charter cleanly.

Update the parties array to add a withdrawal date for that state. Conditional rendering shows withdrawn states under a separate Withdrawn label, and the in_force count adjusts on the next cache refresh. The historical record stays intact while the live page reflects current standing accurately.

Yes. Era-specific blocks render conditionally. A modern UN treaty page shows depositary, registration number, and entry-into-force conditions. A historical treaty page like the Congress of Vienna shows territorial maps and dynastic clauses instead. One template adapts via the data to serve both.

A text_url column points at the official PDF in the UN Treaty Series, the national depositary, or a public archive. The page renders a prominent Full text link, and parsing tools can fetch the PDF for clause-level search. Translations into other languages live as additional URL columns alongside the original.

Schema.org has no dedicated Treaty type, so the page uses LegislativeAct or Article with extra JSON-LD additions for parties, ratifications, and key clauses. Search engines treat the page as a rich legal document, and the custom JSON-LD gives downstream pipelines clean access to the structured agreement data.

The page is static, but a structured submission form can feed a moderated commentary column. Approved analyses land under a Scholarly commentary heading via a list mapping with author attribution. Editorial control stays with the sheet owner, and the editorial team vets submissions before they reach the live page.

Because every page is built from a unique row, visible content varies by treaty. Topic context comes from treaty-specific clauses, not a shared block. Schedule a quarterly review of any columns that risk repetition (generic preamble summaries, boilerplate ratification descriptions) and tighten them at the data layer of the sheet.