US ??? Creating a navigation bar [FUSED INTO US 3]

[Manuella-Sam]

Value proposition

As a user of this Job-search app, I want to have access to navigational elements such as buttons on each page so that I can go back and forth between the homepage the Job categories page and the page where the filtered jobs are displayed.

Description

Acceptance criteria

• A navigation element should be available in each of the category boxes , for the user to navigate between categories page and desired filtered job-list.
• Clicking on the Link in each category-container takes the user to the targeted page
• Clicking on "Home" on the page where each filtered job list is displayed takes the User back to Categories page
• The link should have a consistent color and style pattern so it can easily be recognised by the user

Tasks

• Create a feature branch feature/navigation
• Create a navigation element to navigate between filtered job list page and category-container page
• Add functionality to nav links

Size: M

[CJAkkuec]

Looking good overall, I just have a couple of questions ...

1. What is "Next" routing to if there's no page next up at present?
2. What is "Back" routing to when I'm on the overview page?

I think what you may want is a simple navigation with "Overview" and "Categories". Logically speaking, "back" and "next" only ever need to be a thing if the page you're on isn't strictly part of the navigation items, such as a guided user journey when going from one screen to the next through different "slides" (such as the questionnaire part of your app). This should likely be part of that user story.

[CJAkkuec]

Almost!

I understand the thinking behind adding the .js behind the terms in the navigation bar, but the wireframes are an approximate representation of what the user sees, and I don't thin they'd see that. (At least I hope not. 😂 ❤️ )

Not a hill anyone needs to die on, though - so for what it's worth this US is approverd.

[Manuella-Sam]

You're right.. I´ll correct that detail too