ABCDEF
1
4 (Exemplary)3 (Minimum Project Requirements)2 (Needs Improvement)1 (Unsatisfactory)0 (Incomplete)
2
DatabaseHas a database with at least 4 tables or models. (e.g. Users, Posts, Comments, Likes)Has a database with a Users table and at least 2 additional tables. (e.g. Users, Posts, and Comments).

Aim to have one primary resource (posts) and one secondary resource (comments). A primary resource is something created by a user. A secondary resource is something created by user that references a primary resource.		Has a database with a Users table and one other table (e.g. Users and Posts)Has a database with only 1 tableHas no database
3
ServerHas full CRUD capabilities for most or all models/tables. User authentication and authorization is required for at least 1 modelCan read and create data for all models/tables; Can update and delete data from at least one model/tableCan read data from all models and can create data for some models/tablesCan read data from all models/tablesHas no backend
4
FrontendFront-end has more than one client-side route and displays multiple resources.

Users can create accounts and log-in. Users can create, update, and delete resources with intuitive user interfaces.

React features are used effectively including state, effects, routing, context, controlled forms.

Correct semantic elements are always used. Components and pages are organized in a logical manner.		Front-end has more than one client-side route and displays multiple resources.

User can create accounts and log-in. Users can create, update, and delete resources.

React features are used effectively including state, effects, routing, context, controlled forms.		Front-end has more than one client-side route and displays multiple resources.

User can create accounts and log-in. Users can create, update, and delete resources. React features are used effectively including state, effects, routing, context, controlled forms.		Front-end has 1 client-side route (Landing Page).Has no frontend
5
StylesThe site has almost universal polish. It actively designed to be aesthetically pleasing.

The folowing items are true:
- Color contrast never drops below AA standards,
- At least 2 separate instances of animations have been used,
- Main site navigation is clear and obviously distinct from other elements,
- None of said animations individually take longer than 1 second (ideally less)
- Accessibility (A11y) features (e.g. keyboard focus) are not disrupted by styles
- A page never has more than a primary, secondary, highlight, black, white, and gray colors,
- Basic color theory has been applied when choosing site colors,
- The site uses a custom font, but never more than 3 fonts in the main content,
- All links are visually distinct from surrounding text and change appearance on hover and click

In addition we may even see:
- A light and dark mode,
- Any continous animation can be disabled by user
- A scroll effect exists,
- Overflow text fades out or is trucated (example -> exa...)
NOTE: A CSS library like Bootstrap or Tailwind is NOT required. They can certainly help achieve the results below but building with your own CSS can also achieve the same result (and can deepen your understanding/mastery of CSS!)

The site has coherent static styles and the following items are true:
- Across the site it is clear that it has a primary and secondary color,
- 1 or more instances of properly formatted collections (with Grid/Flexbox),
- Both a mobile and desktop view exist.
- Though one of view is less polished, neither one has overflow or spacing issues.
- A basic navigation option is available in both views
The site has consistent, but basic styles. It has only a desktop view, and when switching to mobile spacing and overflow issues are obvious.Despite using a library, the styles are basic. Only rudimentary padding, margin, display, color,and size attributes have been applied.Project does not use a CSS Library or Framework and has no styling applied.