How dua090/mern-stack-web-d works
Project type and purpose
• At the root level you have a “monorepo” or portfolio repository that collects multiple standalone projects and tutorials:
• browser-use examples (Python scripts)
• duastech (a small frontend app)
• fullstackprojects (several MERN‐style apps: chat app, auth, expense tracker, Google OAuth, resume extractor)
• pure HTML/CSS/JS lectures
• interview preparation code (Node/Express)
• MongoDB CRUD scripts
• neonflake/schollprop (full-stack rental app)
• nodeexpress tutorials (various Express demos)
• react lectures (many Vite/React micro-apps)
• tailwind lectures
• threejs demos
• todo/todolist fullstack app
• The purpose is to organize learning samples and mini-projects by technology or by feature.
File structure
• Top-level directories are grouped by technology or course (e.g. react, nodeexpress, tailwind, threejs, fullstackprojects, etc.).
• Under each technology folder you typically find one or more subprojects, each with its own package.json, source directories (src, backend/frontend), config files, and documentation.
• Full-stack examples always follow a similar two-tier pattern:
• backend – Express/Node server, controllers, models, routes, environment config
• frontend – React/Vite or static HTML/CSS/JS, assets, build config
• Other folders contain standalone scripts or tutorials that run without a server (e.g. Python in browser-use, Mongo shell scripts in mongodb, pure HTML lectures in html_css_js).