How bipul-dubey/js-fullstack-course works
Main Components
• Frontend/Mobile Applications:
• Several React-based projects:
· JavaScript instructional sections (e.g., JavaScript/Section2, Section3, etc.).
· Gym website ("gym-exercise") using React.
· 3D Portfolio ("portfolio-3d") using React, Three.js, and tailwind CSS.
· Next.js projects ("my-next-implement" and "share_prompts") that illustrate SSR, routing, and API integration.
· A React Native application ("movie_suggest_react_native") especially targeting mobile interfaces.
• Backend/Server Projects:
• Multiple Node.js projects are located under backend_nodejs:
· A NODE-FARM project which deals with file I/O and templating.
· Projects focused on core Node.js features such as event loops, streams, and events.
· An Express-based project (4-NATOURS) that includes controllers, models, routes, and utilities – exemplifying the MVC pattern.
· GraphQL with MongoDB demonstrating a backend powered by GraphQL and model definitions.
• Common Shared Assets and Learning Resources:
• Several JavaScript practice “sections” demonstrating core concepts.
• Additional material like a PDF note (“theory-lectures-v2.pdf”) and external links in the README for resources.
Relationships and Interactions
• For Frontend Applications:
• The React/Next.js projects will typically have a client-side UI communicating with APIs – either provided from within the same repo (such as the share_prompts API endpoints) or external services (e.g., RapidAPI for the gym website).
• In applications like share_prompts and my-next-implement, include the internal routing and API endpoints as separate nodes.
• For Backend Applications:
• For Node.js fundamentals sections:
• How core Node.js modules such as event handling and streams are working internally as learning examples.
Architectural Patterns / Design Principles
• Many projects use common design patterns. For example:
• MVC in the NATOURS project (Controllers, Routes, Models).
• API routings and separation of concerns are evident in share_prompts (with dedicated API route folders and components).
• Component-based design in React/Next.js applications.
• How the separation of concerns appears: client (frontend UIs) and server (Node/Express backends) are clearly defined in different project directories.