CodeYourFuture / CodeYourFuture/Module-Data-Flows

TV Show Project Level 999: Stretch

Open
#480 1 comment 0 reactions 0 assignees View on GitHub
🏝️ Priority Stretch 📅 Sprint 3 Optional Submit:None
Dominant language
JavaScript
Stars
0
Forks
275
PR merge metrics
No merged PRs in 30d

Description

# Extra options

Do not do any of these until you have completed level 500!

Submit your Pull Request for level 500 first, and then work on these in a new branch for level 999.

Here are some ideas for consideration for further work:
1. Add cast listing to your show listing, http://api.tvmaze.com/shows/1?embed=cast
2. Add cast listing to your episode listing, http://api.tvmaze.com/shows/1?embed=cast
3. Allow clicking a cast member to present a view of all shows the person has appeared in http://api.tvmaze.com/people/1/castcredits
- Linking those back into your episodes view of each show.
4. Truncate long summaries and provide a "... read more..." control to reveal more.
5. Allow the user to choose to have the show list sorted by rating (highest rated shows first)
6. Have your search support start-of-word search, or other search types.
7. Make the browser's back and forward buttons navigate through your changed views (see [History.pushState()](https://developer.mozilla.org/en-US/docs/Web/API/History/pushState)).
8. Allow user to mark "favourite" shows
9. Allow user to store notes on each episode
10. Use local storage to cache the above, and perhaps also to cache episode lists
11. Paginate through results with a "load more" button - don't load 100s of episodes at a time.
12. Experiment with infinite scroll
13. Responsive design
14. Style your page to fit the theme of the show (colours, typography, background images, etc). Commit to one show to do this.

Contributor guide

No contributing guide indexed for this repository

Research direction

Complete level 500 first, then choose one of the listed enhancements in a new branch. Start by reviewing the relevant TVMaze endpoint or the History.pushState() documentation for the selected idea; done means the chosen enhancement works in the browser and its behavior is demonstrated.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.