Milestones
List view
In order to better find high-quality recipes, we will implement a robust rating system. This system will enable users to rate recipes on a scale of 1 to 5 stars, providing a clear and concise way to evaluate the quality and popularity of each recipe. Key Features of the Rating System: 1. Star Rating Scale: Users can rate each recipe from 1 to 5 stars, with 5 being the highest rating. This allows for nuanced feedback and helps highlight the most appreciated recipes. 1. Average Rating Display: Each recipe will display an average rating, calculated from all user ratings. This will give a quick overview of the recipe's overall reception. 1. Number of Ratings: The total number of ratings a recipe has received will be shown alongside the average rating. This provides additional context, indicating whether a high rating is based on broad consensus or a smaller number of reviewers. 1. User Reviews: Users will be able to leave detailed reviews along with their star rating. This feature allows for more comprehensive feedback and helps other users understand what makes the recipe good or where it could be improved. 1. Rating Criteria: To ensure consistent and fair ratings, users will be encouraged to consider factors such as taste, ease of preparation, clarity of instructions, and overall satisfaction when rating recipes. 1. User Authentication: Only registered users will be allowed to rate and review recipes. This helps maintain the integrity of the rating system by preventing spam and ensuring that ratings come from genuine community members. 1. Editable Ratings: Users will have the option to edit their ratings and reviews. This is particularly useful if they try a recipe multiple times or if updates are made to the recipe. 1. Flagging Inappropriate Reviews: To maintain a respectful and constructive community, users can flag inappropriate or abusive reviews. Moderators will review flagged content and take necessary actions. By integrating this rating system, we aim to enhance user engagement and satisfaction, making it easier for community members to discover and enjoy the best recipes our site has to offer.
No due dateTo enhance user experience and make recipe discovery efficient, we will implement a paginated, sortable, filterable, and searchable recipes page. Key Features: 1. Pagination: Recipes will be displayed in pages, allowing users to navigate through a large number of recipes without overwhelming the interface. 2. Sorting: Users can sort recipes based on various criteria such as date added, popularity, rating, and preparation time. This helps users quickly find recipes that best meet their needs. 3. Filtering: Users can apply filters to narrow down their search based on ingredients, dietary preferences, cuisine type, difficulty level, and more. This ensures they find recipes that match their specific requirements. 4. Search Functionality: A powerful search bar will enable users to search for recipes by keywords, making it easy to locate specific recipes or ingredients. 5. Consistency Across Pages: This system will be reused on the private recipes page, ensuring a seamless and consistent user experience throughout the site. By implementing these features, we aim to make it easier for users to discover, sort, and filter through recipes, enhancing their overall experience on our site.
No due dateTo enhance the visual appeal and usability of our recipes, we will add support for images. Key Features: 1. Image Uploading: Users will be able to upload images for their recipes, making it easier to share and visualize the final dish. 2. Preferred Solution: Our current preferred solution for image uploading is uploadthing.com. However, we are open to suggestions for alternative services that may better suit our needs. 3. Image Management: Users will be able to manage their uploaded images, including options to add, delete, and update images associated with their recipes. 4. Payment Setup: Either before or shortly after implementing image support, we will establish a payment setup to support the platform. Details and progress on this can be tracked on our GitHub milestone. By integrating image support, we aim to create a more engaging and visually appealing platform for our users.
No due dateTo ensure the sustainability and growth of our platform, we will implement a payment system. Key Features: 1. Transition from Free Services: Currently, our platform runs on free versions of services like Vercel and Clerk. As we scale, these free versions will no longer suffice. The payment system will help us cover these costs. 2. Cost-Efficient Pricing Model: We will design a pricing model where only the most costly features to host and maintain require payment. This approach will keep the site as accessible as possible while ensuring we can support and grow the platform. 3. Preferred Payment Solution: We are considering using LemonSqueezy (https://www.lemonsqueezy.com/) as our payment provider. They simplify handling taxes and other complexities of running a global service. - Monitoring Industry Changes: With Stripe's recent acquisition of LemonSqueezy, we will stay informed about any changes that may impact our payment processing options and adjust our strategy accordingly. 4. Supporting Platform Costs: The primary goal of adding payments is to support the platform. Features such as image uploads and scaling the platform will incur costs that we need to cover to ensure continued operation and improvements. By implementing this payment system, we aim to sustain and expand our platform while keeping it as accessible as possible for our users.
No due dateThere needs to be a global search function (e.g. https://github.com/timc1/kbar). The search function should ideally be at least somewhat shareable, so the main logic can be used when searching for recipes directly from the recipes page.
No due dateEnhance user engagement and creativity by allowing users to fork and modify existing recipes. Key Features: 1. Forking Recipes: Users can create a fork of any recipe, enabling them to make personal adjustments and improvements. This allows for customization and innovation, catering to individual tastes and preferences. 2. Private and Public Forks: Users can choose to keep their forked recipes private for personal use or share them publicly in the marketplace, contributing to the community’s collective culinary knowledge. 3. Fork Relationship Visibility: Display the relationship between the original recipe and its forks. This ensures the original creator is credited and allows users to navigate between the original and modified versions easily. 4. Popularity-Based Marketplace: The marketplace will primarily feature recipes based on their popularity. Fork relationships will be highlighted to show the evolution of recipes and recognize contributions from different users. By implementing collaborative sharing and forking, we aim to foster a dynamic and interactive community where users can share their culinary creativity and discover new, personalized variations of recipes.
No due date•0/1 issues closedEnable users to plan their weekly dinners using both public and personal recipes. First Iteration: 1. Weekly Dinner Planning: Users can create a meal plan for the current or upcoming week, focusing exclusively on dinners. Future Iterations: 1. Full-Day Meal Planning: Expand the planning function to include all meals (breakfast, lunch, dinner, and snacks), providing a comprehensive daily meal overview. 2. Shopping List Generation: Generate a shopping list based on the meal plan. As a precursor, implement shopping list generation for individual recipes. 3. Meal Timing and Calendar Integration: Allow users to define specific times for meals. Automatically add events to the user's calendar for meal preparation, based on the cooking time required (opt-in feature). By introducing this meal planning function, we aim to help users organize their meals efficiently and make meal preparation a seamless part of their routine.
No due date