Update based on Fliss comments

Author: liamjberrisford

_toc.yml

@@ -317,11 +317,11 @@ parts:
   - caption: Join Us!
     chapters: 
       - file: contributing/community
-      - file: contributing/new_course_checklist_timeline
       - file: contributing/contributing
       - file: contributing/roles
       - file: contributing/contributing_guidelines
       - file: contributing/developing_a_course
+      - file: contributing/new_course_checklist_timeline
       - file: contributing/suggestions_form
 
   - caption: Community Guidelines and Policy Information

contributing/new_course_checklist_timeline.ipynb

@@ -9,103 +9,58 @@
     "\n",
     "## Timescales & Ordering\n",
     "\n",
-    "- **12 weeks before launch**  \n",
-    "  - Hold initial logistics call with Programme Management to define learning objectives, course scope, and high-level timeline  \n",
-    "  - Confirm roles (Developer, Lead, Helper) and schedule regular check-ins  \n",
+    "### **12 weeks before delivery** \n",
+    "  - Hold initial logistics call with Programme Management to define learning objectives, course scope, and high-level timeline\n",
+    "  - Confirm roles (Developer, Lead, Helper) and schedule regular check-ins\n",
+    "  - Create a feature branch on the [CfRR_Courses repo](https://github.com/coding-for-reproducible-research/CfRR_Courses), alongside a GitHub Issue   \n",
+    "  - Developer begins drafting core materials \n",
+    "\n",
+    "#### Checklist Steps \n",
+    "- [ ] Schedule and hold **initial logistics call** with Programme Management and Delivery Team  \n",
+    "- [ ] Define roles: Developer, Leader, Helper, Participant, Programme Management, and schedule a recurring meeting  \n",
+    "- [ ] Open GitHub Issue for the new course; create feature branch  \n",
+    "- [ ] Draft **course objectives** and detailed **learning objectives** for each section of the course\n",
     "\n",
-    "- **10 weeks before launch**  \n",
-    "  - Developer begins drafting core materials (notebooks, slides, datasets, etc.)  \n",
-    "  - Create a feature branch on the [CfRR_Courses repo](https://github.com/coding-for-reproducible-research/CfRR_Courses)  \n",
     "\n",
-    "- **5 weeks before launch**  \n",
-    "  - Submit the first complete draft of materials for internal review  \n",
+    "### **6 weeks before delivery**  \n",
+    "  - Submit the first complete draft of materials for internal review. Liam Berrisford (@liamjberrisford) to validate website functionality (including accessibility features), then a separate reviewer to verify that the course content itself is accurate and appropriate.\n",
     "  - Draft metadata in `programme_information` and `section_landing_page` (titles, descriptions, prerequisites)  \n",
     "  - Create the “Where Is My Understanding?” quiz; confirm the quiz `JSON` files render via `JupyterQuiz`\n",
-    "  - Conduct accessibility review (alt text, colour contrast, headings, tables)  \n",
     "\n",
-    "- **4 weeks before launch**  \n",
-    "  - Integrate content into `JupyterBook`; perform a dry-run build on staging  \n",
-    "  - Link all assets (images, data files, interactive widgets)  \n",
-    "  - Add course pages to `_toc.yml`  \n",
-    "  - If non-Python kernels are used, add them to the non-run list in `_config.yml`  \n",
-    "\n",
-    "- **1 week before launch**  \n",
-    "  - Freeze content; perform final proofreading and complete “top-to-bottom” code execution  \n",
-    "  - Hold sign-off meeting with Programme Management  \n",
-    "  - Merge the feature branch and add the new course to the live website  \n",
     "\n",
-    "- **Post-launch (within 1 week)**  \n",
-    "  - Collect initial learner feedback via online form; log any issues as GitHub issues  \n",
-    "  - Plan the first update cycle based on participant feedback  \n",
-    "\n",
-    "## Checklist\n",
-    "\n",
-    "### Logistics & Planning\n",
-    "- [ ] Schedule and hold **initial logistics call** with Programme Management and Delivery Team  \n",
-    "- [ ] Define roles: Developer, Leader, Helper, Participant, Programme Management  \n",
-    "- [ ] Open GitHub Issue for the new course; create feature branch  \n",
-    "\n",
-    "### Content Creation & Structure\n",
-    "- [ ] Draft **course objectives** and detailed **learning objectives** for each section of the course\n",
-    "- [ ] Develop Jupyter notebooks (`.ipynb`) for Python or learnr tutorials (`.Rmd`) for R. Other types of course should be discussed with the central CfRR team\n",
-    "- [ ] Include slides or PDFs as needed; confirm static content links  \n",
-    "\n",
-    "### Metadata & Site Integration\n",
+    "#### Checklist Steps\n",
     "- [ ] Populate `programme_information` \n",
     "- [ ] Populate `section_landing_page`\n",
     "- [ ] Populate `where_is_my_understanding`\n",
