How line/abc-user-feedback works
Project type and purpose
• This is a monorepo for a full-stack VOC (Voice of Customer) management system called “ABC User Feedback.”
• It comprises:
• A Next.js web admin frontend (apps/web)
• A NestJS REST API backend (apps/api)
• A CLI tool (apps/cli) for spinning up local infra and orchestrating services
• Shared UI and utility packages (packages/ufb-react, ufb-shared, ufb-tailwindcss)
• End-to-end and integration test suites
File structure
• Top-level “apps” directory splits concerns:
• api – NestJS modules (common, domains, configs, shared, operation, scripts)
• web – Next.js pages, features, entities, widgets, server handlers
• cli – Infrastructure orchestration via Docker Compose templates
• “packages” holds reusable UI components, shared types, and TailwindCSS theming
• Root “docker” and workflows define container images, infra stacks (MySQL, OpenSearch, SMTP, optional S3)
• Test harnesses under apps/api/integration-test, apps/api/test, apps/e2e
README insights
• Monorepo powered by Turborepo (turbo.json)
• Dev workflow uses an “auf-cli” for init/start/stop commands
• Infra requirements: MySQL 8, OpenSearch 2.16, SMTP, S3
• Production images published to Docker Hub for web and api
Elements
• Labels for each component (e.g., “Next.js Frontend,” “NestJS API,” “MySQL DB”)
• Rectangles for application containers
• Clouds for external services
• Diamond or node symbols for the CLI/orchestrator