Layer 08 · Experience Layer
Consistent UI and extensibility across every Conflux surface
Ship consistent UI across web apps with the shared Conflux design system. Extend the platform through a plugin model when applications need custom surfaces.
Why this layer
Built into the platform, not bolted on
Every module in this layer solves the same class of problem the same way — regardless of who implements it.
01
One design system, every surface
Website, docs, console, and your applications share tokens, components, and patterns. Users and developers encounter one visual language.
02
Dark-first, registry-native UI
Components follow Conflux conventions — monospace labels, left-border accents, flat bordered grids. Not generic SaaS marketing chrome.
03
Extensions without forking the platform
Plugin and extension slots let tenants add custom surfaces sandboxed with platform auth — not parallel UI codebases per customer.
Canonical implementation
One path for every author
Junior developers, senior engineers, and AI agents produce the same standard output.
How Conflux does it
UI components follow the same canonical rules
Import from @conflux-stack/ui. Theme tokens come from @conflux-stack/theme. Extensions register through platform config and render in sandboxed slots.
Canonical path
@conflux-stack/ui components used across website, docs, and console
Theme tokens define brand, spacing, and semantic colors once
Extensions register capabilities through platform config
Custom surfaces inherit auth and tenancy from the host app
What you get
Ship product UI that matches Conflux platform surfaces
Reduce design drift between marketing, docs, and application
Extend the console and apps with tenant-scoped plugins
Onboard designers and developers to one component registry
01 · Experience Layer
Design system shared across every surface
Dark-first tokens, registry-native components, and patterns used across website, docs, console, and your applications. One visual language for the whole stack.
UI · One canonical path
SDK
import { Button } from '@conflux-stack/ui'CLI
conflux ui add button
Config
ui: theme: conflux-dark
What's possible with UI
01
Shared design system and component library
02
Dark-first tokens aligned to Conflux brand
03
Used across website, docs, console, and your apps
02 · Experience Layer
Custom surfaces without forking the platform
Plugin and extension slots sandboxed with platform auth. Tenants add custom UI and logic through a registry — not parallel codebases per customer.
Extensions · One canonical path
SDK
await conflux.extensions.register({ id, entry })CLI
conflux extensions publish
Config
extensions: sandbox: strict
What's possible with Extensions
01
Plugin and extension system for custom surfaces
02
Sandboxed extensions with platform auth
03
Extension registry per tenant
Explore
Continue through the platform
Nine layers, one cohesive stack. Browse adjacent layers or return to the full registry.