Bridge Training

UI

The three UI packages and how they stack.

Three packages share the interface work, each one page tree below. They stack: the design system knows nothing of bridge, the bridge components know nothing of the product model, and the product components take ViewModels rather than domain types.

SectionPackageRole
Design system@workspace/uiNeutral primitives: Radix components, Tailwind tokens, theming, tour
UI Bridge@workspace/ui-bridgeBridge display and input: atoms, fields, hand, board, auction and play surfaces
UI Training@workspace/ui-trainingProduct-model components (deals, users…) fed by ViewModels

Where a component belongs follows from what it depends on: a value of the bridge domain goes to UI Bridge, a value of the product model to UI Training, anything else to the design system. See Architecture for the dependency rules.