Keepr is a social network that allows users to visually share, and discover new interests by posting (known as 'keeping' on Keepr) images or videos to their own or others' collections (i.e. a collection of 'vaults,' usually with a common theme) and browsing what other users have kept.
In this checkpoint students will demonstrate a working knowledge of building full-stack applications. They will utilize a VueJs frontend implementing the Vuex design and Vue-Router to manage the dom. On the server side students will use the DotNet WebApi for their server implementing the Repository pattern to communicate with the database. In addition students will use Auth0 for user management, dapper as an ORM and MySQL as their database.
Keepr is a typical project where some of the basic layouts have been thought up but it's still missing some key components. The basic idea here is to allow users to post items if they are logged in. They can also browse all of the items (aka keeps) that have been posted without having to login. If any user wants to store a reference to any paticular keep they will store it in the vault of their choice.
We want to give the users the opportunity to click on the keep icon for any post and have a list of their vaults appear. Selecting the vault should create a reference to that post and the users vault.
Vaults themselves are relatively simple... They only require a name and a description and will then have a list of posts that are saved within the vault. Think about how you will handle this relationship.
For example I may really like game art and thus I would be a user who creates a vault named Sweet Game Art I will then start saving the keeps I like into this vault.
To get started you are going to need to create some models and think about the necessary relationships. Draw these out before you start coding.
The main goal here is to get users logging in and creating public posts (keeps). Once you are creating keeps you should be able to tackle the rest of the application.
Users will be allowed to create vaults where they can organize the posts of other users so they can recall the keeps they enjoy by looking at that paticular vault.
Remember that a single user can have many vaults but each vault will only belong to a single user. Due to the privacy of our users Vaults may only be retrieved by the user who created the vault.
Also a vault has many keeps and keeps could have many vaults but only one author or user...
Also to make things more simplistic once a keep is marked public it can no longer be deleted.
Once you get to the point where users can create vaults its time to put them to work. Users need a simple way to add a paticular keep to the vault of their choice while browsing. Also to give users some credit for creating excellent keeps lets keep track of the number of times a keep has been added to any vault. We also want to keep track of the number of views each keep gets.
What this site is already pretty if you follow the mocks 😉 Make sure the features you add are attractive.
- Keeps should be tagged. Make the site better by implementing a search filter.
- Write a few tests for your components.
- When a user clicks the share icon they should be able to post that share to the various social medias (Facebook, Twitter, ect)
- Visitors can see all public keeps (login not required)
- Keeps are displayed in a card like format with all data rendered
- Users have a dashboard route to see all their keeps and vaults
- Users can only see vaults they created
- Users can View all the keeps in a given vault
- Anytime a
keepiskept in a vaultthe relevant count should go up
-
Users can:
-
Register, login and be automatically logged on page refresh
-
Create and Delete Keeps
-
Create and Delete Vaults
-
Only Delete things they created
-
Add Keeps to Vaults
-
Remove Keeps from Vaults
Make sure you test it. When You are finished submit your project to the gradebook and notify your instructor
