How ycluis/fullstackopen works
Main Components
• Projects by “part” (for example, part1, part2, up to part7). Each “part” addresses a specific exercise or set of exercises.
• For individual projects that are full-stack (such as bloglist or phonebook in certain parts), clearly identify the separation between frontend and backend components:
• Frontend – typically implemented with React (directories like “src”, “public”, and various components, services, and styles).
• Backend – built with Node/Express (files like app.js, index.js, controllers, models, and middleware along with configuration files).
• Supporting infrastructure elements like databases (e.g., when a project uses a db.json file or MongoDB connection hints in projects like part3 phonebook) and containerization (Dockerfiles in part3).
Relationships and Interactions
• For full-stack projects, illustrate the data flow from the React client (frontend) through the REST API layer (backend controllers) to the database or persistence layer.
• The client user interface (React components),
• API endpoints (Express routes and controllers),
• Data layers (simulated databases using JSON files or actual databases when using MongoDB).
• Middleware components that handle authentication, error handling, or token management.
• For projects with Redux or Context API, show internal state flow inside the frontend component bubble.
Architectural Patterns and Design Principles
• Many projects follow the standard separation of concerns into MVC-like patterns (with views in React, controllers handling the API endpoints, and models managing data).
• Some projects illustrate a clear microservice pattern (separate backend and frontend codebases even if in the same repository).
• Components with tests, configuration files (e.g., ESLint, environment samples), and Docker setups must be noted as they show attention to quality, deployment, and environment consistency.
• State management patterns (Redux vs. Context) in the projects under part6 and part7.
Relevant Technologies and Frameworks
• Frontend: React, Redux, and various testing frameworks (e.g., Cypress for e2e tests) as well as CSS styling.
• Backend: Node.js and Express (with clearly organized controllers, routes, and middleware).
• Deployment/DevOps: Docker (part3), environment configuration files, and code style tools (ESLint).
• Supplementary aspects include utilities, services (for making HTTP calls), and configuration management in certain projects.
• A general container for each “part” (e.g., part1, part2, part3, etc.).