kloudysky / strife Goto Github PK

Styling-

• Placement and size of logout button
• Faster fade-in for forms
• Padding in input fields so there is a gap between typed characters and the left edge of the input field
• Errors should be better formatted. Doesn't have to perfectly match Discord, but should not be bullet points on top of the form

Functionality-

• Needs demo login
• Logout button doesn't work
• Errors should clear when switching between forms

MVPs-

• Include expected timeline for each MVP.
• Production README.md will come towards the end of the project.
• The term live chat includes text messaging. This will utilize websockets which we haven't taught in this course. Expect this to take a fair amount of time and it should be a separate MVP. It is also the core functionality of your application so you may want to prioritize this relatively early on in your .
• Voice, video chat, and screen sharing will all be bonus features and should come after direct messaging, which is also a bonus feature.

Schema-

• Include associations for each table in the bullet points listed beneath each table: has_many, belongs_to, has_many through

Sample State-

• I recommend to include any modals, drop downs, etc In your ui slice of state. React and redux give us a very easy when of rendering ui components.

Back-End Routes-

• Everything looks good!

Front-End Routes-

• We only need a new front-end route when rendering a new webpage. Once we're on the /servers page, each server and channel will be rendered as components on the /servers webpage. We do not need the /servers/:id front-end route or anything more complex than that.