The eclipse row holds UTC contact times. Each viewing region row carries a time zone identifier like America/Los_Angeles. At render time SleekRank converts UTC into the region's local time, including daylight saving rules, so visitors see times in the clock they actually live by.

Yes. Add a map image field on the row pointing at a region-specific overlay, or render an SVG from the row's visibility polygon. The same Twig template handles both. Sites with their own cartography stack drop in an iframe pointing at their map service.

Up to you. Most sites keep historical pages live as a searchable archive, since visitors look up past eclipses by date for research. A status field can flip past events into an archive layout that hides the countdown and shows totals like duration of totality and observed reports.

Add a row to the regions list with name, slug, time zone, and reference coordinates. The new region instantly spawns pages for every eclipse the catalog covers, with localized times. No template changes.

Yes. The related entries helper sorts the eclipses dataset by date and filters by region, so the page for the March 2026 eclipse in US Pacific links back to the September 2025 eclipse and forward to the next one automatically.

Yes. The derived visibility field uses the moon's altitude at peak from the region's reference coordinates. If the moon is below the horizon at maximum, the verdict reads "not visible from this region" and the contact times block is collapsed.

Yes. Add an editorial HTML field to the row. The template renders it conditionally, so eclipses with editorial coverage get a richer page and the rest fall back to the data-only layout. The editorial content lives with the row it describes.

Yes. The page title, meta description, Open Graph image, and Event schema all read from the eclipse row and the region row. SleekPixel can render an OG image with the eclipse date and region burned in so social shares look distinct per URL.