
The site, the Matrix Design System and Matrix Rain live in one npm-workspaces repository orchestrated by Turborepo, rather than in a single app or in separate repositories. The intent is partly educational: building publishable packages next to the product that uses them is the point, so the extra machinery is accepted as the cost of learning it.
The website depends on each package by version ("matrix-design-system": "^1.0.0"), npm resolves that to the workspace
copy, and it reads the package's built dist/, not its source. So the site always runs against local changes, while
the packages stay installable exactly as an outside consumer would install them. The price is that every task that
runs or builds the site depends on the packages' build (^build in turbo.json), and npm run dev runs each
package's tsdown --watch alongside the dev server.
@source directive once shipped every component unstyled.apps/website/src/components/features/design-system-next/), not in a
package: the goal is a framework-agnostic design system, not shared Next glue.npm pack, publint, attw, install into a throwaway app) guards what workspace linking
cannot see.