How rckbrcls/portifolio works
Project Components Identification
• Macro Application: At the center is the “main” portfolio application (located in apps/main), which acts as the overarching container and navigation hub.
• Microfrontends: Each subdirectory under apps (like alan-turing, electoral-system, joystick, lojinha-simples, rgbwallet, secret-santa, video-project-manage) represents an independent microfrontend. They are developed using modern web technologies with variations like React, SolidJS, and even Next.js.
• Backend Services/APIs: Under services you find several API services (electoral-system-api, joystick-api, rgbwallet-api, secret-santa-api) which provide the necessary data and business logic. These services use various back-end technologies (e.g., Flask, Node.js) and have their own configuration files (Dockerfile, package.json, etc.).
• Shared Modules: There’s an underlying Turborepo configuration (via turbo.json and pnpm-workspace.yaml) that orchestrates the build, sharing of components, and utilities (such as those under SharedComponents and SharedUtils).
Analyzing Component Relationships and Data Flows
• For each microfrontend, indicate a connection to its corresponding backend API if present. For example, electoral-system (frontend) interacts with electoral-system-api (backend), joystick with joystick-api, rgbwallet with rgbwallet-api, and so on.
• Data flow from the frontends to the backend services. Use arrowheads (e.g., “Served by API1”, “Data from API2”, etc.) to represent how each microfrontend communicates with its respective API.
Notable Architectural Patterns and Design Principles
• Microfrontend Architecture: Emphasize how each project is isolated (deployed and built separately) yet hosted within the macro application.
• Monorepo Management with Turborepo: Indicate the role of Turborepo in managing shared components (e.g., SharedComponents and SharedUtils) and ensuring performance optimization across builds.
• Technology Heterogeneity: Note the mix of both React (and Next.js), SolidJS, TypeScript, and JavaScript, as well as backend frameworks (Flask and Node.js). This diversity is key to understanding how each part of the system is built.