Skip to main content

​
Context

Meridian (the STRATT documentation engine) launched with Starlight’s default dark theme — functional but visually disconnected from so1.io, atlas.devarno.cloud, and flight.devarno.cloud. The wider ecosystem uses the Mars design system: night sky backgrounds (#0A0E17), iron oxide accents (#CD5C5C), atmospheric gradients, and backdrop-blur visor panels.

​
Learning

Extracting the Mars design tokens from atlas/mars.css into Meridian’s Starlight overrides took under an hour of CSS work, but the impact on perceived product quality was immediate. The entire ecosystem now reads as one product family — Meridian looks like it belongs alongside Mission Control and the Atlas documentation hub rather than being a generic Starlight site. The critical insight: design tokens are infrastructure, not decoration. When --mars-iron-oxide appears in 4+ codebases, changing the brand accent requires exactly one variable update per site. The 13.2KB mars.css file has become a shared protocol asset, just like the STRATT schema package is a shared engineering asset.

​
Business Takeaway

For a solo-founder product ecosystem, visual coherence is a trust signal. Investors, early adopters, and potential contributors evaluate polish as a proxy for engineering quality. Applying the same design system across all public-facing surfaces (meridian.devarno.cloud, atlas.devarno.cloud, so1.io) creates an impression of a mature platform rather than a collection of side projects. The cost is low (reuse existing tokens), and the return is high (every surface reinforces the brand).