Themes And Editors
Themes control how your public status pages look and how your subscriber emails are rendered. Every visual aspect — colors, fonts, logos, layout, translations, and even custom CSS — is managed through themes. Each status page is linked to a theme, and activating a new theme version updates the public appearance immediately.
How themes and versions work
A theme is a named container. Inside it, theme versions hold the actual configuration: design tokens, logos, colors, fonts, border radii, navigation links, translations, template overrides, and custom CSS.
From the theme version overview, the sidebar includes a dedicated Theme Settings section where you can update the theme identity itself: the display name and the theme key. The theme key is the stable identifier used within the organization, so it must remain unique for your organization and follow the expected lowercase key format (letters, numbers, and dashes). This lets teams correct naming conventions or align keys with internal standards without leaving the version editing workflow.
Theme versions follow a strict lifecycle: draft, active, and obsolete. Only the active version is used for public rendering. Only a draft can be edited. This separation means you can safely prepare changes without affecting what customers see until you are ready.
When changes are prepared, the system creates a draft by copying the current active version. The draft can be refined through preview, including color, logo, and translation updates, before being promoted as the next active version. Promotion switches versions in one step, so there is no window where the public status page is between versions.
Each theme can have at most one draft at a time. If you need to start over, discard the draft and create a new one from the current active version.
The number of themes your organization can create is governed by your billing plan. The default theme (created during organization registration) cannot be deleted.
The frontend editor
The frontend editor is a full-screen editing experience with a form panel on the left and a live preview on the right. Changes you make in the form are immediately reflected in the preview, so you can see exactly how your status page will look before activating.
The editor is organized into sections:
Branding covers your company name, website URL, and logos. You can upload separate logos for light mode, dark mode, favicon, and email header. Logo changes take effect when you save and activate the version.
Layout settings control structural choices like border radius (for rounded or sharp corners), Google font selection, whether dark mode is available to visitors, and whether the subscription widget appears on the status page. The subscription toggle requires the Subscribers feature on your plan.
Light mode and dark mode sections let you configure color palettes independently for each mode. This includes background colors, text colors, accent colors, and component status indicator colors. If you disable dark mode, visitors always see the light version.
Page settings allow per-page customization for each status page view: Status overview, Incidents list, Incident detail, Maintenance list, Maintenance detail, and Subscribe page. You can control which elements appear and how they are arranged.
Translations let you override default text strings for buttons, labels, headings, and other UI elements. If your organization has multiple languages configured, you can provide translations for each language. Multi-language editing requires the Multiple Languages feature on your plan.
Custom CSS gives you full control over styling beyond what the design token system offers. This is useful for brand-specific adjustments that do not fit into the standard color and font controls. Custom CSS requires the Custom CSS feature on your plan.
Powered-by removal hides the Incido branding from your status page footer. This requires the Brand Removal feature on your plan.
The email editor
Subscriber notification emails are also themed. The email editor works similarly to the frontend editor — a form panel with a live preview — but is focused on email-specific concerns.
You can switch between notification types (incident created, incident updated, maintenance scheduled, and so on) to see how each email template looks with your current design tokens. The preview supports switching between languages and device widths (desktop and mobile) so you can verify rendering across conditions.
Email design tokens control colors, fonts, and layout for the email body, header, and footer. Email template settings control content structure — what information is included, how it is formatted, and how translations are applied.
Changes to email templates affect all future subscriber notifications. Already-sent emails are not retroactively changed.
Template customization
For advanced use cases, theme versions support custom Liquid templates that override default rendering for specific status page views. Template customization is sandboxed, so some advanced template capabilities are intentionally limited for safety.
If no custom template exists for a particular page, Incido falls back to the bundled default template. This means you can selectively override only the pages that need custom rendering while leaving the rest on defaults.
Previewing before activation
Before a draft is promoted, you can preview it using a time-limited preview URL. Preview links are secure and expire after 24 hours, which supports review without exposing draft changes publicly.
What changes on the public frontend
Activating a theme version updates the public status page immediately. Every visual element controlled by the theme — colors, fonts, logos, layout, translations, custom CSS — changes in a single atomic switch.
Email template changes affect all future subscriber notifications sent from the status pages linked to this theme.
If you upload new logos, the previous logo files are cleaned up from storage automatically in the background.
Operational effects
Theme work affects both public page presentation and subscriber email consistency. If incident and maintenance communication is operationally strong but theme rollout is inconsistent, customers can still experience confusing messages across channels. Keep this workflow aligned with Status pages, Incidents, and Maintenances when preparing visual updates.
Troubleshooting
Changes are not visible on the status page. Verify that you saved your changes and activated the draft version. Editing a draft does not affect the public page until activation. Check that the status page is linked to the theme you edited.
The subscription widget does not appear. Check that subscriptions are enabled in the theme version's layout settings and that your plan includes the Subscribers feature.
Custom CSS is not available. This feature is plan-gated. Verify your plan includes Custom CSS.
Email preview shows unexpected formatting. Switch between device widths in the email editor to check responsive rendering. Verify that your email design tokens are set correctly for both light and dark modes.
A logo change did not take effect. Save the draft and activate it. Logo uploads are stored when you save, but the public page only uses the active version.