Well done on your schema! Note that wireframes and component hierarchy are not needed, so focus on finishing up your backend routes, frontend routes/components and sample state. Let me know if you have any questions!
Wiki Page Home
[x] Is the first page you see upon entering the wiki
[x] Contains a welcome message
[x] Contains a link/placeholder for a link to the live page
[x] All links in the right sidebar should contain each wiki page and link to the correct page
[x] Correctly formatted
[x] each wiki page is listed in bullet points
[x] all links route the correct page
Comments:
Routes links to Create a new page
Wireframes not needed
Component Hierarchy not needed
MVP List
[x] Should have 7 MVPs.
[x] 3 of those are User Auth, Heroku, and Production README.
[x] The other 4 are from the MVP List or they have clarified them with you
[x] Contains a description sentence of the app
[x] At least one CRUD feature, which states what CRUD operations are planned (creation, reading, updating, deletion)
[x] Estimates how long it will take the code each MVP
[x] Correctly formatted
[x] MVPs are listed in an ordered list
[x] Each MVP is broken down into bullet points
Comments:
MVP descriptions should be more detaied (CRUD operations, what they are, how users use these features)
Are the dates listed your expected due dates? (Asking because the last day on there is 8/16, but project is due 8/17)
Database Schema
[x] Contains correct datatypes
[x] Contains appropriate constraints/details
[x] primary key
[x] not null
[x] unique
[x] indexed
[x] foreign key
[x] 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
[x] Correctly formatted
[x] schema is written in a table format
[x] the table's name are back_ticked
[x] the table header column names are bolded
[x] columns names are lowercased and snaked_cased and back_ticked
Comments:
Remove/make sure to update [Insert working title here]
You’ll be using ActiveStorage for handling storing images; no need for the image column.
I wouldn't worry about board admins at this point; finish all the MVPs first and then you can add this as a bonus.
Card memberships might be unnecessary. Even though trello cards have a membership field, they also belong to a list, which belongs to a board, where you can get the membership from the board itself.
I wouldn't worry about labels as an MVP.
Routes
[x] Routes accurately reflect MVPs
[x] Covers the frontend functionality of the site
[x] Each route has a description
[x] API Endpoint routes contains wildcard variables written in snake_case
[x] Frontend routes contains wildcard variables written in camelCase
[x] 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 bc that info comes through the post show
[x] Correctly formatted
[x] Routes are displayed with inline coding text (backticks)
Comments:
Sample State
[x] State shape is flat!
[x] State's keys are camelCased
[x] All keys within the values in the state are accessible in the schema (Ex: if you create a imgUrl key in the state, make sure your database also has a column that contains an img_url)
[x] Correctly formatted
[x] 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
[x] Top level slices
[x] entities
[x] session
[x] errors (here or in ui)
[x] ui (if needed)
[x] 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
Trello Feedback
Well done on your schema! Note that wireframes and component hierarchy are not needed, so focus on finishing up your backend routes, frontend routes/components and sample state. Let me know if you have any questions!
Wiki Page Home
Comments:
Routeslinks toCreate a new pageWireframesnot neededComponent Hierarchynot neededMVP List
Comments:
Database Schema
[x] Contains correct datatypes
[x] Contains appropriate constraints/details
[x] 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
[x] Correctly formatted
back_tickedback_tickedComments:
[Insert working title here]Routes
snake_casecamelCaseGET likesapi endpoint bc that info comes through the post showinline coding text(backticks)Comments:
Sample State
imgUrlkey in the state, make sure your database also has a column that contains animg_url)```javascript...```). This will display the state as a code block instead of a giant line of textentitiessessionerrors(here or inui)ui(if needed)commentsinside ofpostsComments: