Feature Request: Advanced Recipe Management (Allergens, Costing, Sub-Recipes, Dimensions & Calendar Integration)

Feature Request: Advanced Recipe Management (Allergens, Costing, Sub-Recipes, Dimensions & Calendar Integration)

Describe the solution you'd like

I would like to propose a set of interconnected features to elevate the Nextcloud Cookbook app:

1. Ingredient-Level Data (Allergens, Pricing, Nutrition)

   • Move from recipe-only metadata to ingredient-specific metadata.
   • Allow users to store allergens, price per unit, and nutritional values directly within the ingredient database.
   • The app should automatically calculate the total cost and total nutrition for the entire recipe based on the scaled ingredient amounts.

2. Sub-Recipes / Recipe Referencing

   • Allow a recipe to be used as an ingredient inside another recipe (e.g., using a "Tomato Sauce" recipe as a base component for a "Lasagna" recipe).
   • Changes to the base recipe should dynamically update the cost, nutrition, and scaling of the parent recipe.

3. Advanced Yield and Dimensions (Baking/Catering Focus)

   • Expand the simple "Servings" field.
   • Add fields for physical dimensions (e.g., Cake Pan 22x9 cm), total weight (e.g., 2 kg), and piece count (e.g., 12 pieces) to better handle baking recipes.

4. Nextcloud Calendar Integration for Production Planning

   • Add a "Schedule Production" button directly inside a recipe.
   • Clicking this should open a prompt to select a date and time (e.g., "Bake Bread on 2027-02-12").
   • This action should automatically create an event in a chosen Nextcloud Calendar with a reminder and a direct link back to the Cookbook recipe.

Additional context

This would bridge the gap between a simple digital recipe book and a powerful tool for passionate bakers, meal-preppers, and small catering workflows, heavily leveraging Nextcloud's core strength (Calendar integration).

The issue names no files, tests, or entry points. Start by reviewing the Cookbook app structure and locating the recipe data and Nextcloud Calendar integration areas, then split the proposal into separately scoped features. Done requires agreed acceptance criteria for ingredient metadata and calculations, sub-recipes, dimensions, and production scheduling.