US 3: Content Page && Back Button

[dimitriosxmi]

Value Proposition

As a user I want to Have a Content page with the same layout as Dashboard and a Back button, also have the option Content in the Side bar so that I can navigate through the Side Bar to Content page and from there navigate back either through the Side bar or through a Back button ​

Description

​

Acceptance Criteria

• [x] route /content must navigate to Content page
• [x] Content page must have the same layout as Dashboard this means Header, Breadcrumb and Side bar.
• [x] Content page must have a Back button on the top left underneath the Breadcrumb
• [x] Back button icon must be arrow-pointing-left
• [x] Clicking Back button must navigate user to / route
• [x] Side bar must have a button with the text 📚 Content which on click navigates to the Content page ​

Tasks

• [x] switch to main branch and perform a git pull in the terminal
• [x] create the branch feature/us3/content-and-back-button
• [x] add arrow-pointing-left icon file
• [x] create content page file
• [x] apply to Content page the Header, Breadcrumb, and SideBar components with the same layout as the Homepage does
• [x] create BackButton component
• [x] apply to Content page the BackButton component underneath the Breadcrumb component
• [x] add 📚 Content button option in the SideBar component

Previous US Next US

[LukasWeckner]

Hi Dimi,

I really like the way you wrote your acceptance criteria and your tasks. To me those seem quite clear and easy to understand.

When I opened your user story I was struggling a bit with the I want to part of your value proposition though. I think that might be because it is a little too long and maybe not so much what a user would directly ask for but more written from your perspective what you would like the feature to be like.

For example a user probably wouldn't care or know which route the app uses and what sections are used on different pages. Maybe it's better to just describe that he wants to able to navigate to menu x and back and put the way how it will be done in the acceptance criteria/tasks only.

[dimitriosxmi]

Hi Dimi,

I really like the way you wrote your acceptance criteria and your tasks. To me those seem quite clear and easy to understand.

When I opened your user story I was struggling a bit with the I want to part of your value proposition though. I think that might be because it is a little too long and maybe not so much what a user would directly ask for but more written from your perspective what you would like the feature to be like.

For example a user probably wouldn't care or know which route the app uses and what sections are used on different pages. Maybe it's better to just describe that he wants to able to navigate to menu x and back and put the way how it will be done in the acceptance criteria/tasks only.

---

Thanks for your time and for your review @LukasWeckner 😊 I see, so hereby I believe that it will be fine not getting any specific in the Value Proposition?

---

I've made some changes to simplify it.. from OLD As a user I want to have a new page to access with the route Content which will have the same layout as Dashboard does without the Recent Uploads section and instead a Back Button, also this new page should be accessible through the Side Bar so that I can navigate to the Content page and navigate out of it either through the Back button or the other button options in the Side bar 👇 to NEW As a user I want to Have a Content page with the same layout as Dashboard and a Back button, also have the option Content in the Side bar so that I can navigate through the Side Bar to Content page and from there navigate back either through the Side bar or through a Back button