Visual editor

The visual editor is the default path for creating a Horizon. It is available on every tier that supports Horizons (Keeper and Guardian). You build the Horizon by adding blocks: text, image, table, code, gallery, embed. There is no markup to write and no file to upload; the Horizon is built in the portal.

​

Opening the editor

Two routes:

1. New Horizon. From Horizons → New Horizon, choose Visual editor. The editor opens on a blank canvas with the Horizon’s name and description prefilled.
2. Existing Horizon. From any active Horizon’s page, click Edit. The editor opens on the current state.

​

Block types

The editor offers eight block types. Each block is added from the + Add block menu and edited inline.

• Heading. H2 by default; H3 and H4 available. Use for the major divisions of the Horizon.
• Text. Paragraphs with the brand’s voice rules in play. Supports bold, italic, links, and lists. Long text is split into multiple blocks for readability.
• Image. A single image with optional caption and alt text. Drag-and-drop from disk or paste from clipboard.
• Gallery. A grid of images, useful for sub-brand mark variants, regional photography sets, or campaign visuals. Layout is single-row, two-column, or three-column.
• Table. Structured data: colour values, type weights, dimensions, partner names. Headers are required.
• Code. Monospaced block for code, configuration, or technical specifications. Language tag is optional.
• File. A downloadable file: a PDF deliverable, a Figma file, a Sketch file, a font file. Carries a name and a description.
• Embed. An external embed (a Figma frame, a YouTube video, a Loom recording). Supported sources are listed below.

​

Supported embed sources

The editor accepts embeds from:

• Figma (frames and prototypes)
• YouTube and Vimeo (video)
• Loom (recordings)
• Twitter / X (posts)
• Codepen (code examples)
• Spotify (audio)

Other URLs become plain links rather than embeds. Embeds are scoped to the audience of the Horizon; a Horizon visible to “All team members” embeds publicly-reachable resources.

​

Editing rules

The editor follows the brand’s rules where possible:

• Voice. When voice rules are configured for the atlas, the editor flags banned vocabulary as a hint while you type. It does not block writing; it surfaces.
• Colour. Hex inputs in the editor offer the brand’s palette as a picker. Off-palette colours are accepted but flagged.
• Type. Headings and body render in the brand’s typography stack so what you see is what the team will read.

The flagging is hint-only. It is the brand owner’s call.

​

Saving and publishing

The Horizon saves automatically as you edit. A Draft badge sits at the top of the editor until you publish. Publishing makes the Horizon visible to its audience and counts it against the tier limit. Three states are visible at the top of the editor:

• Draft. Visible only to the brand owner and assigned Editors.
• Published. Visible to the set audience.
• Archived. Hidden from the main sidebar; reachable through Horizons → Archive.

A published Horizon can be returned to draft for major edits. The team sees the previous published version until the next publish.

​

Audience

Before publishing, set the audience:

• All team members. Every team member with access to the atlas can read.
• Specific roles. Limit to one role (Editors only, for an internal-only Horizon).
• Specific people. Name the team members who can read.
• Public, via Guest Pass. Reach external audiences via Guest Passes.

Audience can be changed after publishing.

​

Versioning

Every save produces a version. The version history is visible from the editor’s History tab. You can compare any two versions and roll back to a past version. The brand record records each version with attribution.

​

Limitations

Three things the visual editor does not do:

1. Custom CSS or layout. The editor uses the brand’s design system. Custom styling is not supported; if you need it, author in MDX and upload (see MDX upload).
2. Complex multi-page Horizons. A Horizon is a single page. Long Horizons should be split into multiple Horizons or moved into a Horizon group (Guardian).
3. Programmatic content. Tables computed from data sources, charts, dynamic embeds. Use the embed block for an external source where the dynamism is hosted elsewhere.

​

Related pages