Emotion-Details

[ladydarkja]

Value proposition

As a user I want to access detailed information of the seven universal emotions, So that I can better understand and analyze my them.

Description

Acceptance criteria

• [ ] Clicking an emotion from the list links to the details page for that specific entry.
• [ ] On the details page, the following information are displayed:
• [ ] A brief description of what the emotion is and how it is generally experienced.
• [ ] Tags or list of "Sub-Emotions" or nuanced variations or related feelings. For instance, under the umbrella of Joy, there could be contentment, pride, optimism, etc.
• [ ] The details page is visually differentiated using different styling (e.g. background colors, font colors).
• [ ] A Link "back to list" is displayed to return to the list of the seven universal emotions.

Tasks

• [ ] Create and switch to the feature branch feature/emotion-details
• [ ] Create a Dynamic Route for Emotion Details: Create a directory emotions inside the /pages directory. In the /pages/emotions directory, create a dynamic route named [slug]/index.js.
• [ ] Design a EmotionDetails Component that maps over the emotions array (e.g. name, description, sub-emotions) to display each emotion including layout and structure.
• [ ] Render EmotionDetails on [slug]/index.js.
• [ ] Add minimal styling.
• [ ] Add Back to List Link: Include a button on the details page to navigate back to the list of seven universal emotions.

[FelineHuhn]

The user story is well-structured and the tasks match good with everything. Very good job 🥳 Just one important thing: You lost your value proposition 😱

And I have some more thoughts:

1. Wireframes

   • Awesome wireframes! Additionally you could implement example data, to show the wireframes more realistic, e.g. instead of empty "boxes" of subemotions, you could show realistic sub emotions there (for me as someone, who don't know much about emotions, subemtotions etc. it would be much more descriptive and understanable)
   • in the wireframe the back link is shown with the text "back to list", in the acceptance criteria it is called "back to the list" - I know, very petty, but a match would be more appropriate

2. Acceptance criteria

   • everything clear, I just noticed a layout thing: You could indent subitems to the right by pressing the space bar twice to show them visually as subitems (here: the subitems from line 3)

3. Tasks

   • Two tasks are not sufficiently understandable for me: You mention a details component first and than a details page - do you create both and render the Details component on the details page or is it only a details page, where you include the jsx?
   • I told the same to the user story before: It could help to understand your tasks, when you use "`" to mark e.g. file names, component names etc. (for example:EmotionDetails` instead of details component")

[FelineHuhn]

Great improvement! The things with the layout and the example data in the wireframe are still the same as before, but that's fine for me if you prefer it that way.

🚀🚀🚀