How daniserrano7/jira-clone works
Main Layers and Components
• Domain Layer: Represented by the “src/domain” folder. This layer contains the core business logic including entities such as users, projects, categories, issues, comments, and priorities. Model the relationships (e.g., a project can have multiple categories, each category contains issues that have comments and associated users).
• Infrastructure Layer: Found in “src/infrastructure”, this includes the database integration via Prisma (with the SQLite database) along with related database schemas, seeding logic, and query functions.
• Application/UI Layer: Under “src/app” and “src/app/ui”, this layer contains the presentation, routing, components, session handling, and state management for the web interface. Note the Remix routes (server-side rendering), shared UI components (located in “src/app/components”), and routing logic supporting things like login, projects list, and project space.
• External Services and Tools: Include the SQLite database (with Prisma managing migrations and seeds), Tailwind CSS for styling, and third-party libraries such as Radix UI for accessible components. Also, indicate how server-side rendering (SSR) and cookie-based session storage are integrated by Remix.
Relationships and Data Flow
• In the Domain layer, list key entities (User, Project, Category, Issue, Comment, Priority) and briefly annotate their relationships (e.g., Projects contain Categories → Categories hold Issues → Issues include Comments, with Users associated at various levels).
• In the Application/UI layer, break it into:
• UI Components (React components found in “src/app/components” and “src/app/ui”) that render interfaces for login, project listing, and project board.
• Routing (Remix routes under “src/app/routes”) that link the UI to server-side logic.
• Session and State Management (session-storage and stores) managing cookie-based user authentication and theme information.
Architectural Patterns and Design Principles
• Separation of SSR and Client State: The design leverages Remix Run for SSR, reducing client-side state and using cookies/session stores.
• Component-Based UI: Note the organization of UI components into a modular, reusable structure with clearly defined responsibilities (note usage of Radix and Storybook for component development).
Relevant Technologies, Frameworks, and Libraries
• Remix Run for server-side rendering and routing.
• React with Typescript for building the UI.
• Tailwind CSS for styling.
• Prisma to integrate and manage the SQLite database.
• Radix UI components to support accessibility.
• Vitest for testing, ESLint and Prettier for code quality.