al6 / diskord Goto Github PK

• Add column to guild for invitation code

• If they are going to be called guilds, call them guilds consistently - including in your schema, otherwise call them servers everywhere. You can do either just make sure that you keep continuity in naming
• Lets talk about how you will you keep track of who is inside v. admining each server next week
• Excellent work!

• What is user data? the backend route should just return user information, then you can format that information to include additional info if you would like - so GET to api/users or GET api/users/:id
• Lets talk about backend route to join a guild.
• Add in backend routes for channel information

• Add in time estimates for each MVP
• Users should be able to delete their own servers
• Users can create and delete channels
• Add a production read me to MVP List (should be last MVP)

• Great job

• Will you add people to guilds/servers through friendships?
• Make a note in MVP list that guilds are servers
• Lets chat on Monday about direct messages table

Hi Albert,
please make app.json file to easy deploy on heroku & if its possible mke changes to use backblaze b2 as amazon s3 because so cheapest:
https://www.backblaze.com/b2/cloud-storage-pricing.html
waiting for your response
finest regards

• Images are not showing up
• Footer should not have dead links - edit footer to just have links to professional social media
• Header should also not have dead links - make sure that if there is a button it goes somewhere, or omit it
• Error messages should be above each line they correspond with, rather than all listed at the top of the form
• Make sure email inputs are type="email"
• Make words on home page larger

• Nice work with pictures!
• Lets meet about messages again tomorrow
• Logout/something should be visible when you click "home"
• Add DMs