This is Devlog 1, but just so you know: I’ve been working on this project since way before I even heard of Flowertown.

Here’s what I’ve coded so far – Key Features & Technical Setup:
Built with Express.js
Authentication: * Used bcrypt for secure password hashing.
Implemented JWT (JSON Web Tokens) for stateless auth.
Built the entire Login and Registration flow from the ground up.

Authorization & Security:
  Custom Middleware: To validate tokens and protect specific routes.
  Data Isolation: Added logic so users can only see and edit their own todos no peeking at others' data!
  Secure Storage: Tokens are stored in HTTP-only cookies to keep them safe from XSS attacks.

Input Validation:
    Using express-validator to clean up and check incoming data.
    Set up custom error handling with messages that actually make sense.

Rate Limiting:
    Added protection against Brute-Force attacks by blocking IPs that spam requests.
    Granular Limits: I set different limits for sensitive stuff (like /auth) compared to general routes.

Today I spent some time improving the project structure by reorganizing my files to make everything cleaner and easier to maintain. This makes the codebase more readable and will help a lot as the project grows.

I also implemented a temporary ID system for newly created todos, so each task now has a unique identifier even before the backend is connected. This is an important step to ensure smooth state handling later on.

Additionally, I started working on a** login page** where users can either create an account or sign in. This feature is not fully functional yet, but it’s an important foundation for when I connect the frontend to a backend and add real authentication in the future.

I have implemented the functionality to add new tasks and mark tasks as completed. Completed tasks now automatically move to the “Completed” section, and tasks can also be moved back to the active list if needed.