How trungvose/jira-clone-angular works
Project type and purpose
• This is a front-end heavy, single‐page application built with Angular (v9+), Akita (state management), ng-zorro (UI components), TailwindCSS, and Angular CDK.
• It simulates a simplified Jira‐style kanban board, with modular features (login, project board, issue detail, settings), but currently uses static JSON assets as its “API.”
File structure
• Top-level Angular CLI project: angular.json, tsconfig.*, src/, e2e/, storybook/, webpack.config.js.
• src/app/core – application‐wide services, directives, validators, styles, analytics, “snow” decoration.
• src/app/project – the main feature module (lazy loaded) hosting auth, components (board, issues, navigation, search, user), pages (board, full-issue-detail, settings), Akita state (stores, queries, services).
• src/app/work-in-progress – a second lazy-loaded feature.
• src/assets/data – static JSON payloads as a stand-in API.
• storybook – UI component isolation environment; e2e & karma for tests.
README for additional insights
• Tech stack includes Angular CLI, Akita, NestJS (planned Phase 2 GraphQL API), ng-zorro, ngx-quill, CDK drag-drop, TailwindCSS.
• Architecture overview images: Application architecture (core vs lazy modules) and Akita data flow (component → service → store → query → component).
Detail over guesswork
• Decompose each feature module into its major pieces (pages, key component groups, state files).
• Lazy loading boundaries to highlight on-demand code splitting.
• Both current static data sources and future GraphQL backend to give a complete roadmap.