How 100xdevs-cohort-3/assignments works
Project’s Nature and Purpose
• This repository is a “meta-project” comprising multiple week-by-week assignments.
• Each week folder (week-1, week-2, … week-19) contains one or more self-contained exercises or mini-applications. Some assignments are static HTML/CSS puzzles, while others are full-stack exercises (using backend routes, Express middleware, React components, Next.js pages, and even database integrations via Prisma).
• At the top layer, represent the repository as an umbrella “100xdevs Cohort 3 Assignments” container.
• Below that, break out the major week folders (e.g., week-1, week-2, … week-19) as separate nodes or layers.
• For each week, if there are multiple projects or assignments (for example, week-10 has “authSystem” and “userApi”), represent these as subcomponents connected to their respective week folder.
And Label Main Components for Each Assignment
• For projects that are plain HTML/CSS/JS (like many in week-1, week-2, week-3, or some in week-9):
– Label components such as “Static Frontend,” “Assets (CSS/JS/Images),” and “HTML Templates.”
• For full-stack assignments (e.g., week-4/hard, week-5, week-7, week-19):
– Identify separate layers/components:
▪ Frontend (client-side assets such as HTML files, React components, Next.js pages)
▪ Backend (Node.js servers, Express routes, middleware, API endpoints)
▪ Database/Models (for projects using Prisma or database-related directories, e.g., week-18’s prisma folder)
▪ Middleware/Utilities (folders like “middlewares” in week-4 and week-7 which include rate-limiting, authentication, logging).
• For projects that include tests (e.g., many assignments have tests or __tests__ folders):
– Optionally include a “Testing” component or annotate that these components follow test-driven practices.
Relationships and Interactions
– Inside the backend, show interactions between “Middleware” and “Routes/Controllers.”
• For assignments involving asynchronous JavaScript or promise-based functions (see week-2’s async-js challenges), you might represent the flow of asynchronous operations from function calls to callbacks/promises.
Architectural Patterns and Design Principles
• For assignments using modular file structures (such as React components in separate folders or Express route separation), indicate how modules communicate.
• Where applicable, note patterns such as MVC (in backend projects), component-based architecture (in React or Next.js assignments), or even simple procedural code (in straightforward HTML/JS assignments).
• Clear layering (presentation, business logic, data access) in more complex projects like week-19 which uses Next.js and Prisma.
Technology and Framework Labels
• Within each component/assignment, annotate relevant technologies:
– For client-side code: HTML, CSS, JavaScript, React (JSX files), Next.js (app directory, API routes)
– For backend code: Node.js, Express (look for routing files), TypeScript (in week-17), middleware design.
– For database integration: Prisma and migration folders are present in week-18 and week-19.
– For build configuration: note Vite, ESLint, Tailwind CSS (week-19 tailwind.config.ts), and so on.