Flux Atlas • Design system

Worldbuilding in motion.

A design system for a world-building app that tracks places, factions, events, and change over time. It should feel structured, atmospheric, and easy to read without drifting into generic fantasy or loud sci‑fi.

Primary action Secondary action
Cal Sans Display and section headings
Lexend Body copy and interface reading
Topo lines Core motion motif and environmental texture
Flux Atlas primary lockup
Flux Atlas light lockup preview

Primary dark lockup framed on a quiet light plate.

Flux Atlas orb-led application frame

Orb-led support mark for darker product moments and utility contexts.

Visual theme & atmosphere

Logo system and brand expression

The mark should feel engineered but alive. The orbital symbol and letterforms suggest movement, mapping, and tracked change across worlds, timelines, and systems.

Use the full lockup when recognition matters. Use the orb-led mark in tighter spaces or darker, more atmospheric contexts.

Primary lockup
Flux Atlas primary lockup framed on white

This is the clearest expression of the brand. Use it for hero moments, overview sections, marketing headers, and any place where the typography needs to read immediately.

Orb variants

Keep supporting marks consistent across dark and light surfaces. Use the orange orb only when the interface needs a deliberate point of emphasis.

Dark-surface orb
Dark-surface orb

Primary supporting mark for darker product surfaces, navigation, and ambient UI.

Light-surface orb
Light-surface orb

Use the same core mark on light panels and framed contexts where contrast stays controlled.

Signal orb
Signal orb

Accent variant for featured moments, active states, or directional emphasis.

Light-surface lockup
Flux Atlas dark horizontal lockup

Use the darker lockup on restrained light surfaces, framed callouts, or documents where the logo should feel stable and grounded.

Supporting marks
Flux Atlas supporting orb mark on dark surface
Orb mark on dark
Flux Atlas supporting orb mark on light surface
Orb mark on light

Use supporting marks for avatars, sidebars, splash states, and tighter layouts where the full wordmark would feel crowded.

Color palette & roles

Palette and contrast

Deep teals establish the environment, orange signals change or action, and stone offers visual rest. Use orange deliberately so it guides attention rather than overwhelming the interface.

Check colors in actual lockups and interface surfaces, not as isolated swatches. These examples show how contrast and emphasis should behave in context.

Reference palette
Flux Atlas palette reference with lockups and full color swatches

Use the lockups to judge whether the palette feels integrated with the identity before applying it to UI components.

Deep Teal

#1a3637

Primary brand anchor for interfaces, hero zones, and high-confidence surfaces.

Slate Teal

#719196

Secondary brand color for panels, tags, hover states, and softer information layers.

Signal Orange

#ff9248

Reserve for emphasis. It should guide the eye, not dominate the whole composition.

Soft Stone

#adaaa1

Quiet neutral used for light contexts, outlines, and moments that need visual rest.

Typography rules

Hierarchy for long-form worldbuilding

Cal Sans handles decisive moments such as headings and section labels. Lexend supports sustained reading across lore entries, interface text, and documentation.

Keep headings short and bold. Use Lexend for paragraphs, buttons, cards, and longer explanatory text.

Header system
Cal Sans headlines stay broad, stable, and readable.
Display64–88 / 0.96 / Cal Sans
Section44–56 / 0.98 / Cal Sans
Body system
Lexend is for sustained reading across lore entries, cards, UI labels, and longer product explanations. It should stay easy to scan without feeling clinical.
Body17–18 / 1.7 / Lexend
Caption14–15 / 1.5 / Lexend
Component stylings

Atmospheric UI with readable priority

Use dark, lightly frosted surfaces with restrained borders and clear emphasis. Components should feel stable enough for dense information while still suggesting living systems and change.

Favor hierarchy over decoration. Keep buttons purposeful, surfaces quiet, and tags supportive of scanning.

Buttons

Primary buttons carry orange. Secondary actions stay quiet with low-contrast fills and thin outlines.

Create world Secondary action
Button guidance Use orange for directional actions, not every action. The secondary button should feel supportive, not absent.
Surfaces

Surfaces should feel slightly frosted, not glossy. Borders and blur do the work that heavier shadows normally would.

Tags and labels

Use rounded chips for status, categories, and world attributes. They should support scanning without stealing attention.

Volatile Stable Procedural
Active change Passive system