How pankaj116-andc/nexusboard works
1. What this repo is
- NexusBoard is an Angular 18 single-page client application. The architecture is UI-first and browser-run; there is no visible backend, API client, or database layer in the repo.
2. App bootstrap and shell
- src/main.ts, app.config.ts, and app.routes.ts define the Angular startup path.
- app.component.* is the top-level shell that likely hosts routing and the main layout.
- This suggests a standalone Angular app structure rather than a classic NgModule-based one.
3. Primary feature boundary: Kanban
- Most of the application lives under src/app/features/kanban.
- The feature is decomposed into focused UI components for a Kanban board domain: board, columns, task cards, task modal, and activity log.
- This is the main architectural boundary for the app.
4. State ownership
- src/app/core/services/board-state.service.ts is the central state holder for the board.
- The naming implies shared in-memory application state for columns, tasks, selection/editing state, and activity history.
- UI components likely interact with this service rather than talking directly to each other.
5. Domain model layer
- src/app/core/models/board.models.ts defines the board/task data shapes.
- This is the app’s domain contract boundary: components and services should depend on these models instead of ad hoc objects.
6. Board rendering pipeline
- board.component.ts is the container for the Kanban experience.
- column.component.ts likely renders each lane/column.
- task-card.component.ts renders individual tasks inside a column.
- The likely data flow is: board state service → board component → column components → task card components.
7. Task interaction and editing
- task-modal.component.ts is the edit/create/detail surface for a task.
- This indicates a split between read/display components (board, columns, cards) and a focused interaction component for task mutation.
- The modal probably reads from and writes back to the shared board-state service.
8. Activity/history tracking
- activity-log.component.ts is a separate presentation surface for task/board events.
- Architecturally, this implies the board state service likely records actions and exposes them to the log component.
- This is useful for diagramming a secondary data stream: user actions → state service → activity log UI.
9. Shared presentation logic
- src/app/shared/directives/priority-glow.directive.ts is a reusable behavioral/presentation directive.
- src/app/shared/pipes/days-until-due.pipe.ts is a reusable transformation for due-date display.
- These are cross-cutting UI helpers, kept out of the feature components so the feature remains focused on Kanban behavior.
10. Styling and UI system
- tailwind.config.js, src/styles.css, and component CSS files indicate a mix of global styling plus component-scoped styles, with Tailwind in the stack.
- The visual architecture is therefore component-driven, with utility styling layered on top.
11. Project boundaries
- src/app/core contains app-wide primitives: models and services.
- src/app/features contains business functionality.
- src/app/shared contains reusable UI behavior.
- This is a clean separation that should appear in the architecture diagram as core / feature / shared layers.
12. What is not present
- There is no visible persistence layer, REST client, authentication subsystem, or server integration.
- For architecture purposes, treat board data as local client state managed inside Angular, with components synchronized through the service.
13. Tooling/runtime
- Angular CLI is the build and dev runtime (ng serve, ng build, ng test).
- The app targets the browser and uses Angular’s standard tooling plus Karma for tests.
Main entry points: styles.css Global styles · task-card.component.ts Task card · board.component.ts Board view · board-state.service.ts Board state
Components 14
App shell
Angular bootstrap, routing, and top-level layout.
- main.ts · Angular entrypoint that starts the app.
src/main.ts - app.config · Standalone app configuration and providers.
src/app/app.config.ts - app.routes · Top-level application routes.
src/app/app.routes.ts - App shell · Top-level application component and layout host.
src/app/app.component.ts - Global styles · Global styling layer for the application.
src/styles.css
Core
App-wide domain model and shared state.
- Board models · Shared board and task data shapes.
src/app/core/models/board.models.ts - Board state · Central in-memory board state and activity history.
src/app/core/services/board-state.service.ts
Kanban feature
Primary board experience and task interactions.
- Board view · Kanban board container and coordinator.
src/app/features/kanban/components/board/board.component.ts - Column view · Renders a single Kanban column.
src/app/features/kanban/components/column/column.component.ts - Task card · Displays an individual task within a column.
src/app/features/kanban/components/task-card/task-card.component.ts - Task modal · Creates, edits, and views task details.
src/app/features/kanban/components/task-modal/task-modal.component.ts - Activity log · Shows board and task activity history.
src/app/features/kanban/components/activity-log/activity-log.component.ts
Shared UI
Reusable presentation behavior used across the feature.
- Priority glow · Reusable priority-based visual emphasis.
src/app/shared/directives/priority-glow.directive.ts - Due date pipe · Formats due-date timing for display.
src/app/shared/pipes/days-until-due.pipe.ts
Connections 18
- main.ts → app.config: initializes · Bootstraps the Angular application with shared configuration.
- main.ts → App shell: mounts · Starts the root component in the browser.
- app.config → app.routes: uses · Wires application routing into the standalone app setup.
- App shell → app.routes: navigates · Hosts routed views and shell-level layout.
- Board view → Board state: reads/writes · Coordinates board data and task actions through shared state.
- Board view → Board models: uses · Depends on the shared board domain shapes.
- Column view → Board view: nested in · Board composes columns as part of the Kanban layout.
- Task card → Column view: nested in · Columns render task cards.
- Task modal → Board state: mutates · Creates and edits tasks through central state.
- Activity log → Board state: subscribes · Displays activity history produced by board actions.
- Board state → Board models: stores · Keeps board state in the shared domain format.
- Task card → Priority glow: decorates · Uses shared directive for priority emphasis.
- Task card → Due date pipe: formats · Uses shared pipe for due-date display.
- Board view → Global styles: styled by · Relies on global styling plus component styles.
- Column view → Global styles: styled by · Relies on global styling plus component styles.
- Task card → Global styles: styled by · Relies on global styling plus component styles.
- Task modal → Global styles: styled by · Relies on global styling plus component styles.
- Activity log → Global styles: styled by · Relies on global styling plus component styles.