Instructor Notes

[bartdorsey]

• Include a user story about user registration and user login
• Consider either making 'likes' a bonus story or making the viewing of a user's likes a main feature. In other words, if a user can like the articles for the purpose of keeping track of favorites they should be able to view those favorites
• Consider a feature of a User Profile page to contain things like the likes and stories of a user or author.
• You should decide if you want to let the users edit a page using a rich text editor, or if you will use something like Markdown for users to write their stories. (Markdown could be implemented more quickly and you could make the rich text editor a bonus feature) Markdown also supports code blocks, links and images (with urls from elsewhere on the web) natively so that might make those features easier to implement.
• Consider combining the roles of author and user. From your feature list, it doesn't appear that they have many differences.

[ianmagenta]

Thanks for the comments, Bart! We've gone through and implemented the above suggestions. If for some reason you don't think we've implemented any of these properly, please feel free to let us know!

[bartdorsey]

Your feature packet is looking great, thanks for implementing some of our notes. Here are some more notes about your endpoints and models.

Endpoints:

• Do you have a front endpoint that displays recent stories?

Models:

• Your model names should be singular (table names should be plural, maybe you can list both)
• Your password field should not be a varchar 20 because you need to store a bcrypt hash in there.
• You can setup a unique constraint on the StoryLikes and CommentLikes tables to make it so that a user can only like a single story or comment. https://sequelize.org/master/class/lib/query-interface.js~QueryInterface.html#instance-method-addConstraint
• If you setup this constraint you do not need the likes integer field on comments and stories because you can simply count the number of likes in the appropriate like table.
• you should probably just use the updatedAt column directly instead of using a date column, I'm unsure what you mean by read val from updatedAt.
• For comments and stories you might want to use createdAt instead of updatedAt for the date, as changing a comment or story might change the order it sorts on the views where lists of stories appear.

[ianmagenta]

Thanks again for the feedback, Bart! We've gone ahead and implemented these changes.