Why Contour UI

How shared components became a React package, and the decisions behind its boundaries, interaction behavior, and optional dependencies.

From shared interface code to a package

Contour UI began with shared components and visual rules: paper and ink surfaces, a lime accent, three typefaces, and light and dark themes. The reusable parts now have one implementation and an explicit package version.

Application ownership

A dialog fix belongs in Contour; a weather request belongs in Atmos. Apps keep their data, workflows, layouts, and product-specific scenes. Three.js and Lenis remain optional.

Enable JavaScript for the full article, or read setup guidance.