From a8655fba6b01900acfbcbd2c5aa55edcf025e9cf Mon Sep 17 00:00:00 2001
From: l <l>
Date: Wed, 18 Mar 2026 10:58:04 +0000
Subject: [PATCH 1/8] add name

---
 index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/index.html b/index.html
index 9a400d1..7ae1e1d 100644
--- a/index.html
+++ b/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
-    <title>TV Show Project | My Name (My GitHub username)</title>
+    <title>TV Show Project | LonMcGregor</title>
     <link href="style.css" rel="stylesheet" />
     <link rel="icon" href="/favicon.ico" type="image/x-icon" />
   </head>

From 53b38ef34f8b872dd22cda497f9f627e3514bcc9 Mon Sep 17 00:00:00 2001
From: l <l>
Date: Wed, 18 Mar 2026 11:29:52 +0000
Subject: [PATCH 2/8] impl level 100

---
 index.html |  2 ++
 script.js  | 12 ++++++++++++
 2 files changed, 14 insertions(+)

diff --git a/index.html b/index.html
index 7ae1e1d..b479905 100644
--- a/index.html
+++ b/index.html
@@ -17,5 +17,7 @@
 
     <!-- Loads YOUR javascript code -->
     <script src="script.js"></script>
+
+    <footer>Data from TVMaze. <a href="https://www.tvmaze.com/api#licensing">Use of the TVmaze API is licensed by CC BY-SA</a>. This means the data can freely be used for any purpose, as long as TVmaze is properly credited as source and your usage complies with the ShareAlike provision. You can satisfy the attribution requirement by linking back to TVmaze from within your application or website, for example using the URLs available in the API.
   </body>
 </html>
