Opus journal
The story behind the system.
Product releases, design decisions, and the work of making a component library feel ready for real applications.
01
The app writes the release notes.
Opus 0.17.1 fixes Data Grid sorting on pills, badges and nested cell content — a defect that only appeared once the published package was consumed by a real application, which is how this project finds its changes.
Read story →02
Opus now speaks 48 languages.
Every component in the library has been translated into 47 languages besides English. The translations are live in the docs and ship with the npm package — and we are looking for native speakers to proof-read them.
Read story →03
Components for the work after the demo.
Opus 0.8 adds eight components for production workflows, and Opus 0.9 gives DataGrid a column manager and saved views. Together they close the gap between a polished prototype and an application people use every day.
Read story →04
Introducing Neumorphism: a softer surface for Opus.
Opus 0.7.4 introduces a Neumorphism theme across the component library, with raised actions, recessed inputs, and a shared material colour in light and dark modes.
Read story →05
The atmosphere is part of the system too.
The colour field behind the Opus home page is now the same fully configurable Background Blobs component available to every application that installs opus-react.
Read story →06
Money controls should speak the local language.
Opus 0.7.2 brings international currency formatting and a dedicated selector that makes the right choice clear before data leaves the form.
Read story →07
Design the system, then take it with you.
Visual Theme Designer, global tokens, responsive previews, and the new Search Box arrive in the Opus 0.7 release.
Read story →08
A component library should feel at home anywhere.
Background atmospheres and universal surface settings gave the catalogue a stronger, more adaptable visual foundation.
Read story →09
Quality is a feature, not a finishing pass.
A library-wide quality baseline made accessibility, public APIs, and release confidence part of the product itself.
Read story →010
The brand travels with the library.
A package-owned Opus brand system removed the fragile dependency on an application's public folder.
Read story →011
The everyday work around the work.
A major expansion of workflow primitives brought the things business applications rely on into the core library.
Read story →012
Media that does not lose its place.
Persistent playback turned video from an isolated component into an experience that can follow a user through an application.
Read story →013
Time deserves a better interface.
Portaled pickers replaced browser-native date and time interfaces with a consistent, application-ready control family.
Read story →014
From internal system to installable tool.
The first public npm release made Opus usable where it matters: in another team's application.
Read story →