snapics's People
snapics's Issues
PA:REVIEW User Authentication
- Users can sign up, sign in, log out
- Users can use a demo login to try the site
- Users can't use certain features without logging in (create comment & albums)
Wiki Home Page
- 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
PA:REVIEW Photos index page, upload form and show page
- Logged in Users can upload photos
- Users can view list of Photos
- Users can press on a photo to view the photo in a larger size
DB 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
PA:REVIEW Albums
- Logged in Users can create an album
- Logged in Users can add photos to an album
- Users can view other users photo albums
PA:REVIEW User Authentication
- Users can sign up, sign in, log out
- Users can use a demo login to try the site
- Users can't use certain features without logging in (create comment & albums)
Wire Frames and Component Hierarchy
- All routes listed in the routes wiki page is also listed in the component hierarchy
- Each component, if necessary, has route, state, and other components it renders example
- Necessary components are wrapped in a container
- Correctly formatted
- Bullet point hierarchy
- Component names are displayed with
inline coding text
(backticks)
- Wireframes included
- Every component listed in the component hierarchy wiki page has at least one wireframe
- Every MVPs listed on the MVP wiki page has at least one wireframe
- Every route listed on the route wiki page has at least one wireframe
- Contains Containers
- Contains Lists
- Contains ListItems
- Correctly formatted
- Wireframe images display on the page
- Every wireframe has a header title
PA:REVIEW comments
- Logged in users can comment on a photo
- the comments count is display on each photo
Sample State Shape
- State shape is flat!
- State's keys are camelCased
- All keys within the values in the state are accessible in the schema (Ex: if you create a
img_url
key in the state, make sure your database also has a column that contains animg_url
) - Correctly formatted
- Sample state is rendered with 3 back ticks before and after. This will display the state as a code block instead of a giant line of text
- Top level slices
-
entities
-
session
-
errors
(here or inui
) -
ui
(if needed)
-
- Should NOT have nested slices, aka
comments
inside ofposts
- 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
- Some info from other tables is ok, for instance:
MVP List
- Should have 7 MVPs.
- 3 of those are User Auth, Heroku, and Production README.
- The other 4 are from the MVP List
- 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
login | logout form close
the login | sign up form should be closed when user click outside of the form
Routes
- Routes accurately reflect MVPs and Component Hierarchy
- Covers the frontend functionality of the site through routes that match to the wireframes
- Contains the following sections: HTML, API Endpoints(Backend), and Frontend Routes
- Each route has a description
- API Endpoint routes contains wildcard variables written in
snake_case
- Frontend routes contains wildcard variables written in
camelCase
- 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 bc that info comes through the post show
- probably doesn't need a
- Correctly formatted
- Routes are displayed with
inline coding text
(backticks)
- Routes are displayed with
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. ๐๐๐
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google โค๏ธ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.