Submitted by: Jackson Seifferly
Estimated time spent: 20 hours spent in total
Deployed Application (required): [https://flixster-bs8p.onrender.com/]
- Display Movies
- Users can view a list of current movies from The Movie Database API in a grid view.
- Movie tiles should be reasonably sized (at least 6 playlists on your laptop when full screen; large enough that the playlist components detailed in the next feature are legible).
- For each movie displayed, users can see the movie's:
- Title
- Poster image
- Vote average
- Users can load more current movies by clicking a button which adds more movies to the grid without reloading the entire page.
- Users can view a list of current movies from The Movie Database API in a grid view.
- Search Functionality
- Users can use a search bar to search for movies by title.
- The search bar should include:
- Text input field
- Submit/Search button
- Clear button
- Movies with a title containing the search query in the text input field are displayed in a grid view when the user either:
- Presses the Enter key
- Clicks the Submit/Search button
- Users can click the Clear button. When clicked:
- Most recent search results are cleared from the text input field and the grid view and all current movies are displayed in a grid view
- Design Features
- Website implements all of the following accessibility features:
- Semantic HTML
- Color contrast
- Alt text for images
- Website implements responsive web design.
- Uses CSS Flexbox or CSS Grid
- Movie tiles and images shrink/grow in response to window size
- Users can click on a movie tile to view more details about a movie in a pop-up modal.
- The pop-up window is centered in the screen and does not occupy the entire screen.
- The pop-up window has a shadow to show that it is a pop-up and appears floating on the screen.
- The backdrop of the pop-up appears darker or in a different shade than before. including:
- The pop-up displays additional details about the moving including:
- Runtime in minutes
- Backdrop poster
- Release date
- Genres
- An overview
- Users can use a drop-down menu to sort movies.
- Drop-down allows movies to be sorted by:
- Title (alphabetic, A-Z)
- Release date (chronologically, most recent to oldest)
- Vote average (descending, highest to lowest)
- When a sort option is clicked, movies display in a grid according to selected criterion.
- Drop-down allows movies to be sorted by:
- Website displays:
- Header section
- Banner section
- Search bar
- Movie grid
- Footer section
- VIDEO WALKTHROUGH SPECIAL INSTRUCTIONS: To ease the grading process, please use the color contrast checker to demonstrate to the grading team that text and background colors on your website have appropriate contrast. The Contrast Ratio should be above 4.5:1 and should have a green box surrounding it.
- Deployment
- Website is deployed via Render.
- VIDEO WALKTHROUGH SPECIAL INSTRUCTIONS: For ease of grading, please use the deployed version of your website when creating your walkthrough.
- Website implements all of the following accessibility features:
- Embedded Movie Trailers
- Within the pop-up modal displaying a movie's details, the movie trailer is viewable. -[x] When the trailer is clicked, users can play the movie trailer.
- Favorite Button
- For each movie displayed, users can favorite the movie.
- There should be visual element (such as a heart icon) on each movie's tile to show whether or not the movie has been favorited.
- If the movie is not favorited:
- Clicking on the visual element should mark the movie as favorited
- There should be visual feedback (such as the heart turning a different color) to show that the movie has been favorited by the user.
- If the movie is already favorited:
- Clicking on the visual element should mark the movie as not favorited.
- There should be visual feedback (such as the heart turning a different color) to show that the movie has been unfavorited.
- Watched Checkbox
- For each movie displayed, users can mark the movie as watched.
- There should be visual element (such as an eye icon) on each movie's tile to show whether or not the movie has been watched.
- If the movie has not been watched:
- Clicking on the visual element should mark the movie as watched
- There should be visual feedback (such as the eye turning a different color) to show that the movie has been watched by the user.
- If the movie is already watched:
- Clicking on the visual element should mark the movie as not watched.
- There should be visual feedback (such as the eye turning a different color) to show that the movie has not been watched.
- Sidebar
- The website includes a side navigation bar.
- The sidebar has three pages:
- Home
- Favorites
- Watched
- The Home page displays all current movies in a grid view, the search bar, and the sort movies drop-down.
- The Favorites page displays all favorited movies in a grid view.
- The Watched page displays all watched movies in a grid view.
[(https://www.loom.com/share/c29c8d99c6b341ce9b32ac4571128836?sid=e821737c-e09b-48e1-9be8-35ce3c17b324)]
- Did the topics discussed in your labs prepare you to complete the assignment? Be specific, which features in your weekly assignment did you feel unprepared to complete?
I felt that almost all of the features that we had to implement in the project were covered by ideas in the labs, I found myself constantly looking back at past labs to refrence code I wrote there for my project. The only thing I felt a little unprepared for was the video embedding but with a bit of web searching it was actually relativly simple to implement.
- If you had more time, what would you have done differently? Would you have added additional features? Changed the way your project responded to a particular event, etc.
If I had more time I wish I could add more features to the site, maybe a list of theaters in the area playing the movie for each movie. And maybe some more filtering options for the type of search you can perform, like search for movies within a particular year or by rating.
- Reflect on your project demo, what went well? Were there things that maybe didn't go as planned? Did you notice something that your peer did that you would like to try next time?
Talking with my peers a big thing I noticed was that a lot of people started the project by implementing some of the smaller features that were less code intensive which helped them quickly understand the layout of their project and how components would communicate with each other. I started with one of the bigger features which required a lot of inter-connected components which made it hard initially to figure out how the app features would communicate.
- Add any links to open-source libraries used in your project.
Give a shout out to somebody from your cohort that especially helped you during your project. This can be a fellow peer, instructor, TA, mentor, etc.
-
First shout out to bravemaster619 at [https://dev.to/bravemaster619/simplest-way-to-embed-a-youtube-video-in-your-react-app-3bk2] for his very good guide on embedding youtube video saved me a lot of headache
-
Shout out to my table mates again Ben, Kevin, and Thomas who all helped me bounce ideas of them and compare our features.