ToDo-Console-Manager

πŸ“ ToDo Multi-User Web App


πŸ‘©β€πŸ’»πŸ‘¨β€πŸ’» Team Members


πŸ“Œ App Idea

A simple multi-user ToDo web application prototype where users can enter their name, receive a random avatar, and manage their personal tasks.

Each user has their own task list stored in a MongoDB database.


πŸ‘₯ Target Users (User Story)

As a user, I want to enter my name, access my personal dashboard, and manage my tasks so that I can stay organized and track my work easily.


βš™οΈ Features

πŸ‘€ User System


πŸ“‹ Task Management (CRUD)


🎨 UI / UX Features

πŸ› οΈ Tech Stack


πŸ—οΈ Architecture


πŸ“Š Product Backlog

πŸ”· Epics


πŸ“¦ Selected Capability Boxes (Pathway 1)

Box What We Did Evidence Notes
Advanced Architecture Built REST API using Node.js + Express https://github.com/sweetiesyvi/ToDo-Console-Manager/issues/7#issuecomment-4321325883 Clean backend structure
Database Integration Used MongoDB Atlas for persistent storage https://github.com/sweetiesyvi/ToDo-Console-Manager/issues/8#issuecomment-4321330324 Cloud-based database
CRUD System Full task management (create/read/update/delete) https://github.com/sweetiesyvi/ToDo-Console-Manager/issues/14#issuecomment-4321342194 Core system implemented
UI / UX Improvement Alerts, avatars, navigation flow https://github.com/sweetiesyvi/ToDo-Console-Manager/issues/10#issuecomment-4321344015 Better user experience
Debugging Fixed Node.js ES module configuration issue https://github.com/sweetiesyvi/ToDo-Console-Manager/issues/24#issue-4330137817 Issue resolved during development
System / Infrastructure Connected backend to MongoDB Atlas cloud DB .env + server configuration Full-stack setup

πŸ”§ Debug Case Study

❗ Problem

The Node.js server initially failed to run due to ES Module configuration issues.
Setting up the GCP environment was also challenging due to limited available zones.


🧠 Cause

Mismatch between ES module syntax (import/export) and Node.js configuration.
Additionally, some GCP regions had limited availability for free-tier resources.


πŸ› οΈ Fix


πŸ“Œ Important Note

No direct screenshots or external logs were captured during the debugging process. However, the issue was identified and resolved during development, and the final working state is reflected in the current codebase.


πŸš€ Sprint 99 (Future Improvements)

✨ Planned Features

πŸ› οΈ Improvements


🐞 Known Limitations


πŸ’‘ Design Philosophy

This project was intentionally built as a prototype, focusing on:

Advanced features were intentionally deferred to future iterations.



πŸ” Access & Deployment


πŸš€ How to Run Locally

```bash id=”runfinal1” npm install node server.js


Open browser:

```id="runfinal2"
http://localhost:3000

πŸ’‘ Final Notes

This project demonstrates a full-stack prototype application with:

As a prototype, the focus was placed on core functionality rather than advanced UI or extended feature sets. Future improvements are clearly outlined in Sprint 99.