Repository navigation
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.