User Story - Button-Component

[Nesssaaa]

Value proposition

As a user I want to see buttons for later function: "keep learning/ kann ich☑️" "mastered/ kann ich🔄", "edit 🖊️", "delete ❌" So I can click on them at the moment

Description

Acceptance criteria

• [ ] For now, we see for buttons under every card on the homescreen
• [ ] The buttons are clickable

  Tasks

• [ ] Create Button-Component with button styling
• [ ] Create ButtonNavBar-Component with flexbox-styling, where you return 4 buttons
• [ ] Return ButtonNavBar in CardList-Component within the div under the CardContainer
• [ ] Style the div in the CardList-Component as a styled.div with flexbox

[MerleMak]

This unfortunately doesn't count as a user story, as the button component doesn't have its own functionality. Creating the button component would rather be part of the edit or delete user story as a tasks.

When you add the buttons for keep learning / mastered, you already need to write all the logic for this mechanism :)

[MerleMak]

you can rewrite this user story to something like this:

Progress categories

Value proposition

As a user I want to categorize my cards into two buckets: "keep learning" and "mastered" So I can repeat my weaker vocabulary more regularly

Acceptance criteria

• Every card includes two buttons for "keep learning" and for "mastered"
• When the button "keep learning" is clicked, the card turns around again so the solution is not displayed anymore
• when the button "mastered is clicked the card is moved to the bottom of the list and also turns around

Tasks

• Call the Button-Component on each card with the according props
• write handleMastered function which includes a state of an Array of Objects containing all mastered cards
• write handleKeepLearning function witch includes includes the logic to turn the card back again

Somthing like this but make it your own :)