Skip to content
JiraVision

Landing-page content management

How a super-admin edits marketing copy, and how overrides are audited.

Landing-page content management

Who can use it

Super-admin only: a stored role of superadmin, or an email present in ADMIN_EMAILS. Everyone else gets 403 from /api/admin/cms and never sees the editor in navigation.

Where

/admin/cms lists the editable landing pages and the sections within them. Pick a section, edit the copy, save. The marketing page renders the override on the next request.

How an override works

  1. The page reads its default copy from the content module in content/ (home.ts, pricing-page.ts, products.ts, solutions.ts, about.ts and the rest).
  2. lib/cms-registry.ts declares which parts of those modules are editable — the section keys and the shape of each.
  3. A saved override is a row in cms_content_overrides keyed by page and section.
  4. Rendering merges the override over the default, so an untouched section always shows the code default and a removed override restores it.

Audit

Every write lands in cms_audit_log with the actor, the section, the previous value and the new one. GET /api/admin/cms/audit returns it and /admin/cms shows it, so public copy can never change without a record of who changed it.

Working safely

  • Edit one section at a time and look at the live page afterwards.
  • Removing an override is the undo: it restores the default from code rather than leaving stale copy.
  • Overrides survive deployments because they live in the database, not in the build.
  • Keep claims true. The registry exposes marketing copy, and the placeholders document lists the claims that still need an owner decision before launch.

Relationship to the rest of the docs

This is the only part of the product where a non-developer can change what the public sees. Everything else in these docs describes the signed-in workspace.