TV Show Project Level 500: Build a front page

Open
#479 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
frontend

Research direction

Start with README.md for the repository's submission instructions, then review the original codebase and the level 500 requirements. The work is done when the shows listing, show search, navigation, episode controls, and one-fetch-per-URL behavior all work together and the required partner-reviewed pull request is ready.

Written by the indexing model from the issue text.

Description

🏕 Priority Mandatory 📅 Sprint 3 Core Submit:None

Level 500

For level 500, you should switch back to your original codebase.

You should have reviewed and merged someone else's level 400 implementation.

Once again, compare their implementation to yours. Think:

  1. How is it different?
  2. What do you prefer about your implementation?
  3. What do you prefer about their implementation?
  4. What did you learn that you didn't know before?

Have a discussion about your answers to these questions. In class, together you should give a 3 minute talk about your conclusions.

Refactoring

Feel free to change anything in your codebase which you think will make it easier to work with, or to build new features.

Make a branch and pull request for yourself, and then have your partner review, making sure they understand the changes made.

Adding new functionality

Level 500 is about adding a front-page which lets users select (and find) shows from your shows list.

Requirements
  1. When your app starts, present a listing of all shows ("shows listing")
    1. For each show, you must display at least name, image, summary, genres, status, rating, and runtime.
  2. When a show name is clicked, your app should:
    1. Fetch and present episodes from that show (enabling episode search and selection as before)
    2. Hide the "shows listing" view
  3. Add a navigation link to enable the user to return to the "shows listing"
    1. When this is clicked, the episodes listing should be hidden
  4. Provide a free-text show search through show names, genres, and summary texts
  5. Ensure that your episode search and episode selector controls still work correctly when you switch from shows listing to episodes listing and back
  6. During one user's visit to your website, you should never fetch any URL more than once.
Screenshot of minimal version

Note: Provided your project meets the above requirements, it can look however you want.

Here is one example layout.

Screenshot of a website with a drop-down list with the show "Breaking Bad" selected

Submission

Once you have finished your level 500 it is ready to submit.

Check the README.md for this repo for instructions.

Dominant language
JavaScript
Stars
0
Forks
276
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CodeYourFuture/Module-Data-Flows

All issues in CodeYourFuture/Module-Data-Flows

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.