Course content minor updates, readme updates (#31)

* readme updates, migrate generate_slides.sh from shell course

* some slide updates

---------

Co-authored-by: Simeon Wong <dtxe@users.noreply.github.com>

Author: dtxe

.gitignore

@@ -1,5 +1,3 @@
 .DS_Store
 .vscode/
-/03_instructional_team/lessons/pdf/*
-/03_instructional_team/lessons/html/*
-/03_instructional_team/lessons/pptx/*
+/03_instructional_team/node_modules

01_materials/slides/01_git_installation.pdf

@@ -18,9 +18,9 @@ In this assignment, you will be learning more about `git` and `GitHub` by workin
     
     > b. What is a _pull request_?
 
-    > c. How do I open up a _pull request_?
+    > c. Describe the steps to open a _pull request_?
     
-    > d. Give me a step by step guide on how to add someone to your repository.
+    > d. Describe the steps to add a collaborator to a repository (share write permissions)
 
     > e. What is the difference between `git` and `GitHub`?
 
@@ -50,7 +50,7 @@ Feel free to at any point (recommended after answering every 2 questions) to sta
 🚨 **Please review our [Assignment Submission Guide](https://github.com/UofT-DSI/onboarding/blob/main/onboarding_documents/submissions.md)** 🚨 for detailed instructions on how to format, branch, and submit your work. Following these guidelines is crucial for your submissions to be evaluated correctly.
 
 ### Submission Parameters:
-* Submission Due Date: `11:59 PM - 28/04/2024`
+* Submission Due Date: `2024-08-25 - 23:59`
 * The branch name for your repo should be: `assignment`
 * What to submit for this assignment:
     * The mentioned markdown file above (README.md) should be populated with what we have asked for and should be the only change in your pull request.

01_materials/slides/02_git_version_control.pdf

@@ -1,7 +1,7 @@
 #!/bin/bash
 
 # CONFIGURATION
-folder_md="lessons/"
+folder_md="markdown_slides/"
 folder_output="../01_materials/slides" # This will be used for both PDF and HTML
 
 # Clear the screen for the splash screen
@@ -38,7 +38,7 @@ function show_help() {
     echo ""
     echo "Options:"
     echo "  --html                   Generate slides in HTML format. This option"
-    echo "                           processes all Markdown files in the 'lessons'"
+    echo "                           processes all Markdown files in the 'markdown_slides'"
     echo "                           directory, outputting HTML files."
     echo ""
     echo "  --pdf                    Generate slides in PDF format. Similar to --html,"
@@ -59,8 +59,8 @@ function show_help() {
     echo "    $0 --pdf"
     echo ""
     echo "Note:"
-    echo "  Ensure Marp CLI is installed and accessible in your system's PATH."
-    echo "  The script processes Markdown (.md) files located in the 'lessons'"
+    echo "  Ensure Node.js is installed and npm is accessible in your system's PATH."
+    echo "  The script processes Markdown (.md) files located in the 'markdown_slides'"
     echo -e "  directory, preserving filenames but changing extensions to .html or .pdf.\n\n"
 }
 
@@ -71,11 +71,16 @@ if [ "$#" -lt 1 ]; then
 fi
 
 # Check for Marp CLI installation
-if ! command -v marp &> /dev/null; then
-    echo "- Error: Marp CLI is not installed. Please install Marp CLI to proceed."
+if ! command -v npx >/dev/null 2>&1; then
+    echo "- Error: npx is not installed. Please install Node.js to proceed."
     exit 1
 fi
 
+if ! npx marp --version >/dev/null 2>&1; then
+    echo "- Marp CLI is not installed. Installing Marp CLI in this repository..."
+    npm install --no-save @marp-team/marp-cli
+fi
+
 # Defaults
 output_type=""
 theme_path=""
@@ -144,12 +149,12 @@ for markdown_file in $markdown_files; do
         # Generate HTML
         output_file+=".html"
         echo "  - Generating HTML: $output_file"
-        marp "$markdown_file" --output "$output_file" --html --allow-local-files ${theme_path:+--theme-set $theme_path} # &> /dev/null
+        npx marp "$markdown_file" --output "$output_file" --html --allow-local-files ${theme_path:+--theme-set $theme_path} # &> /dev/null
     elif [ "$output_type" = "--pdf" ]; then
         # Generate PDF
         output_file+=".pdf"
         echo "  - Generating PDF: $output_file"
-        marp "$markdown_file" --output "$output_file" --pdf --allow-local-files --pdf-notes ${theme_path:+--theme-set $theme_path} # &> /dev/null
+        npx marp "$markdown_file" --output "$output_file" --pdf --allow-local-files --pdf-notes ${theme_path:+--theme-set $theme_path} # &> /dev/null
     else
         # nahhh
         show_help

01_materials/slides/03_git_basics.pdf

@@ -1,6 +1,9 @@
 ---
 marp: true
-theme: dsi-certificates-theme
+style: |
+    section {
+        font-family: Inter, -apple-system, BlinkMacSystemFont, 'Helvetica Neue', sans-serif;
+    }
 _class: invert
 paginate: true
 ---

01_materials/slides/04_optional_git_slide.pdf

@@ -1,6 +1,9 @@
 ---
 marp: true
-theme: dsi-certificates-theme
+style: |
+    section {
+        font-family: Inter, -apple-system, BlinkMacSystemFont, 'Helvetica Neue', sans-serif;
+    }
 _class: invert
 paginate: true
 ---
@@ -13,6 +16,8 @@ $ echo "Data Sciences Institute"
 
 ---
 Prerequisites:
+- Git version ≥2.39
+- Git Credential Manager
 - GitHub account
 
 ---
@@ -31,43 +36,31 @@ References
 ## `Version Control`
 
 ---
-##### What is Version Control?
-Version control is a system that records changes to a file or a set of files over time so that we can recall a specific version later. We may already do this by copying files to another directory to save past versions.While it is simple, it lacks flexibility and complexity.
+#### What is Version Control?
+Version control is a system:
+* that records changes to a file or a set of files over time 
+* that enables recall a specific version
 
----
-Version Control Systems (VCS) can do a number of things and can be applied on nearly any type of file on our computers:
-- revert files to a previous state
-- revert entire project to a previous state
-- compare changes over time
-- see who modified something last
-- who introduced an issue and when
-- recover lost files
+We may already do this by copying files to another directory to save past versions. While it is simple, it lacks flexibility and complexity.
 
 ---
-##### Local Version Control Systems
-Local VCSs were developed to keep track of changes to our files by putting them in a version database.
-
-![bg right contain](./pics/02_lvc.png)
-
----
-##### Centralized Version Control Systems
-Centralized VCSs (CVCS) were developed to enable collaboration with developers on other systems. CVCSs have a single server that contains all the versioned files.
-
-![bg left contain](./pics/02_cvcs.png)
-
----
-CVCSs allow some level of transparency to others' work and give Administrators a level of control over what developers can and can't do.
-
-Unfortunately, a single server means that if it ever goes down, all collaboration halts for however long that lasts for. Additionally, if backups haven't been kept, work could easily be lost.
+#### Why version control?
+Version Control Systems (VCS) can do a number of things and can be applied on nearly any type of file on our computers:
+* revert files to a previous state
+* revert entire project to a previous state
+* compare changes over time
+* see who modified something last
+* who introduced an issue and when
+* recover lost files
 
 ---
-##### Distributed Version Control Systems
-To handle the limitations of LVCSs and CVCSs, Distributed VCSs were created. This includes Git, Mercurial and Bazaar. 
+#### Why specialized version control for software teams?
+* Robust software is documented as it is written
+    * Log changes and reasoning for why changes are made
+* Working in teams requires code-specific version control
+    * Changing one part of a code project can affect behaviour in seemingly unrelated features
+    * In-progress state of one component can render the entire program temporarily unusable (e.g. syntax error)
 
-Collaborators mirror the entire repsoitory, therefore if a server dies, any one of the collaborators' repositories can be copied back to the server to restore it.
-
----
-![w:560 center](./pics/02_dvcs.png)
 
 ---
 
@@ -80,22 +73,25 @@ Questions?
 ## `Git`
 
 ---
-##### Git Basics
-Git thinks of data in a very different way than other VCSs. Instead of storing a set of files and the changes over time, Git thinks of its data more like a set of snapshots of a mini file system. 
+### Git Basics
+Git is the most common VCS in modern coding teams. 
 
-If files have not changed, Git does not store the file again, it links to the previous identical file already stored.
+##### Git is efficient with storage
+* Git stores snapshots of files in your project directory
+* If files have not changed, Git does not store the file again, it links to the previous identical file already stored.
 
 ---
-![w:1100 center](./pics/02_git_data.png)
+
+![auto center](./pics/02_git_data.png)
 
 ---
-##### Local Operations
+##### Git can operate locally
 Most operations on Git only need local files and resources to operate. Git also keeps the entire history of our projects on our local disks meaning we can see changes made months ago without a remote server.
 
 We also don't need to be connected to the server to get work done, rather we only need to be connected when we want to upload our work.
 
 ---
-##### Benefits
+##### Git assures integrity
 Git uses a check-summing mechanism called *SHA-1 hash* which is calculated based on the contents of a file or directory structure in Git. It looks somehting like this:
 ```
 24b9da6552252987aa493b52f8696cd6d3b00393

02_activities/assignments/git_assignment.md

@@ -1,6 +1,9 @@
 ---
 marp: true
-theme: dsi-certificates-theme
+style: |
+    section {
+        font-family: Inter, -apple-system, BlinkMacSystemFont, 'Helvetica Neue', sans-serif;
+    }
 _class: invert
 paginate: true
 ---
@@ -327,12 +330,17 @@ $ git remote show origin
 Here we can see the URL that we're fetching and pulling from, our remote branches, and configurations for git push (to the main branch or another).
 
 ---
-To send and retrieve work between our local and remote repositories, we have to authenticate a personal access token:
+To send and retrieve work between our local and remote repositories, we use Git Credential Manager.
 
-               ![w:350 left](./pics/03_settings.png)           ![w:340 right](./pics/03_developer.png)
+```console
+$ git credential-manager github login
+```
 
----
-![w:1150 center](./pics/03_personal_auth.png)
+To check our login status
+
+```console
+$ git credential-manager github list
+```
 
 ---