• Retrieve data
• Create a list with data
• Create link between tracks and albums
• Design track page

As a software Developer,
I want to create diagrams for the frontend,
So I have a visualization of the frontend

We need to create some (UML) diagrams to visualize the user interaction with the application and it's capabilities.

As a software Developer,
I want to search for data sources of albums and tracks,
So I can use them for this application.

As a customer,
I want to see general information about the company,
So I know who I'm dealing with.

As a software developer,
I want to have a tool that fills the database,
so we have data in our database.

As a software developer,
I want a sample Apollo implemented,
so I can send queries.

Ik ben hier voor het laatst gebleven:
https://www.apollographql.com/docs/react/essentials/get-started.html#request

As the developer team,
we want every member to practice by creating a page with react,
so they learn how to work with react.

As a software Developer,
I want to create diagrams for the database,
So I can see the structure of the database.

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Provide an User Story
As an ___ I would like to ___ to achieve ___ .

Is your feature request related to a problem? Please describe.
I hate it when I can't find things.

Describe the solution you'd like
I want to search and find what I'm looking for.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
n.d.

Additional context
n.d.

Provide an User Story
As an User I would like to be able to search to easily find products, albums and tracks.

See https://github.com/graphql-dotnet/authorization

As an admin I would like to have a dashboard to be able to mutate data and view various webshop statistics.

• Create an admin dashboard for the front end
• Display a link to the dashboard when logged in as admin
• Write CRUD (Create, Remove, Update, Delete) functions
• Determine and choose appriopiate graphs for visualising webshop data.
• Link graphs to dummy data
• Link graphs to real time webshop data

https://github.com/graphql-dotnet/authorization

• We should be able to selectively exclude our users from accessing certain data.
• We should be able to include certain data based on the logged in user (e.g. my bought products)

As a customer,
I want to be able to contact the company,
so if I have trouble with anything shop-related, I can ask the company for help.

We are currently (on 17/10/2018) using Material UI as our UI library, this works well, but it gives the application more of a functional feel to it, like a web application, rather than a webshop.

It seems that Semantic UI provides a more wide variety of styling choices than Material UI does, so this might be a candidate to replace Material UI with.

See https://react.semantic-ui.com/

Provide a User Story
As a user I would like to add products (albums and songs) to a shopping cart to be able to buy these from the site at the checkout step.

Bug description:
Some artists are duplicated, with one copy containing no albums and/or tracks. These must be deleted.

As a user I would like to have a registration form to create my own user account, so that I can order products faster and view my order history.

• Create a registration form

As a customer,
I want to get a confirmation email,
so I know the status of my orders.

• Tracks in an album should have an order.
• An order should contain the ordered products, not the invoice.
  EDIT:
• A new entity Genre should be added to the datamodel.

Originally posted by @elertan in https://github.com/elertan/project-c-webshop/issue_comments#issuecomment-427692707

As a software Developer,
I want to create a layout with a storyboard,
so i can show the apps life cycles.

Create a page with all the genres available.

As a software Developer,
I want to have the ERD completed,
So we have the structure of the data in the database.

The artist page is split up in multiple tasks :

• Read the data with GraphQl
• Display the data on screen
• Put the different artists in a grid
• Redirect user to another page when the user clicks on an artist
• Design the artist page

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Provide an User Story
As an ___ I would like to ___ to achieve ___ .

At the time of creating this issue, a local page was already developed on branch 'robrecht'. This page is functional and only contains a sample text.

Before creating an actual Genre page, we must first specify the available music categories in our project.

Then we must specify what is displayed after selecting a genre, for example: all artists that fit the genre, or display only albums for that genre?

• Display a sample page
• Determine the display of implementation
• Add relevant data to Database
• Display albums and artists based on selected category.

https://github.com/SimonCropp/GraphQL.EntityFramework

As a software Deveoloper,
I want to create basic GraphQL schemas,
So I can visualise how the code works.

As software developer,
we want to have a base structure in place,
so it can guide the less experienced software developers in the right direction.

As of right now we have created an AlbumGrid component that shows AlbumCovers in a grid layout.
But it seems that we require this layout for more than just Albums, such as Genres.

This means we should extract the current code from the AlbumGrid component and create a generic GridView component, which will just take a set of JSX.Element (JSX.Element[]) and show it in a grid layout.

Because there is not a working payment system yet, i would like to create a payment system by reusing the change payment details from the user dashboard.

• - Create payment page.
• - Create payment page content.
• - Create connection between email system and payment page.
• - Create ordersuccesfull page.
• - Redirect to Order succesfull page .

Userstory
As an user I would like to be able to pay my order and receive a confirmation email after it.

As a software Developer,
I want to think of a few new features,
So we can propose them to the product owner.

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Provide an User Story
As an ___ I would like to ___ to achieve ___ .