How strapi/design-system works
Project type and purpose
• It’s not a standalone full-stack app; instead it’s an open-source UI toolkit with build, test, versioning, and publishing pipelines.
Main architectural components
a. Monorepo root (Yarn v3 workspace + Turbo)
b. Packages
• packages/primitives
c. Documentation site (docs/) – powered by Storybook + Vite, imports design‐system
d. Shared configs & scripts
• ESLint / Prettier / TypeScript configs
• .changeset folder & scripts for versioning
• turbo.json for task orchestration
• scripts/pre-publish.sh, find-release-from-changeset.js
e. CI/CD pipelines (GitHub Actions workflows + custom actions)
f. Test framework (Jest + jsdom mocks)
Relationships & data-flow
• The monorepo orchestrator (turbo + Yarn workspaces) runs install, lint, typecheck, test, build, and publish across all packages.
• Each package has its own src/, tests/, tsconfig, and build config (packup or rollup).
• Changesets detect version bumps, custom scripts generate releases, GitHub Actions trigger on PRs, merges, and scheduled jobs (bundle size, chromatic visual tests, release).
Architectural patterns & design principles
• Monorepo with shared configs and task orchestration (Turbo + Yarn workspaces).
• Component-driven development (Storybook).
• Semantic versioning and changelog automation (Changesets).
• CI/CD as code (multiple GitHub workflows + custom actions).
• Package encapsulation: each UI module is isolated, tested, and published separately.
Technologies / frameworks
• Node.js, Yarn v3 (Plug’n’Play), Turborepo
• React, React-DOM, styled-components
• TypeScript, Jest, Storybook, Vite
• Changesets, Husky (git hooks), ESLint, Prettier
• GitHub Actions for CI/CD