How amruthpillai/reactive-resume works
Main Components
• Frontend Applications:
• “apps/client”: The main React (Vite) frontend that users interact with. It handles login, registration, resume building (with pages for authentication, builder, dashboard, home, etc.), and integrates detailed components such as various resume sections, theming, notifications, and localization.
• “apps/artboard”: Likely a specialized part of the application for designing or previewing resume templates in real time. It includes its own set of components (templates, pages, etc.).
• Backend Server:
• “apps/server”: A NestJS-based backend that exposes APIs for authentication, resume management, user management, email services, storage, and more. Within this, modules are clearly separated (auth, contributors, feature, health, mail, printer, resume, storage, translation, user) which points to a micro-modular architectural style.
• Shared Libraries:
• “libs/dto”: Contains Data Transfer Objects used for standardizing communication between frontend and backend.
• “libs/hooks”: Provides reusable React hooks for frontend logic.
• “libs/parser” and “libs/schema”: Handle parsing of resume data, templates and schema validation.
• “libs/ui”: Contains shared UI components used across different frontend parts.
• “libs/utils”: Offers utility functions (such as array, string, date, and other namespace functions) used throughout the project.
• Infrastructure and Tools:
• Database and ORM: Uses PostgreSQL as the primary database along with Prisma ORM for database operations.
• Object Storage: Minio is used for storing objects such as avatars, PDFs, and resume previews.
• External Services:
▪ OpenAI integration for functionalities like content improvement and tone adjustment.
▪ Browserless service for headless Chrome operations (PDF printing and preview generation).
▪ SMTP server for sending password recovery and other emails.
▪ OAuth providers (GitHub, Google) to allow for third-party authentication.
▪ Localization and translation through LinguiJS and Crowdin.
• Containerization and Deployment Tools: Docker-related files and multiple Docker Compose files indicate containerized deployment and various environments (development, swarm, traefik-based setups).
Relationships and Data Flow
• The Frontend (both apps/client and apps/artboard) will interact with the backend server through RESTful APIs secured with JWT or other guards (note the existence of multiple authentication guards and strategies).
• The backend server communicates with the database (Postgres) via Prisma ORM, manages file storage via Minio, and performs PDF generation via Browserless.
• The shared libraries (DTOs, UI components, hooks, parser, utilities) ensure that both the frontend and backend adhere to a consistent contract and code reuse—thus, they fall into a “common” layer.
Architectural Patterns and Design Principles
• Micro-modular / Layered Architecture: Layers for UI, business logic, data access, and utilities are clearly differentiated.
• API-First Communication: Consistent data contracts (provided by DTOs) are used between the frontend and backend.
• Scalability & Extensibility: The libraries and consistent use of external configuration files (like Dockerfiles, Compose files) allow easy scaling, customization, and deployment.