How torque-labs/torque-public works
1. The Next.js web app (under apps/web), which demonstrates the integration of the Torque UI kit and Torque SDK.
The Torque UI Kit library (inside packages/ui) which provides reusable UI components.
3. Several configuration packages (in packages/config-eslint, packages/config-tailwind, and packages/config-typescript) for standardizing project settings.
4. Extensive documentation (in the docs folder) that covers usage, developer guides, API references, and integrations.
• Apps: specifically, the “web” Next.js application.
• Packages: including “ui” (the main UI kit library) and the config packages (eslint-config, tailwind-config, typescript-config).
• Documentation: shown as an external supportive component that informs both end users and developers.
• For the “apps” section:
• For the “packages” section:
• An orchestration layer:
• Usage of Turborepo by drawing a “Turborepo” or “Monorepo Orchestrator” component. This layer manages installing dependencies, running development servers (npm run dev), building (npm run build), and starting production servers (npm run start).
• Additional external interactions:
• If needed, add nodes for external tooling (e.g., Node.js and npm) which are used to build and develop the entire repository.
• That the repository’s documentation (found in the docs folder) is available to guide integration and usage, pointing to both developers and marketers.
• Use clear, descriptive labels for every component (e.g., “Next.js Web App”, “Torque UI Kit”, “ESLint Config”, “Tailwind Config”, “TypeScript Config”, “Turborepo Build Pipeline”, “Documentation”).
• Present dependency lines that show “import” or “dependency” relationships—for example, the web app relying on components from the UI kit, and the shared configurations flowing into both the app and package build processes.
• Architectural patterns:
• The project follows a modular monorepo architecture, which supports reusability, consistency, and integrated development through Turborepo.
• That the separation of concerns is evident between runtime applications (the web app) and the UI library, along with configuration separation for development and production tools.