-    "- [ ] Ensure no overlap or missing sections  \n",
-    "\n",
-    "### Rendering & Functionality\n",
-    "- [ ] Build with Jupyter Book on the PR; confirm notebooks render without errors  \n",
+    "- [ ] Add course pages to `_toc.yml`  \n",
+    "- [ ] Ensure no overlap or missing sections \n",
     "- [ ] Test interactive plots, embedded HTML, and widgets  \n",
     "- [ ] Validate “Where Is My Understanding?” quiz (`display_quiz(\"path/to/quiz.json\")`)  \n",
-    "\n",
-    "### Asset Linking & URL Encoding\n",
     "- [ ] Verify all file paths (spaces, special characters) are realtive paths as used in JupyterBook\n",
     "- [ ] Confirm images, data files, and HTML assets load correctly  \n",
-    "\n",
-    "### Accessibility & Style\n",
-    "- [ ] Use descriptive headings (H1–H3) and labels  \n",
-    "- [ ] Provide concise alt text for all images  \n",
-    "- [ ] Check colour contrast with a Contrast Checker  \n",
-    "- [ ] Avoid conveying information by colour alone; add text indicators, change shapes of points etc  \n",
-    "- [ ] Use clear, simple language and accessible tables  \n",
-    "\n",
-    "### Testing & QA\n",
+    "- [ ] Include slides or PDFs as needed; confirm static content links  \n",
     "- [ ] Execute all notebooks end-to-end  \n",
     "- [ ] Peer-review code comments and markdown explanations  \n",
-    "- [ ] Conduct cross-browser and device checks  \n",
-    "\n",
-    "\n",
-    "## Highlighting Issues\n",
     "\n",
-    "Auditing materials refreshes your understanding and helps improve accuracy. Types of issues include:  \n",
-    "- Typographical errors  \n",
-    "- Factual errors  \n",
-    "- Content clarity and comprehension  \n",
-    "- Formatting and layout issues  \n",
-    "- Technical errors (broken links, non-functional elements)  \n",
-    "- Cultural and bias concerns  \n",
-    "- Outdated content  \n",
-    "- Logical fallacies or reasoning errors  \n",
     "\n",
-    "## Ensuring Understanding\n",
-    "- **Multiple-Choice Questions** via JupyterQuiz (`display_quiz(\"path/to/quiz.json\")`)  \n",
-    "- **Coding Exercises** with clear instructions, hints, and dropdown solutions (use Jupyter Book admonitions) \n",
-    "\n",
-    "## Language-Specific Standards\n",
+    "### **4 weeks before delivery**  \n",
+    "  - Confirm that all feedback and change requests from the internal review have been addressed\n",
+    "  - Link all assets (images, data files, interactive widgets)  \n",
     "\n",
-    "### Python\n",
-    "- Use Jupyter notebooks (`.ipynb`) with well-commented code and markdown  \n",
-    "- Include visualizations, interactive elements, and test notebooks end-to-end  \n",
+    "#### Checklist Steps\n",
+    "- [ ] Confirm there is no outstanding feedback to be actioned from the internal review \n",
+    "- [ ] Ensure that the Continuous Integration (CI) in the PR for building the Jupyter Book (website) and Accessibility passes\n",
     "\n",
-    "### R\n",
-    "- Use learnr tutorials (`.Rmd`) distributed via the `cfrr-r-tutorials` repo  \n",
-    "- Define prerequisites, embed interactive exercises/quizzes, and self-contain data and instructions  \n",
     "\n",
+    "### **2 week before delivery**  \n",
+    "  - Freeze content; perform final proofreading and complete “top-to-bottom” code execution  \n",
+    "  - Please notify Liam Berrisford (@liamjberrisford) that the content is ready for integration into the website and request his final review prior to publication.\n",
+    "  - Merge the feature branch and add the new course to the live website\n",
     "\n",
-    " \n"
+    "#### Checklist Steps\n",
+    "- [ ] Perform a final proofreading pass; execute a full “top-to-bottom” run of all notebooks  \n",
+    "- [ ] Notify Liam Berrisford (@liamjberrisford) that materials are ready for integration and request his final sign-off  \n",
+    "- [ ] Once approved, merge the feature branch into main and deploy the new course to the live website  "
    ]
   },
   {