v1.0.0

Read README.md for instructions on how to build locally

(4/23/25) In our previous meeting, the team was wrapping up sprint 2 and discussing our backlog of tasks to complete for sprint 3. Towards the end of sprint 2, we were not quite where we would have liked to be so we must be diligent in the final sprint to ensure all required features are implemented and done to the level of quality required. In this meeting we held a discussion as to what we would like to implement for our “beyond the requirements feature”. Many ideas were tossed around, such as voice-integration or an AI chat bot, but we ended up deciding to work on allergen/nutritional information for the benefit of our users as this also is related to the theme of accessibility.

(4/25/25) In our lab SCRUM meeting this week, we laid out what our course of action will look like over the next week and a half as we are in a crunch to implement all the required features in time. We discussed some high-level design decisions regarding the layout and function of our customer menu page and concluded that it will be made as an amped-up version of our employee POS interface, complete with accessibility features - such as language translations and descriptive images – and a more customer-friendly layout and appearance.

(4/28/25) In our previous meeting, each member went over their progress on their assigned tasks and the team discussed the overall progression of the project. Due to time constraints from the approaching demo and presentation submission, members agreed to cut out some of our planned features and replace them with alternatives that are faster to implement. We also investigated some possible accessibility improvements for our webpages. Lastly, the team went over possible changes to environmental variables and fetch request parameter for our website deployment.

v0.2.1-alpha

Read README.md for instructions on how to build locally

Scrum 1 (4/9/25)
In our previous meeting, we discussed our latest progress in the manager page. Then, we brainstormed the high-level implementation of the kiosks for customer ordering. We decided to create a new, cleaner, and more accessible page specifically for customers to order. Unlike the staff’s page, where the ordering process happens over several pages, we decided to condense the process to one (or two at max) page, with pop-ups windows for shopping cart and finalizing orders. We also looked into implementing the external apis, some further backend functions, and some potential changes to the front-end esthetics.

Scrum 2 (4/11/25)
In our previous meeting, we discussed each members’ progress and the bugs we are struggling with. We talked further about integration between front and backend and worked on potential solutions for the errors that we ran into while doing integration. We have decided on the structure for the customer kiosks and begun talks on accessibility designs. With a majority of the back-end functionality completed, we have the back-end members begin transition into front-end development.

Scrum 3 (4/15/25)
In the previous meeting, we talked about our latest progress in the use of external apis. We talked about references for the customer kiosks and the designs for the website home page. One important topic we discussed is regarding how to make our website more accessible and complainant to WCAG 2.1. Members brief over their recent activities, such as learning about React (for backend people to transition into front-end), work-in-progress for front-end functionalities, and debugging on some on- going issues. The team agreed on future goals, meeting times, and tasks to be split.

v0.2.0-alpha

Read README.md for instructions on how to build locally

Scrum 1 (4/9/25)
In our previous meeting, we discussed our latest progress in the manager page. Then, we brainstormed the high-level implementation of the kiosks for customer ordering. We decided to create a new, cleaner, and more accessible page specifically for customers to order. Unlike the staff’s page, where the ordering process happens over several pages, we decided to condense the process to one (or two at max) page, with pop-ups windows for shopping cart and finalizing orders. We also looked into implementing the external apis, some further backend functions, and some potential changes to the front-end esthetics.

Scrum 2 (4/11/25)
In our previous meeting, we discussed each members’ progress and the bugs we are struggling with. We talked further about integration between front and backend and worked on potential solutions for the errors that we ran into while doing integration. We have decided on the structure for the customer kiosks and begun talks on accessibility designs. With a majority of the back-end functionality completed, we have the back-end members begin transition into front-end development.

Scrum 3 (4/15/25)
In the previous meeting, we talked about our latest progress in the use of external apis. We talked about references for the customer kiosks and the designs for the website home page. One important topic we discussed is regarding how to make our website more accessible and complainant to WCAG 2.1. Members brief over their recent activities, such as learning about React (for backend people to transition into front-end), work-in-progress for front-end functionalities, and debugging on some on- going issues. The team agreed on future goals, meeting times, and tasks to be split.

v0.1.0-alpha

Read README.md for instructions on how to build locally

Scrum Meetings

In our meeting on 3/28, we had an in-depth team discussion about the high-level architecture and functionality of our application. One of the key decisions we made was to use Express.js as the framework for our backend implementation. We also explored the initialization process of the backend, including setting up routes and preparing it to handle requests from the frontend. On the front-end side, we discussed the development of Manager Cards as an important upcoming feature. At that point, most of the foundational components related to the drinks section—such as individual drink items, categories, and add-ons—had been implemented. With those elements in place, we decided that after finishing the rest of drinks we would shift focus toward building out the Manager interface. Only building cards for the moment. We agreed that the card components for the Manager section would be our next priority. These cards would serve as the visual and functional building blocks for managing items or data from the backend. Initially, the cards would display basic information, but we planned to add more interactivity and functionality—such as inventory tables and order graphs—as the front-end development progressed.

In our 3/31, we primarily focused on getting our application up and running. With both the frontend and backend in place at a minimal level, we implemented a unified “start” script using npm-run-all. This allowed us to run both parts of the application concurrently, streamlining the development workflow and ensuring the front and back ends communicate effectively during startup. We also reviewed the current state of our Minimum Viable Product (MVP). On the frontend, we began developing key components for essential user flows, including the checkout and login pages. In addition, we started implementing the structure for browsing drink categories, where each category includes a set of individual drink items along with configurable add-Ons. On the backend, we moved away from hardcoded data by setting up dynamic communication between the frontend and a connected database. This allows drink data to be fetched from the backend in real-time, making the system more flexible and scalable as we continue development.

During our meeting on 4/2, we focused on reviewing the progress made across both the backend and frontend of the application. On the backend, we worked on developing API endpoints to allow seamless communication between the frontend and database, aiming for efficient and reusable data access throughout the app. This included setting up calls to dynamically fetch and manage drink data instead of relying on hardcoded values. On the frontend, we began implementing key UI components inspired by previous project work, such as the inventory table, order functionality, order history histogram, and the X and Y reports used for logging and financial tracking. We also made initial updates to the Settings page layout. As the frontend still relies heavily on backend support to be fully functional, we agreed that the upcoming focus would be on completing more of the backend and API development and to begin work on the Checkout Page to improve the core user experience.