Project LEAFLOG Status Update

Mid of Sprint 1

Date: 2024-02-24 - 2024-02-28

Major Project Feature Summary:

Status	Symbol
Completed	✅
In Progress	🔶
Pending	⛔️

Major Project Feature % completed to date

Feature	Status	Completion Percentage
Sign Up / Sign In along with Google OAuth	✅	100%
Plant Logging	✅	100%
Notification feature	✅	100%
Home Page	✅	100%
Plant Information Page	⛔️	0%
User Profile	🔶	50%

Current Project Status Summary: GREEN

Currently, the project is going well, the frontend and the backend teams are actively working on implementing core functionalities and in the upcoming sprint we will be planning to integrate the frontend part with the backend code.

Team Status Summary:

The team is finishing some touching on the website framework and starting to stylize the website. The backend is in very good shape, and will be worked on to continue connecting functionality.

Team Goals for the upcoming week:

• Finish creating all pages
• Plan for API usage and integration
• Plan strategy and delegate functional user stories

Individual Team Member Status:

• Mikayla: Initialized and stylized key pages, created header.

  Next week: Further stylize all pages, ensuring consistency.

• Atishay: Writing routes for data accessing, implementing google Oauth authentication.

  Next week: Finish implementing routes and authentication and start work on merging backend with the frontend.

• Hiral: Worked on the landing Page of the webapp.

  Next week: Work on Blog details of the page.

• Caitlin: Working on integrating HTML and TS components.

  Next week: Continue integrating HTML and TS components, work on front end. Investigate testing options. Investigate APIs for potential future functionality.

Past week team activities:

• Pair Programing for Frontend (Mikayla & Caitlin) 02/27/2024
• Status update group meeting (ALL) 02/19/2024
• Pair Programming for Frontend (Hiral & Mikayla) 02/17/2024, 02/27/2024

Team Project Decisions:

We were planning to not use Express.js as we are using next.js, but after understanding our project requirements and the way our code is set and written, we decided to stick to express.js but also use next.js (explicitly for frontend and not for routing), this would have forced us to rewrite the backend routing exclusively in next.js. Now, the challenge is to make the next.js read the routes from express.js code, which we need to figure out.

Other Comments: