- Day 1: Met Alan and Abe, finalized Project Plan
- Day 2: Created Basic Homepage frontend, dived into user authentication, met Abe, talked about technical challenges and moving 
         forward with  the project
- Day 3: Implemented login, signup and logout functionalities, worked on data flow, Met Alan, Murray & Abe, dsicussed handling 
         local storage & loading state and other relevant stuff
- Day 4: Fixed logout bug, worked on self-review, improved UI of homepage, added floating animation on hover
- Day 5: Cleaned up code, working on Add trip, AviationStack API integration and workplace post about progress

    - Day 1 
            - Met Alan, worked on add trip functionality
    - Day 2 
            - Met Maddy, completed add trip functionality
            - Added Amadeus API integration in backend
            - Developed flight search and result display in frontend
            - Stored flight search results in session storage for better user experience
            - Implemented trip addition to database
            - Enhanced error handling with single error state
            - Added loading states to all components
            - Refactored for improved code quality and maintainability

          BREAKING CHANGE: New API endpoints for flight search and trip addition
          
    - Day 3 
            - Met Alan, Maddy, Abe, Murray made the following changes:
            - Backend middleware:
                    - Added authenticateUser function to check session validity
                    - Protecting API routes by verifying user session before allowing access
                    - Returning 401 status if session is invalid or missing
            - Session-based auth:
                    - Storing user info in server-side sessions
                    - Using secure, HTTP-only cookies to maintain session across requests
            - API protection:
                    - Each protected route first passes through authenticateUser middleware
                    - Ensures only authenticated users can access sensitive endpoints
            - Frontend integration:
                    - Sends credentials with each request using withCredentials: true
                    - Handles 401 responses by redirecting to login page
    - Day 5
            - Met with Alan and his manager Yinuo, Maddy, Abe, and Murray to discuss feedback from the previous pull request.
            - Implemented updates based on feedback:
                    - Removed frontend authentication verification and centralized it in the backend for improved security and maintainability.
                    - Implemented redirect to login page if authentication fails, ensuring seamless user experience.
                    - Replaced session storage for add trip functionality with useContext to manage state, improving code organization and scalability.
                    - Created a new route to retrieve user data, laying the groundwork for future features.

    Day 1
            - Completed Upcoming Trips list and Individual Trip page:
                    - Fetched trips from the database and listed them on the Upcoming Trips page, providing users with a clear view of their upcoming travel plans.
                    - Enhanced each trip list view by adding formatted date, time, departure city, and destination city, making the list more interactive and informative.
                    - Developed a timeline for each trip, showcasing detailed flight information and a dynamic flight progress bar, keeping users informed about their journey.
                    - Implemented a feature to recommend when to leave for the airport based on the user's geolocation, airport location, traffic info, and TSA recommendations, ensuring users arrive at the airport on time.
                    - Added various smaller functionalities to display detailed flight information, further enhancing the user experience.