DigiLawyer Design System

A token-driven design system built for DigiLawyer.

8 Color Scales  ·  160+ Design Tokens  ·  25 Components

Jump to the most used parts of the system.

Components

All 25 components in the DigiLawyer Design System — fully documented.

Inputs
Data Display
Feedback
Navigation

Latest Changes

Recent updates to the DigiLawyer Design System.

v2.55.0
MINOR
Next.js docs site, blocks showroom and GitHub Packages publishing
21 September 2026
Records three additions that shipped between v2.54.2 and now without a version entry. site-next: a Next.js static-export docs site (Quickstart, component variant gallery, blocks showroom, changelog generated from CHANGELOG.md at build time), deployed to GitHub Pages at /site-next/ alongside the HTML docs and Storybook; its build runs a CSS-collision check that fails if any site-chrome class shares a name with docs/shared/components.css, so the docs chrome can never restyle a live component preview. blocks/: a copy-paste page-sections registry (navigation-1, navigation-2) rendered live at Mobile/Tablet/Desktop in site-next. GitHub Packages: the React library publishes as @adeshsingh0604/digilawyer-ds via publish.yml whenever react/ changes on main. Also retired the uncommitted Vite site/ prototype (superseded by site-next) and reconciled README, STATUS, TODO and CLAUDE.md with the real repo state. The React package is unchanged and stays at 2.54.2; this is a docs-and-infrastructure release.
v2.54.2
PATCH
Fix Storybook controls across the remaining eighteen components
21 August 2026
Completed the 25-component Storybook audit. Declared controls for every PropTypes.node prop that lacked one, following the convention Button and Input already used: text-carrying props (children, label, caption) get control:'text'; element-valued props (icon, leading, trailing, badge, action) get control:false so they stop rendering as uneditable empty-object controls. Composite components — Breadcrumb, Dropdown, Pagination and Table — take structural children rather than text, so their children control is hidden instead of forced to text. Avatar's alt uses a custom validator function which react-docgen cannot type, so it also fell back to a JSON control and could not be edited; now text. Avatar and Snackbar hardcoded JSX children which always override a spread children prop, leaving their controls inert; both moved into args. Tabs and UploadMedia had their node props declared as well. Result: 25/25 components clean, 194 stories indexing. No shipped component changed and the bundle is unchanged at 78.06 kB. No component was ever functionally broken — every one worked correctly; Storybook simply could not show it.
v2.54.1
PATCH
Wire Storybook actions for six interactive components
21 August 2026
Added action argTypes to DatePicker (onSelect), Rating (onChange), Slider (onChange), Snackbar (onClose), Tabs (onClick) and UploadMedia (onFilesChange). All six fired their callbacks correctly but none were logged, so interactions looked dead in Storybook — Snackbar worst of all, where clicking the close button produced no visible and no logged result despite Snackbar.jsx wiring it properly. Snackbar's Playground also hardcoded onClose after the args spread, which would have silently overridden the action spy; removed so args flows through, verified the close button still renders with no visual change. Audited all six functionally first: DatePicker opens and selects and closes, Rating updates stars and ARIA, Slider tracks value, Tabs moves selection, UploadMedia registers files — none were actually broken, only unobservable. Stories files only, no shipped component changed, bundle unchanged at 78.06 kB. Known gap: SliderRange has no args-driven story, so its onChange still cannot be logged in the Actions tab.
View full changelog
→