Yes. Add columns for feast_day_west, feast_day_east_julian, and feast_day_east_gregorian. Conditional selector mappings render whichever apply for the saint, and the daily calendar pages aggregate from whichever column matches the calendar the visitor is using. One template carries the whole tradition cleanly.

Use a tradition column with values like Catholic, Orthodox, or Coptic. The base page renders fields appropriate to the tradition, and cross-tradition saints like Saint Nicholas show parallel feast dates and parallel patronage lists. The sheet handles the doctrinal nuance through conditional column logic.

Add a calendar_rank column and update it for the canonized saint. The page picks up the new rank on the next cache refresh, and the daily calendar pages reflect the change immediately. No template work needed when Rome formally recognizes a new memorial or solemnity.

Yes. Add a historicity column with values like documented, legendary, or removed-from-calendar. Conditional notices render only on pages where the column is non-empty so readers see appropriate context, and removed-from-calendar saints stay accessible for historical research without misleading the casual reader.

An icon_url column per row points at a hero image in the media library or a CDN, typically a public-domain icon or painting. The meta mapping for og:image picks up the same URL so the share card and the page hero stay aligned. Caption and source credit live in their own columns.

Schema.org has no dedicated Saint type, so the page uses Person with extra JSON-LD additions for feast_day, patronage, and canonization. Search engines treat the page as a rich Person entry, and the custom JSON-LD gives downstream pipelines clean access to the liturgical metadata.

The page is static, but a structured submission form can feed a moderated testimonials column. Approved testimonies render under the saint's intercession block via a list mapping. Editorial control stays with the sheet owner, and the parish or media team reviews submissions before they appear.

Because every page is built from a unique row, visible content varies by saint. Generic intros come from saint-specific fields, not a shared paragraph. Schedule a quarterly review of any columns that risk repetition (generic patronage intros, boilerplate biography sentences) and tighten them at the data layer.