Winter 2025 Features

[torieee]

Winter 2025 Features and Bug Fixes

Welcome Winter 2025 team!

This page is where you'll find features and bug fixes to work on. Bug fixes should take first priority (and help new team members get familiar with code base), but don't worry about all of the bug fixes right at the beginning. I assigned a story point value for each so our new members can get a feel for the difficulty, but change those or ignore if they don't fit.

All features are in order of priority per category. Bolded features should be completed first. If there is anything a team member would really like to work on or do that's not on this list, add it under the appropriate header! When you pick up a feature, put your branch name next to the feature so that everyone can find your feature quickly, and check it off when you've completed it.

Remember, NO code should be committed directly to the main branch. Please create a pull request and wait for it to be approved when you want to merge your code with main.

Bug Fixes/Small Changes

• Fix Login / Registered User bugs - When user attempts to logs in, they don't actually get logged in. This worked until last pull request was pushed to main (reclogin).
• All new team members: Add your name, major, etc. to the About Us page {1 pt}
• Report recipe: currently, when a single user reports a recipe, it is removed from search results and sent for admin approval. Change this so that A) the recipe is not removed until the Admin deletes it if less than four unique users reported the recipe AND B) remove if four unique usernames report the recipe (we want to prevent a single user from spamming user created recipes and removing everything). {2 pts}
• Update readme.md at the end of the quarter {1 pt}
• Look into automating some additional recipe tagging to resolve issue where dietary restrictions aren't followed. I.E. vegan diet set, but can search for and find steak recipes when none should show up. This has to do with Edamam tags and may require us to add additional tagging. {3 pts}

User Experience Features

• Like buttons with counters for each type of recipe/comments {5 pts} - User-created recipe like button, Edamam recipe like button, Comment like button
• Nested comments {3 pts} - currently users can comment on recipes, but cannot reply to existing comments in a nested fashion. Create nested commenting capabilities where users can reply to specific comments.
• Public user profile {21 pts} - 1) Create profile page which displays username, full name, stock photo, and 500 char limit bio, 2) Toggle button for public/private (allow all users to view or private only to that user), 3) Add username hyperlink in user created recipe that takes user to the recipe creator's profile. If public, display the profile. If private, display the username and a "this user's profile is set to private" message.
• Tag cuisine types in user created recipes for filtering (follow Edamam tags for consistency - may have to implement additional logic based on user dietary profile filtering) {3 pts}

UI Features

• Deploy new UI {1 pt} - Torie will merge the new UI with the main branch. If it is not merged, ask Torie to merge it.
• Clean up site graphics, sizing, etc. Make sure website is responsive to different screen sizes and the mobile version of the site is sized appropriately. Make it look pretty! {2 pts}

General Site Features

• Complete implementation of Google AdSense ads (this is partially completed) {3 pts}

CI/CD and Architecture Features

• HTTPS / SSL certificate implementation
• Cron job for database backup across VM restarts {5 pts}
• Cache data such as my recipes so we don't need to fetch each time (this will make loading faster) {3 pts}

Backlog Features (work on these if you find them interesting - not a priority)

• Refactor legacy tests for new client. When complete, remove all legacy source {13 pts}
• Update client/server so you can run standalone from docker. CORS issue between ports and requests. Need to handle the additional port for CORS (client 3000, server 3001). {8 pts}
• Find different CI/CD solution than GCP VM. This could be Azure, another GCP service, etc. {13 pts}
• Mobile application (need to discuss this further) {34 pts}