Yes. Add a legal_notes or restrictions column to the sheet and render it into a notice block via a selector mapping. The notice appears on every page where the column is non-empty, so legal disclaimers stay consistent across the corpus without manual review of each page.

Add a parent_slug column. The base species page renders from its own row, and morph rows link back via a list mapping that filters the sheet by parent_slug. That way one fire salamander page sits at the top of a small cluster of subspecies pages, all maintained from the same sheet.

Change the scientific_name column for that row. The next cache refresh propagates the new name into the page title, H1, and JSON-LD. If you also need to change the slug, add a redirect from the old slug in your redirects layer; the new URL inherits the same data.

Yes. Use a setup_type column with values like terrestrial, semi-aquatic, or fully aquatic. A conditional mapping shows or hides the water section, substrate notes, or filtration spec depending on the value. One template serves the whole spectrum.

An image_url column per row pointing at a hero photo in your media library or a CDN. The meta mapping for og:image picks up the same URL so the share card and the on-page hero stay aligned. Captions and credits can sit in their own column and render via selectors.

Schema.org doesn't have a dedicated Animal type, so the page uses Article with biological fields rendered into the body. You can also add a custom JSON-LD block per page mapping scientific name, conservation status, and habitat into properties of your choice for richer machine-readable data.

The page itself is static, but you can wire a comments widget or a structured submission form to a moderation queue. Approved notes land back in the sheet as a community_notes JSON array column, which then renders on the page via a list mapping. Editorial control stays with the sheet owner.

Because every page is built from a unique row, the visible content varies by species. Boilerplate care intros come from species-specific fields, not a shared paragraph. Schedule a quarterly review of any columns that risk repetition (intro paragraphs, generic warnings) and tighten them at the data layer.