Record → template → page graph
Every generated page traces back to the exact record and template that produced it, kept live as your content model evolves.
ProductDEPENDENCIES & STALENESS
Your source changes. Your pages should keep up.
Programmatic pages create a problem most CMSs never solve: once a page is generated, what keeps it honest when the data behind it changes? CMSHub keeps a live graph of every record → template → page relationship, so a change never lands as a surprise.
01 / BEFORE YOU CHANGE ANYTHING
See the blast radius first
Before you edit a schema field or a source record, simulate the change and see exactly which pages it would affect — how many, which ones, and what would break.
Simulate before you commit
Preview the impact of a schema or record change across every dependent page, before a single page actually changes.
Schema-change validation
Collection updates run through a dry-run validator that reports what would break, not just whether the migration is syntactically valid.
02 / AFTER THE FIRST PUBLISH
Staleness detection & transactional rebuilds
Source data drifts. CMSHub tracks per-page age and last-change timestamps, flags pages as stale the moment their source has moved on, and rebuilds them transactionally so a failed rebuild never leaves a page half-updated.
Per-page staleness tracking
Know exactly which pages are behind their source data, and by how long — not just that "some pages might be out of date."
Rebuild in bulk or by plan
Rebuild every stale page in a collection in one pass, or generate a rebuild plan to review before it runs.
Immutable versions, instant rollback
Every rebuild produces a new immutable page version — roll back to the prior version in one action if something looks wrong.
SEE THE DEPENDENCY VIEW
Change a record. Watch the impact.
Walk through the source-record-changes-dependents demo on the homepage.