Public Page Customization

Customization controls both how the page looks and how it behaves for readers.

The main customization areas

The current customization workspace is split into:

• Homepage
• Branding
• Extensibility
• Embeds
• Incidents
• Notifications

Homepage layout

The homepage configuration decides which sections visitors see first.

The main sections are:

• current status and live activity
• component hierarchy
• previous activity

Admins can:

• reorder sections
• hide sections
• choose the default hierarchy mode
• set a default component focus

Basic View vs Tree View

This is one of the most important visitor-facing choices.

Choose Tree View when you want:

• a concise structural tree
• a clear sense of parent-child depth
• a classic service hierarchy feel

Choose Basic View when you want:

• flatter expandable rows
• more progressive disclosure
• a layout that feels easier to browse for less technical audiences

Branding

Branding includes:

• site title
• site subtitle
• header identity mode: Logo + Text, Logo Only, or Text Only
• managed uploads or approved URLs for light and dark logos
• managed favicon upload or approved favicon URL
• light and dark brand colors
• live preview before save

The goal is not only to look polished, but to make the page feel trustworthy and familiar.

Extensibility and locale

The customization workspace also includes a bounded extensibility tab for hosted public routes.

Current settings include:

• custom CSS
• approved external head script URL
• approved external body script URL
• document locale
• date and time locale

The important boundary is that this is controlled extensibility, not arbitrary inline code:

• custom CSS is bounded and sanitized
• external scripts must use public https URLs
• inline JavaScript is intentionally not supported

That gives teams room for brand polish and instrumentation without turning the hosted page into an unrestricted code surface.

Hosted embeds

The Embeds tab publishes two hosted status surfaces:

• an SVG badge for docs sites, changelogs, or support portals
• an iframe widget for dashboards, launchpads, or embedded product surfaces

Admins can:

• enable or disable each surface
• choose the badge label
• copy the generated hosted URLs and snippets

If the page itself is private, hosted embeds still inherit that viewer access policy. In practice, embeds are most useful on public pages.

Incident card presentation

You can also tune how active incidents appear on the homepage, including:

• which message content is primary
• whether to show affected-component summaries
• whether timestamps appear
• whether impact text shows in collapsed cards
• whether to show a View Details link

These choices change how much detail a visitor gets at a glance.

Notifications and readiness

Customization also touches operational behavior, including:

• email delivery settings
• long-running incident notifications
• long-running maintenance notifications

That is why this screen matters so much: it is both brand design and operating policy.

Related operational reporting

After publishing customization changes, page admins can review the effect through the status-page Analytics workspace.

The current analytics workspace focuses on:

• page views and estimated unique visitors
• hosted badge and widget impressions
• subscriber growth and delivery mix
• incident and maintenance activity

Those analytics are available in the app, API, and MCP as read-only summaries. They are operational reporting, not Terraform-managed configuration.

Recommended defaults

• Keep the homepage sections simple and readable.
• Use the hierarchy mode that best matches your audience.
• Make incident cards informative before you make them clever.
• Verify branding in both light and dark preview.
• keep custom CSS and script hooks intentionally small and reviewable
• enable hosted embeds only where the parent page visibility model makes sense
• Document which customization choices are intentional so later changes are easier to review.