diff --git a/script.js b/script.js
index 87a7de8..29be7f0 100644
--- a/script.js
+++ b/script.js
@@ -7,6 +7,18 @@ function setup() {
 function makePageForEpisodes(episodeList) {
   const rootElem = document.getElementById("root");
   rootElem.textContent = `Got ${episodeList.length} episode(s)`;
+  for(let ep of episodeList){
+    document.writeln(`<article>
+    <h1>S${ep.season.toString().padStart(2,"0")} - E${ep.number.toString().padStart(2,"0")}
+    <h2>${ep.name}</h2>
+    <img src="${ep.image.medium}" />
+    <details>
+    <summary>blurb</summary>
+    ${ep.summary}
+    </details>
+    </article>`)
+  }
 }
 
+
 window.onload = setup;

From fd6d2c9c569c7fce2e52611b3bd23cd3fd7d5f23 Mon Sep 17 00:00:00 2001
From: l <l>
Date: Wed, 29 Apr 2026 11:07:51 +0100
Subject: [PATCH 3/8] update requirements

---
 levels/Reviewers-All-Requirements.md | 51 ++++++++++++++++++++++++++++
 readme.md                            | 26 ++++++++++++++
 2 files changed, 77 insertions(+)
 create mode 100644 levels/Reviewers-All-Requirements.md

diff --git a/levels/Reviewers-All-Requirements.md b/levels/Reviewers-All-Requirements.md
new file mode 100644
index 0000000..5710725
--- /dev/null
+++ b/levels/Reviewers-All-Requirements.md
@@ -0,0 +1,51 @@
+There are the main requirements that a submitted project needs checked by reviewers.
+Trainees should **not** need to refer to this document, and should focus on completing each level one at a time.
+
+1. It is deployed on GitHub pages
+1. The site must fetch data from an API at `TVMaze.com`, **not** a JSON file
+	1. The page should state somewhere that the data has (originally) come from [TVMaze.com](https://tvmaze.com/), and link back to that site. 
+	1. During a visit to the website it should never fetch any URL more than once.
+	1. The site should indicate when data is loading.
+	1. If an error occurred loading the data, notify the user on the page (not only in the console)
+1. Listing Shows - When the site starts, present a listing of all shows ("shows listing")
+	1. For each show, display at least:
+		1. name
+		1. image
+		1. summary
+		1. genres
+		1. status
+		1. rating
+		1. runtime
+	1. When a show name is clicked, it should:
+		1. Fetch and present episodes from that show
+		1. Hide the "shows listing" view
+		1. Enable episode search / select (see below)
+	1. Have a navigation link or button to enable the user to return to the "shows listing"
+		1. When this is clicked, the episodes listing should be hidden
+	1. Ensure that the search and selector controls still work correctly when you switch from shows listing to episodes listing and back
+1. Listing Episodes - When a show is selected, all episodes must be on the page shown for that given show, with at least:
+	1. The name of the episode
+	1. The combined season number and episode number into a zero-padded episode code: `S02E07` is correct, `S2E7` is incorrect.
+	1. The medium-sized image for the episode
+	1. The summary text of the episode
+1. Select Shows - a `select` element to your page so the user can choose a show.
+	1. When the user first loads the page, use the `fetch`ed list of available shows, and add an entry to the drop-down per show.
+	1. When a user selects a show, display the episodes for that show after `fetch`ing the episode list.
+	1. The select must list shows in alphabetical order, case-insensitive.
+1. Select Episodes - a `select` drop-down which lets the user jump quickly to a particular episode:
+	1. The select options are updated whenever a new show is selected, and this select isn't used otherwise
+	1. The select input should list all episodes in the format: "S01E01 - Episode Title"
+	1. When the user makes a selection, they should be taken directly to that episode on the page
+1. Search Shows - When a user types a search term into the search box:
+	1. Only shows whose summary **OR** name contains the search term should be displayed
+	1. The search should be case-**in**sensitive
+	1. The display should update **immediately** after each keystroke changes the input
+	1. Display how many shows match the current search
+	1. If the search box is cleared, **all** shows should be shown
+1. Search Episodes - When a user types a search term into the search box:
+	1. Only episodes whose summary **OR** name contains the search term should be displayed
+	1. The search should be case-**in**sensitive
+	1. The display should update **immediately** after each keystroke changes the input
+	1. Display how many episodes match the current search
+	1. If the search box is cleared, **all** episodes should be shown
+  
diff --git a/readme.md b/readme.md
index a65a311..379c3bc 100644
--- a/readme.md
+++ b/readme.md
@@ -85,3 +85,29 @@ After that, you're going to swap codebases with someone else. You should complet
 You are allowed to change anything in your partner's code to make it easier to understand or build on, but they must understand and accept your changes.
 
 Remember, finish each level before you move on to the next. Reach out for help when you're stuck.
+
+## Submission
+
+When you are ready to submit this task, you will submit it in a different way to normal.
+Instead of using PRs, you will deploy your TV project website to GitHub pages and reviewers will assess it live, check the code, and leave issues for you to fix if there are any problems.
+
+When you have finished level 500:
+1. Go to the Portal and fill out the submission step for the TV Project. Include a link to the deployed page, and the branch where you finished level 500.
+2. A reviewer will check your project and leave issues on your repository.
+3. Resolve the issues, and check that the reviewer is happy the problems are resolved. The reviewer will close the issues when they are happy they are fixed.
+4. Once all issues raised are fixed and closed, your TV project is fully submitted.
+
+### Instructions for Reviewers
+**Requirements**
+If this is your first review of the TV show project, familiarise yourself with the task requirements.
+You will review features that are present in level 500, which includes some requirements from prior levels.
+For your convenience, you can find a list of all the requirements [here](levels/Reviewers-All-Requirements.md).
+There are no rules about how the site should look, only how it behaves.
+
+**How to review**
+Submission is not done via a pull request, instead any issues you find should be raised as issues.
+You can choose whatever is easiest - given there may be multiple issues, grouping them into issues by related themes may be best, but use your own judgement.
+The trainee will deal with the issues and should check in replying to these issues.
+Check any changes made, and if all problems are resolved, you can close the issue.
+You may wish to double-check your notification settings to make sure you are notified for any replies or activity on these issues.
+When allthe issues you opened are closed, the task is considered "complete".

From a8baf364bd4ed055ed2b8426e41c4c6c4591e1ba Mon Sep 17 00:00:00 2001
From: l <l>
Date: Wed, 29 Apr 2026 11:09:01 +0100
Subject: [PATCH 4/8] spellcheck

---
 readme.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/readme.md b/readme.md
index 379c3bc..1be2c20 100644
--- a/readme.md
+++ b/readme.md
@@ -4,7 +4,7 @@ One of the most powerful things a software engineer can do is take some data and
 
 The aim of this project is to take some data someone else has (and exposes over an API), and display it to users. The data we're using for this project is about episodes of TV shows.
 
-This project will take you multiple weeks to complete. As always, we will break down the project into levels we can deliver incrementally. You must finish each milestone before you start working on the next one (but it's ok to know what the future levels are going to be - it may help you design things). Your goal is to complete all of the levels up to and including level 500 during the Data Flows module.
+This project will take you multiple weeks to complete. As always, we will break down the project into levels we can deliver incrementally. You must finish each milestone before you start working on the next one (but it's OK to know what the future levels are going to be - it may help you design things). Your goal is to complete all of the levels up to and including level 500 during the Data Flows module.
 
 ## Goals
 
@@ -110,4 +110,4 @@ You can choose whatever is easiest - given there may be multiple issues, groupin
 The trainee will deal with the issues and should check in replying to these issues.
 Check any changes made, and if all problems are resolved, you can close the issue.
 You may wish to double-check your notification settings to make sure you are notified for any replies or activity on these issues.
-When allthe issues you opened are closed, the task is considered "complete".
+When all the issues you opened are closed, the task is considered "complete".

From 32a1155e2c80259d3d1cdbdfafdae16e816268a8 Mon Sep 17 00:00:00 2001
From: l <l>
Date: Wed, 29 Apr 2026 11:13:43 +0100
Subject: [PATCH 5/8] make instruction more explicit

---
 readme.md | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/readme.md b/readme.md
index 1be2c20..930b1b4 100644
--- a/readme.md
+++ b/readme.md
@@ -87,27 +87,27 @@ You are allowed to change anything in your partner's code to make it easier to u
 Remember, finish each level before you move on to the next. Reach out for help when you're stuck.
 
 ## Submission
-
 When you are ready to submit this task, you will submit it in a different way to normal.
-Instead of using PRs, you will deploy your TV project website to GitHub pages and reviewers will assess it live, check the code, and leave issues for you to fix if there are any problems.
+You will **not** use PRs.
+Instead, you will deploy your TV project website to GitHub pages and reviewers will assess, check the code, and leave issues for you to fix.
 
 When you have finished level 500:
-1. Go to the Portal and fill out the submission step for the TV Project. Include a link to the deployed page, and the branch where you finished level 500.
+1. Go to the CYF Portal and fill out the submission step for the TV Project. Include a link to the deployed page, your repository, and the branch you used for level 500.
 2. A reviewer will check your project and leave issues on your repository.
-3. Resolve the issues, and check that the reviewer is happy the problems are resolved. The reviewer will close the issues when they are happy they are fixed.
-4. Once all issues raised are fixed and closed, your TV project is fully submitted.
+3. Resolve the issues, and use the issue comments to check that the reviewer is happy the problems are resolved.
+4. The reviewer will close the issues when they are fixed.
+4. Once all issues raised are fixed and closed, your TV project is submitted and complete.
 
 ### Instructions for Reviewers
 **Requirements**
 If this is your first review of the TV show project, familiarise yourself with the task requirements.
-You will review features that are present in level 500, which includes some requirements from prior levels.
 For your convenience, you can find a list of all the requirements [here](levels/Reviewers-All-Requirements.md).
 There are no rules about how the site should look, only how it behaves.
 
 **How to review**
-Submission is not done via a pull request, instead any issues you find should be raised as issues.
-You can choose whatever is easiest - given there may be multiple issues, grouping them into issues by related themes may be best, but use your own judgement.
+Submission is not done via a PR, instead any problems you find should be raised as issues in the repository.
+Given there may be multiple problems, grouping them into issues by related themes may be easiest, so use your own judgement.
 The trainee will deal with the issues and should check in replying to these issues.
 Check any changes made, and if all problems are resolved, you can close the issue.
 You may wish to double-check your notification settings to make sure you are notified for any replies or activity on these issues.
-When all the issues you opened are closed, the task is considered "complete".
+When all the issues you opened are closed, the task is considered complete.

From 9262a7ac2fe75b13b2646cbe109d3504e6e1e0ad Mon Sep 17 00:00:00 2001
From: l <l>
Date: Wed, 29 Apr 2026 11:55:50 +0100
Subject: [PATCH 6/8] update issue templates to allow for freeform review

---
 .github/ISSUE_TEMPLATE/config.yml             |  2 +-
 .github/ISSUE_TEMPLATE/pd-assignment.yml      | 59 --------------
 .github/ISSUE_TEMPLATE/tech-ed-assignment.yml | 80 -------------------
 3 files changed, 1 insertion(+), 140 deletions(-)
 delete mode 100644 .github/ISSUE_TEMPLATE/pd-assignment.yml
 delete mode 100644 .github/ISSUE_TEMPLATE/tech-ed-assignment.yml

diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
index 5fe8ffd..5fe1d1c 100644
--- a/.github/ISSUE_TEMPLATE/config.yml
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -1,4 +1,4 @@
-blank_issues_enabled: false
+blank_issues_enabled: true
 contact_links:
   - name: CYF
     url: contact@codeyourfuture.io
diff --git a/.github/ISSUE_TEMPLATE/pd-assignment.yml b/.github/ISSUE_TEMPLATE/pd-assignment.yml
deleted file mode 100644
index c8bd229..0000000
--- a/.github/ISSUE_TEMPLATE/pd-assignment.yml
+++ /dev/null
@@ -1,59 +0,0 @@
-name: PD Coursework
-description: Assign a piece of PD coursework
-title: "[PD] <title>"
-labels: [PD, 🏝 Priority Stretch, 🐇 Size Small]
-body:
-  - type: markdown
-    attributes:
-      value: |
-        Thanks for taking the time to assign this coursework!
-  - type: input
-    attributes:
-      label: Coursework content
-    validations:
-      required: true
-  - type: input
-    attributes:
-      label: Estimated time in hours
-      description: (PD has max 4 per week total)
-    validations:
-      required: true
-  - type: textarea
-    attributes:
-      label: What is the purpose of this assignment?
-      description: Clearly explain the purpose of this assignment and how trainees can evaluate this.
-    validations:
-      required: true
-  - type: textarea
-    attributes:
-      label: How to submit
-      description: State in clear steps how a trainee can submit this assignment.
-      placeholder: |
-        Copy the Google doc to your own Google Drive
-        Complete the work assigned
-        When you are ready, move your document to your class Drive
-    validations:
-      required: true
-  - type: textarea
-    attributes:
-      label: Anything else?
-      description: |
-        Links? References? Anything that will give more context
-
-        Tip: You can attach images or log files by clicking this area to highlight it and then dragging files in.
-  - type: markdown
-    attributes:
-      value: |
-        **Thank you so much.**
-
-        Please now complete this ticket by filling in the options on the sidebar.
-
-        1. Update labels
-        - priority -- is this coursework key, mandatory, or stretch?
-        - size -- help trainees plan their time with rough estimation
-        2. Add to project backlog
-        - add to the project named the same as this repo
-        - fill in custom fields -- priority, size, hours, week -- to match this issue
-
-        Once your ticket is complete, you may like to check it out on the example project board attached to this repo.
-        This is so you understand how trainees will use your work.
diff --git a/.github/ISSUE_TEMPLATE/tech-ed-assignment.yml b/.github/ISSUE_TEMPLATE/tech-ed-assignment.yml
deleted file mode 100644
index 1bdba29..0000000
--- a/.github/ISSUE_TEMPLATE/tech-ed-assignment.yml
+++ /dev/null
@@ -1,80 +0,0 @@
-name: Tech Ed Coursework
-description: Assign a piece of technical coursework
-title: "[TECH ED] <title>"
-labels: [Tech Ed, 🏕 Priority Mandatory, 🐂 Size Medium]
-body:
-  - type: markdown
-    attributes:
-      value: |
-        Thanks for taking the time to assign this coursework! 
-
-        To support our trainees with planning and prioritising their own learning journey, we want our coursework assignments to be more informative. 
-        We don't just want to tell them what to do, we want to tell them stuff like:
-        - why we are doing it
-        - what it's "for" (problem-solving, debugging, etc)
-        - how long they should spend on it, maximum
-        - how to get help 
-        - how to review it with answers 
-        - how to get it reviewed from mentors and peers
-  - type: input
-    attributes:
-      label: Link to the coursework
-    validations:
-      required: true
-  - type: textarea
-    attributes:
-      label: Why are we doing this?
-      description: Clearly explain the purpose of this assignment
-    validations:
-      required: true
-  - type: input
-    attributes:
-      label: Maximum time in hours
-      description: (Tech has max 16 per week total)
-    validations:
-      required: true
-  - type: textarea
-    attributes:
-      label: How to get help
-      description: State simply how trainees can get help with this assignment
-      placeholder: |
-        Share your blockers in your class channel
-        https://syllabus.codeyourfuture.io/guides/asking-questions
-  - type: textarea
-    attributes:
-      label: How to submit
-      description: State in clear steps how a trainee can submit this assignment.
-      placeholder: |
-        Fork the repo to your own GitHub account
-        Make regular small commits with clear messages
-        When you are ready, open a Pull Request to the CYF repo
-        Make sure you fill in the PR template provided
-    validations:
-      required: true
-  - type: textarea
-    attributes:
-      label: How to review
-      description: How to get code review and how to self-review
-  - type: textarea
-    attributes:
-      label: Anything else?
-      description: |
-        Links? References? Anything that will give more context
-
-        Tip: You can attach images or log files by clicking this area to highlight it and then dragging files in.
-  - type: markdown
-    attributes:
-      value: |
-        **Thank you so much.**
-
-        Please now complete this ticket by filling in the options on the sidebar.
-
-        1. Update labels
-        - priority -- is this coursework key, mandatory, or stretch? Pick one.
-        - size -- help trainees plan their time with rough estimation. Pick one
-        - topics -- add all that seem relevant to you. 
-        2. Add to milestone
-        - week 1,2,3,4
-
-        Once your ticket is complete, you may like to add it to the example project board attached to this repo.
-        This is so you understand how trainees will use your work. Nobody has built a board copier yet, so trainees will be doing this step themselves.

From 84b3c0182b9a6bfe0c8fb375fcd527c1e9f7f5a6 Mon Sep 17 00:00:00 2001
From: l <l>
Date: Wed, 29 Apr 2026 12:04:22 +0100
Subject: [PATCH 7/8] add template for reviewing issue

---
 .github/ISSUE_TEMPLATE/pd-assignment.yml | 10 ++++++++++
 1 file changed, 10 insertions(+)
 create mode 100644 .github/ISSUE_TEMPLATE/pd-assignment.yml

diff --git a/.github/ISSUE_TEMPLATE/pd-assignment.yml b/.github/ISSUE_TEMPLATE/pd-assignment.yml
new file mode 100644
index 0000000..e3850c9
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/pd-assignment.yml
@@ -0,0 +1,10 @@
+name: Coursework Review
+description: For a volunteer to review a coursework project
+title: "[Review] <title>"
+labels: []
+body:
+  - type: textarea
+    attributes:
+      label: Any problems you want to discuss, or something you want to highlight was done well
+    validations:
+      required: true

From f7e031e887d54b0cff87c41e2c475423e63a3239 Mon Sep 17 00:00:00 2001
From: l <l>
Date: Wed, 29 Apr 2026 12:07:15 +0100
Subject: [PATCH 8/8] revert changed files

---
 index.html |  4 +---
 script.js  | 12 ------------
 2 files changed, 1 insertion(+), 15 deletions(-)

diff --git a/index.html b/index.html
index b479905..9a400d1 100644
--- a/index.html
+++ b/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
-    <title>TV Show Project | LonMcGregor</title>
+    <title>TV Show Project | My Name (My GitHub username)</title>
     <link href="style.css" rel="stylesheet" />
     <link rel="icon" href="/favicon.ico" type="image/x-icon" />
   </head>
@@ -17,7 +17,5 @@
 
     <!-- Loads YOUR javascript code -->
     <script src="script.js"></script>
-
-    <footer>Data from TVMaze. <a href="https://www.tvmaze.com/api#licensing">Use of the TVmaze API is licensed by CC BY-SA</a>. This means the data can freely be used for any purpose, as long as TVmaze is properly credited as source and your usage complies with the ShareAlike provision. You can satisfy the attribution requirement by linking back to TVmaze from within your application or website, for example using the URLs available in the API.
   </body>
 </html>
diff --git a/script.js b/script.js
index 29be7f0..87a7de8 100644
--- a/script.js
+++ b/script.js
@@ -7,18 +7,6 @@ function setup() {
 function makePageForEpisodes(episodeList) {
   const rootElem = document.getElementById("root");
   rootElem.textContent = `Got ${episodeList.length} episode(s)`;
-  for(let ep of episodeList){
-    document.writeln(`<article>
-    <h1>S${ep.season.toString().padStart(2,"0")} - E${ep.number.toString().padStart(2,"0")}
-    <h2>${ep.name}</h2>
-    <img src="${ep.image.medium}" />
-    <details>
-    <summary>blurb</summary>
-    ${ep.summary}
-    </details>
-    </article>`)
-  }
 }
 
-
 window.onload = setup;
