List view

• MVP 1

  Think of how the main page should be structured. Use / build upon Charlotte's low-fidelity wireframe to help with this if needed. Mid-fidelity wireframe may be good to flesh-out the structure? At minimum, MVP 1 should have: A header (with our logo) A footer The main body, which includes a few rendered cards of the first 3-5 films in our dataset, and a search bar which acts as a form, and takes the user to another page that renders cards of films including the title the user typed in

  No due date

  •0/8 issues closed
  0% complete8 open0 closed

• MVP 0 COMPLETE

  In its current state, this current project creates API endpoints that follow CRUD (with the assistance of helper functions). It also has endpoints for query parameters, to be able to filter the data set for specific queries, e.g. filter by actor. The dataset is currently being stored in a JSON, hardcoded. The helper functions re-write this file. The way that ID is assigned to these films is bad, so come back and rethink. All requests have to be made through postman, there is no front end.

  No due date

  •0/4 issues closed
  0% complete4 open0 closed