curtisblackwell / bub Goto Github PK

As an admin, I expect I can create ingredients so admins can use them to create recipes.

Creating an ingredient

• I expect ingredients to have fields for:
  • Name (text)
  • Diets (array)
• I expect the Name field is required.

As an admin, I expect I can create diet-based recipe alternatives so I can be more inclusive of users.

Marking recipes as alternatives

• I expect I can choose existing recipes to mark as an alternative version of the current recipe.
• I expect relations to work in both directions.

NOTE Alternative recipes shouldn't need to have pivot fields for diets since diets can intelligently be determined based on ingredients, just as planned for all recipes.

As an admin, I expect I can log in to the admin panel so I can manage content.

Logging in

• I expect to see a login form at /cp (CP: Control Panel).
• I expect I can log in using my credentials (not displayed here for security).
• I expect to see the CP after logging in.

As an admin, I expect I can create a drink recipe so users can find it on the website.

Creating a recipe

• I expect recipes to have fields for:
  • Name (text)
  • Image (file upload)
  • Ingredients (array: amount, unit, ingredient)
  • Instructions (markdown)
• I expect the name field is required.

As an admin, I expect I can create a diet so I can mark ingredients as meeting their requirements.

Creating a diet

• I expect the create diet form to have a required Name field (text).

We may later add a story for adding a content field that would allow for diet-specific pages explaining any unclear concepts like halal alcoholic beverages.