Open abaibik opened 1 year ago
Very good second user story friends 🫶 I have some more suggestions for you.
Value Proposition:
Description:
Acceptance Criteria:
Tasks:
Heading
component could be located in the common used components folder, or? Also for the other components before, your planned folder structure seems to be a bit confusing for me (like ProjectDetails
in features/projects/ProjectDetail.js could be just in a components folder, or?)Great job and keep up the good work 🚀
Hello, and thank you for letting me look at your work! Here are some comments:
Thanks again for letting me look, and happy coding!
Hey ducks, you should implement your content of your user story 6 in this one, since you need a back button for the details page, otherwise the user would be lost forever in the details page. :)
hey team! great work!
I am a little confused about the VP and the last sentence.
The VP always follows the form of the first 3 lines.
As a... I want to ... In order to ...
If you really have more - it should be another US.
➡ but in this case, just delete it. It is implicit already a part of this US. remember- A US is always a story for the user. It is not finished when the user can not navigate back. Keep the information in AC, Tasks and scribble, but you dont need to mention it in the VP.
everything else looks good to me awesome! 🦆
Value proposition
As a team member I want to see the details of the project In order to get a better understanding about the project
Description
Acceptance criteria
[ ] Every project on the homepage is clickable and links to the corresponding detail page
[ ] On the Detail Page:
Tasks
[ ] create a dynamic page pages/projects/[id].js
[ ] create a Heading component
[ ] render the Heading component on the dynamic page
[ ] create a ProjectDetail component inside
[ ] create a Button coponent with a Link back to the overview page
[ ] ProjectDetail props: { project }
[ ] ProjectDetail should render:
[ ] render the ProjectDetail component on the dynamic page and add the { project } prop to it
[ ] take the query parameter id from next/router
[ ] use the id to find the project to display
[ ] create a dynamic route to the ProjectDetail page [id]