More than pages.
A publishing system.
Turn structured content into useful pages. Know why they’re ready to publish—and what needs attention when the source changes.
One record. A page with a reason to exist.
Follow the content, not a checklist of disconnected tools.
Give your content a shape.
Content Types define the fields. Records hold the details. Try changing this city.
- Content Type
- City guides
- Local detail
- Compare neighborhoods by transport, walking routes, and accessibility.
- Record status
- Draft example
Browser-only illustration. No data is saved or published.
Typed fields
Bound templates
Evidence-backed pages
PostgreSQL ownership
A page shouldn’t go live just because a template can generate it.
CMSHub checks the rendered page before publishing. Missing provenance, weak metadata, or insufficient substance become reasons to enrich—not problems to discover later.
- Trace the facts
- Name the source behind each bound field.
- Test the substance
- Check whether the page still offers value without its variables.
- Explain the difference
- Document what makes this page useful in its own right.
Your source changes.
Your pages should keep up.
Keep records, templates, and pages connected. Inspect the impact of a change, find stale output, and rebuild what needs attention.
- Source recordA detail changesThe content is updated at its source.
- Dependency viewSee what’s affectedFollow the record → template → page relationship.
- Page inventoryRefresh with contextIdentify stale pages and review rebuilds.
Own the content.
And where it lives.
Self-host CMSHub with PostgreSQL. Model content, manage records, and deliver through controlled APIs without handing over your database.
Read the security overview ↗CMSHub Content operations
PostgreSQL Your data store
Content API Controlled delivery