US4 - DetailsPage

[gwittm]

Value proposition

As a user I want to have a details page for each recipe In order to see all information about it.

Description

Update:

Acceptance criteria

• [x] Clicking on the title at Recipes Page leads to its detail page
• [x] that shows a heading (dynamic; title of the recipe)
• [x] details page that is divided in sections:
  • [✅] Overview section displays type, needed time, serving size
  • [✅] Ingredient section displays all necessary ingredients for the recipe
  • [✅] Preparation section guides through cooking process
• [x] a Button, that redirects to starting page, where you can see an overview of all recipes

Tasks

• [x] new branch "US4-detailsPage"
• [x] create Component Recipe
• [x] create titles at Recipes Page as Links with dynamic routing to details page (Router push)
• [x] Recipe displays heading and all sections
• [x] styled sections display flex
• [x] Link-Component (visible as button), that redirects to starting page

[FelineHuhn]

Very nice user story 🙌 And I love the app idea!

I have two general suggestions: You could be a bit more detailed in your acceptance criteria and also tasks.

To give you an example for the acceptance criteria - Instead of the short acceptance criteria: "section ingredients", "section preparation", (...) you could write more descriptive criteria, which would explain more, what the user should see:

• [ ] The details page should be divided into sections:
  • [ ] An overview section displaying the recipe type, preparation time, and serving size
  • [ ] An ingredients section listing all necessary ingredients for the recipe
  • [ ] A preparation section guiding through the cooking process

Just to give you another example for a more descriptive task - instead of "Component Recipe" you could better write "create a component Recipe"

This is a general device for all future user stories, so you don't have to adjust it in this user story, but maybe enhances your future user stories.

The reason for giving you not the green check for now is, that in the wireframe + acceptance criteria + tasks is missing the starting point of your feature, or? From where does the user get to the details page? You should show this in the wireframe and also mention it in the acceptance criteria and tasks, since the feature will not be accessible to the user without a link somewhere, or?

[gwittm]

Thank you for your helpful comments! We changed our US accordingly :)

[NikRoe]

Well done 👏

[gwittm]

Hi All, we just noticed that we forgot to mention one section. The following sections will be displayed in the overview section: type, preparation time, amount of servings, preparation. Instead of preparation-section in the first drawing, the instructions will be displayed at this place. Please notice the second image.

[gregorsart]

One little thing I noticed. You write: "Link-Component (visible as button), that redirects to starting page".

Maybe you can specify:

1. What is the Starting Page
2. What will the href be or will it be a Router.back()

Apart from that, I understood everything. The wireframes are nice, too.

[gwittm]

Thank you :)

[NikRoe]

Hi there,

with the updates it looks good to me and your comment serves as a great addition / extension for the previous description of the US.

Hi All, we just noticed that we forgot to mention one section. The following sections will be displayed in the overview section: type, preparation time, amount of servings, preparation. Instead of preparation-section in the first drawing, the instructions will be displayed at this place. Please notice the second image.

For upcoming reviews it would be amazing, @gregorsart, if you could also leave a reaction is slack, so that people know the current status of the Review =)