Wiki Page Home

• Is the first page you see upon entering the wiki
• Contains a welcome message
• Contains a link/placeholder for a link to the live page
• All links in the right sidebar should contain each wiki page and link to the correct page
• Correctly formatted
  • each wiki page is listed in bullet points
  • all links route the correct page

Comments

MVP List

• Should have 7 MVPs.
  • 3 of those are User Auth, Heroku, and Production README.
  • The other 4 are from the MVP List or they have clarified them with you
• Contains a description sentence of the app
• At least one CRUD feature, which states what CRUD operations are planned (creation, reading, updating, deletion)
• Estimates how long it will take the code each MVP
• Correctly formatted
  • MVPs are listed in an ordered list
  • Each MVP is broken down into bullet points

Comments

• Put user auth first on the MVP list so that you have something to host on Heroku
• Add these bullets to all of your MVPs
  • Adequate styling
  • Smooth, bug-free navigation
  • Adequate and appropriate seeds to demonstrate the feature
• Explicitly say which feature uses CRUD
• Format according to Bluebird
• Put your production README last

Database Schema

• Contains correct datatypes

• Contains appropriate constraints/details

  • primary key
  • not null
  • unique
  • indexed
  • foreign key

• Contains bullet points after the table that state which foreign keys will reference to which table, or references to the associations which will be made

• Correctly formatted

  • schema is written in a table format
  • the table's name are back_ticked
  • the table header column names are bolded
  • columns names are lowercased and snaked_cased and back_ticked

Comments

• Remove the associations page and just add bullets under each table for the associations
• Rename any foreign keys in the convention _id

Sample State

• State shape is flat!
• State's keys are camelCased
• All keys within the values in the state are accessible in the schema
• Correctly formatted
  • Sample state is rendered with triple backticks, and the language ```javascript...```). This will display the state as a code block instead of a giant line of text
  • Top level slices
    • entities
    • session
    • errors (here or in ui)
    • ui (if needed)
  • Should NOT have nested slices, aka comments inside of posts
    • Some info from other tables is ok, for instance:
      • the author username and imageurl for a post. basically any info that the user can't change
      • like count and a boolean on whether the user likes the post instead of a likes slice

Comments

Backend Routes

• Contains the following sections: HTML, API Endpoints(Backend)
• Each route has a description
• API Endpoint routes contains wildcard variables written in snake_case
• Routes does not contain superfluous routes
• Have API routes that will allow the front end to get all info it needs and does not have unneeded routes:
  • probably doesn't need a GET likes api endpoint because that info comes through the post show

Comments

Frontend Routes

• Frontend routes contains wildcard variables written in camelCase
• Correctly formatted
  • Routes are displayed with inline coding text (backticks) - missing this for your general

Comments

• Follow Bluebird formatting for the frontend routes/components.
• I think you may want to rethink your frontend routes. The main purpose of the frontend routes is to conditionally display different components, but I think you'll want to display channel index, message creation form, messages, user index, all on the same frontened route.

Good job, Elena! Address the unchecked items above, and then you're good to go!

User auth has:

• register (sign up)
• log in
• log out
• log in as demo user
• display errors on form submission
• displaying errors does not move around other elements
• clear errors on resubmit/moving between pages
• styling closely resembles actual site (for splash, login, & register pages)

Servers have:

Create: Users can create new servers
Read: Users can view a list of servers of which they are a member
Users must be logged in to view servers
Adequate styling
Smooth, bug-free navigation
Adequate and appropriate seeds to demonstrate the feature

Site is live at https://eris-chat.herokuapp.com