glhkang / prfctpx Goto Github PK

Excellent work on your final docs, here are my notes:
BACKEND ROUTES

• You'll want a users index (/api/users) and a users show (/api/users/:id)
• Pluralize your photos routes

FRONTEND ROUTES AND COMPONENTS

• You could use the use the user's username for the route, but because in your state they'll be nested under their own Ids, it will be easier to use :userId instead of :username

Great work on your sample state, here are my only notes:

• Add a slice under entities for comments. Add commentIds arrays under photos and users
• Add an array of profilePhotos under users (to track photos on their profile page).
• Can archived (on photos) only exist in two states? If so, you should use a boolean for this (and should also change this to a boolean in your schema).

Excellent work so far! Here are my only notes:
MVP LIST
Looks perfect!

SCHEMA

• 500px photos include a location, so you should add that column to your photos table.
• If users can customize their own profile page, do you need a joins table tracking which photos a user has on their profile page?

Hi!
Took some design liberties to make it more aesthetically pleasing; was inspired by my splash page image.
Front end auth should be good to go. Also, I'm thinking about adding a footer (that'll include my personal links).
Thank you!