+
+2. **Clone Your Fork To Your Computer**: To make edits and test your script.
+ ```bash
+ cd
+
+
+
+
+
\ No newline at end of file
diff --git a/03_instructional_team/githubpages/shell_basics.yml b/03_instructional_team/githubpages/shell_basics.yml
new file mode 100644
index 000000000..7506e89e8
--- /dev/null
+++ b/03_instructional_team/githubpages/shell_basics.yml
@@ -0,0 +1,321 @@
+title: Shell Basics Practice Problems
+problems:
+ - title: "Creating Directories"
+ description: |
+ Which command would you use to create a directory named `dir1`?
+ questiontype: multiplechoice
+ options:
+ - "`mkdir dir1`"
+ - "`touch dir1`"
+ - "`cd dir1`"
+ - "`ls dir1`"
+ correct_options: [0]
+ solution: |
+ The correct command to create a directory named `dir1` is:
+ ```bash
+ mkdir dir1
+ ```
+
+ * `touch dir1` would create a file named `dir1`, not a directory.
+ * `cd dir1` would change into a directory named `dir1`, but it doesn't create it.
+ * `ls dir1` would list the contents of a directory named `dir1`, but it doesn't create it.
+
+ - title: "Creating Directories"
+ description: |
+ How would you create directories named `dir2` and `dir3`, within a new directory named `dir1`?
+ questiontype: multiplechoice
+ options:
+ - |
+ ```
+ mkdir dir1/dir2 dir1/dir3
+ ```
+ - |
+ ```
+ mkdir dir1
+ mkdir dir1/dir2 dir1/dir3
+ ```
+ - |
+ ```
+ mkdir dir1
+ mkdir dir2 dir3
+ ```
+ - |
+ ```
+ cd dir1
+ mkdir dir2 dir3
+ ```
+ - |
+ ```
+ mkdir dir1
+ cd dir2
+ mkdir dir3
+ ```
+ correct_options: [1]
+ solution: |
+ First, we must create `dir1`, and then we can create `dir2` and `dir3` inside it.
+
+ Alternatively, we can use the `mkdir -p` command to create the parent directory and subdirectories in one go:
+ ```bash
+ mkdir -p dir1/dir2 dir1/dir3
+ ```
+ This command would creates `dir1` and its subdirectories `dir2` and `dir3` in a single step.
+
+
+ The other options are incorrect.
+ ```
+ mkdir dir1
+ mkdir dir2 dir3
+ ```
+ * This would create `dir2` and `dir3` in the current directory, not inside `dir1`.
+
+
+ ```
+ cd dir1
+ mkdir dir2 dir3
+ ```
+ * This would fail because `dir1` does not exist yet.
+
+
+ ```
+ mkdir dir1
+ cd dir2
+ mkdir dir3
+ ```
+ * This would fail because `dir2` does not exist yet.
+
+
+ - title: "Verifying Directory Creation"
+ description: |
+ You've just created the directories above.
+
+ For reference, this is your current terminal session:
+ ```bash
+ user@computer:~$ pwd
+ /home/user
+ user@computer:~$
+ ```
+
+ How might you verify the directories were created successfully?
+ questiontype: multiplechoice
+ options:
+ - "`ls`"
+ - "`ls -r`"
+ - "`ls dir1`"
+ - "`ls dir2 dir3`"
+ - "`find dir1 dir2 dir3`"
+ - "`cat dir1/*`"
+ - "`less dir1 dir1/dir2 dir1/dir3`"
+
+ correct_options: [1, 2]
+ solution: |
+ To verify the directories were created successfully, you can use:
+ `ls dir1` or `ls -r`
+ - `ls dir1` lists the contents of `dir1`, which should include `dir2` and `dir3`.
+ - `ls -r` lists all files and directories in the current directory and its subdirectories.
+
+ The other options are incorrect because:
+ * `ls` would list the contents of the current directory, but not specifically check for `dir2`, or `dir3` which are inside `dir1`.
+ * `ls dir2 dir3` would fail because `dir2` and `dir3` are inside `dir1` and do not exist in the current directory.
+ * `find dir1 dir2 dir3` is not a valid command.
+ * `cat dir1/*` would attempt to display the contents of files in `dir1`, but there are no files yet.
+ * `less dir1 dir1/dir2 dir1/dir3` would attempt to display the contents of `dir1`, `dir1/dir2`, and `dir1/dir3`, but these are directories, not files.
+
+ - title: "Creating Text Files"
+ description: |
+ After verifying you've created the directories, how would you create two text files named `file1.txt` and `file2.txt` inside a folder named `text_files`?
+
+ This is your current terminal session:
+ ```bash
+ user@computer:~$ pwd
+ /home/user
+ user@computer:~$ ls
+ dir1
+ user@computer:~$
+ ```
+ questiontype: parsons
+ options:
+ - "`mkdir text_files`"
+ - "`cd text_files`"
+ - "`touch file1.txt file2.txt`"
+ - "`touch file1 file2`"
+ - "`new file1.txt file2.txt`"
+ - "`echo file1.txt file2.txt`"
+ - "`mv file1.txt file2.txt`"
+ - "`cp file1.txt file2.txt`"
+ - "`less file1.txt file2.txt`"
+ - "`cat file1.txt file2.txt`"
+ correct_options: [0, 1, 2]
+ solution: |
+ To create the text files, you can follow these steps:
+ ```bash
+ mkdir text_files
+ cd text_files
+ touch file1.txt file2.txt
+ ```
+ This creates a new directory named `text_files`, navigates into it, and creates two empty text files named `file1.txt` and `file2.txt`.
+
+ The other options are incorrect because:
+ * `touch file1 file2` would create files without the `.txt` extension.
+ * `new file1.txt file2.txt` is not a valid command.
+ * `echo file1.txt file2.txt` would just print `file1.txt file2.txt` to the terminal, not create files.
+ * `mv file1.txt file2.txt` would move files, but they don't exist yet.
+ * `cp file1.txt file2.txt` would copy files, but they don't exist yet.
+ * `less file1.txt file2.txt` would attempt to display the contents of non-existent files.
+ * `cat file1.txt file2.txt` would attempt to display the contents of non-existent files.
+
+ - title: "Appending Text to a File"
+ description: |
+ Suppose your terminal session looks like this:
+ ```bash
+ user@computer:~$ pwd
+ /home/user
+ user@computer:~$ ls text_files
+ file1.txt file2.txt
+ user@computer:~$
+ ```
+ You want to *append* the text "Bash is hard!" to `file1.txt`.
+ questiontype: parsons
+ options:
+ - "`cd text_files`"
+ - "`echo 'Bash is hard!' > file1.txt`"
+ - "`echo 'Bash is hard!' >> file1.txt`"
+ - "`cat file1.txt`"
+ - "`less file1.txt`"
+ - "`mv file1.txt file2.txt`"
+ - "`cp file1.txt file2.txt`"
+ - "`rm file1.txt`"
+ correct_options: [0, 2]
+ solution: |
+ To append text to `file1.txt`, you can use:
+ ```bash
+ cd text_files
+ echo 'Bash is hard!' >> file1.txt
+ ```
+ This command navigates to the `text_files` directory and appends the text "Bash is hard!" to `file1.txt`.
+
+ The other options are incorrect because:
+ * `echo 'Bash is hard!' > file1.txt` would overwrite the contents of `file1.txt`, not append to it.
+ * `cat file1.txt` and `less file1.txt` would display the contents of the file but not modify it.
+ * `mv file1.txt file2.txt` would rename or move the file, not append text.
+ * `cp file1.txt file2.txt` would copy the file, not append text.
+ * `rm file1.txt` would delete the file.
+
+ - title: "Verifying Appended Text"
+ description: |
+ Suppose your terminal session looks like this:
+ ```bash
+ user@computer:~/text_files$
+ ```
+ After appending text to a file, how would you verify that your text has been successfully added to `file1.txt`?
+ questiontype: parsons
+ options:
+ - "`cat file1.txt`"
+ - "`echo file1.txt`"
+ - "`rm file1.txt`"
+ - "`ls file1.txt`"
+ - "`cd text_files`"
+ correct_options: [0]
+ solution: |
+ To verify that the text has been successfully added to `file1.txt`, you can use:
+ ```bash
+ cat file1.txt
+ ```
+ This command displays the contents of `file1.txt`, allowing you to confirm that the text "Bash is hard!" is present.
+
+ The other options are incorrect because:
+ * `cd text_files` is not necessary since you are already in the `text_files` directory.
+ * `echo file1.txt` would just print the filename, not its contents.
+ * `rm file1.txt` would delete the file.
+ * `ls file1.txt` would list the file, but not its contents.
+
+ - title: "Deleting Files and Globs"
+ description: |
+ Suppose you are inside `dir2`.
+ This is your current terminal prompt:
+ ```
+ user@computer:~$ ls dir1
+ file1.txt file2.txt dir2/ dir3/
+ user@computer:~$ cd dir1/dir2
+ /home/user/dir1/dir2
+ user@computer:~/dir1/dir2$
+ ```
+ How would you delete all `.txt` files within `dir1`?
+
+ questiontype: multiplechoice
+ options:
+ - "`rm .txt`"
+ - "`rm dir1/*.txt`"
+ - "`rm dir1/dir2/.txt`"
+ - "`rm ../*.txt`"
+ correct_options: [3]
+ solution: |
+ To delete all `.txt` files within `dir1`, you can use:
+ ```bash
+ rm ../*.txt
+ ```
+ This command removes all `.txt` files in the parent directory (`dir1`) from your current location inside `dir2`.
+
+ The other options are incorrect because:
+ * `rm .txt` would not match any files.
+ * `rm dir1/*.txt` and `rm dir1/dir2/.txt` would fail because you are currently in `dir2`
+
+ - title: "File and Directory Management: Navigating to the Parent Directory"
+ description: |
+ This is your current terminal session:
+ ```bash
+ user@computer:~/dir1/dir2$ pwd
+ /home/user/dir1/dir2
+ user@computer:~/dir1/dir2$ ls
+ user@computer:~/dir1/dir2$
+ ```
+ After working inside one of the directories, how would you navigate back to your home directory?
+ questiontype: multiplechoice
+ options:
+ - "`cd ..`"
+ - "`cd ../..`"
+ - "`cd`"
+ - "`cd /home/user`"
+ - "`cd dir1`"
+ correct_options: [1, 2, 3]
+ solution: |
+ To navigate back to your home directory, you can use:
+ - `cd` - This command takes you directly to your home directory.
+ - `cd /home/user` - This command takes you to the absolute path /home/user, which is your home directory.
+ - `cd ../..` - This command takes you two levels up from your current directory, which would also take you to your home directory.
+
+ These other options are incorrect because:
+ - The command `cd ..` would take you one level up to `dir1`, not directly to your home directory.
+ - The command `cd dir1` would attempt to change into the `dir1` directory which will fail because there is no `dir1` in the current directory.
+
+ - title: "Removing Directories and Their Contents"
+ description: |
+ This is your current terminal session:
+ ```bash
+ user@computer:~$ ls
+ Desktop/ dir1/ Documents/ Downloads/ Music/ Pictures/ Videos/
+ user@computer:~$
+ ```
+ How would you remove directory `dir1` and all its contents, including `dir2`, `dir3`, and their files? Then confirm that all directories and files have been deleted.
+ questiontype: multiplechoice
+ options:
+ - "`rm dir1`"
+ - "`rm -r dir1`"
+ - "`rm -r dir1 dir2 dir3`"
+ - "`ls`"
+ - "`ls -r dir1`"
+ - "`ls dir1/*`"
+ correct_options: [1]
+ solution: |
+ To remove `dir1` and all its contents, including `dir2`, `dir3`, and their files, you can use:
+ ```bash
+ rm -r dir1
+ ```
+ This command recursively removes the directory and all its contents.
+
+ The other options are incorrect because:
+ * `rm dir1` would fail because `dir1` is a directory and requires the `-r` option to remove it.
+ * `rm -r dir1 dir2 dir3` would attempt to remove `dir1`, `dir2`, and `dir3` but would fail because they are not in the current directory.
+ * `ls` would list the contents of the current directory, but not confirm that `dir1` has been deleted.
+ * `ls -r dir1` would list the contents of `dir1`, but it doesn't confirm that it has been deleted.
+ * `ls dir1/*` would list the contents of `dir1`, but it doesn't confirm that it has been deleted.
+
diff --git a/03_instructional_team/githubpages/shell_moderate.yml b/03_instructional_team/githubpages/shell_moderate.yml
new file mode 100644
index 000000000..417bbbceb
--- /dev/null
+++ b/03_instructional_team/githubpages/shell_moderate.yml
@@ -0,0 +1,248 @@
+title: Unix Shell Moderate Practice Problems
+problems:
+ - title: "File and Directory Management 1"
+ description: |
+ You are working on a project and need to create a directory named `data` inside your project directory (`project3`)
+ and a file named `info.txt` inside it.
+
+ This is your current terminal session:
+ ```bash
+ user@computer:~/project3/scripts$ pwd
+ /home/user/project3/scripts
+
+ user@computer:~/project3/scripts$
+ ```
+
+ Select and order the following commands to accomplish this task.
+ questiontype: parsons
+ options:
+ - "`cd ..`"
+ - "`mkdir data`"
+ - "`cd data`"
+ - "`touch info.txt`"
+ - "`ls`"
+ - "`echo info.txt`"
+ - "`cd scripts`"
+ correct_options: [0, 1, 2, 3]
+ solution: |
+ ```bash
+ user@computer:~/project3/scripts$ cd ..
+ user@computer:~/project3$ mkdir data
+ user@computer:~/project3$ cd data
+ user@computer:~/project3/data$ touch info.txt
+ ```
+
+ We start off in the `scripts` directory.
+ - First, we need to navigate to the project root directory using `cd ..`
+ - (`project3` is the parent directory of `scripts`)
+ - Then, we can create the `data` directory and navigate into it.
+ - Finally, we create the `info.txt` file.
+
+ - we can also list the contents of the current directory using `ls` to check if the `data` directory and
+ `info.txt` file was created successfully
+
+
+
+ - title: "File and Directory Management 2"
+ description: |
+ Create a directory structure for a project with the following hierarchy:
+ ```
+ project/
+ βββ src/
+ β βββ main.py
+ β βββ utils.py
+ βββ data/
+ β βββ input.csv
+ β βββ output.csv
+ βββ README.md
+ ```
+ questiontype: freeform
+ solution: |
+ To create the directory structure, you can use the following commands.
+ ```bash
+ mkdir -p project/src project/data
+ touch project/src/main.py project/src/utils.py project/data/input.csv project/data/output.csv project/README.md
+ ```
+ - Since the problem asks us to create this in the current directory, we don't need to `cd` anywhere.
+ - `mkdir -p` creates the directories and any necessary parent directories.
+ - `touch` creates the files in the specified directories.
+
+ **Alternative solution:**
+ ```bash
+ mkdir project
+ mkdir project/src
+ touch project/src/main.py
+ touch project/src/utils.py
+ mkdir project/data
+ touch project/data/input.csv
+ touch project/data/output.csv
+ touch project/README.md
+ ```
+ - In this longer example, we create the `project` directory first, then create the `src` and `data` directories inside it.
+ - `touch` is called individually for each file
+
+ Additionally:
+ - `cd` can also be used to change into each directory before creating files, but it is not necessary
+
+
+
+ - title: "Output Redirection"
+ description: |
+ Which command correctly redirects the standard output of `ls` to a file named `filelist.txt` without overwriting?
+ questiontype: multiplechoice
+ options:
+ - "ls > filelist.txt"
+ - "ls < filelist.txt"
+ - "ls >> filelist.txt"
+ - "ls filelist.txt"
+ correct_options: [2]
+ solution: |
+ The correct command is:
+ ```bash
+ ls >> filelist.txt
+ ```
+ This sends the output of `ls` into `filelist.txt`, without overwriting the file if it exists.
+
+ - `ls > filelist.txt`: This command **overwrites** the contents of `filelist.txt` with the output of `ls`.
+ - `ls < filelist.txt`: This command tries to read from `filelist.txt` as input, which is not what we want. (*not covered in the main session*)
+ - `ls filelist.txt`: This command tries to list the contents of `filelist.txt`, instead of writing to it.
+
+
+ - title: "Debugging 1"
+ description: |
+ You are trying to run a script but encounter an error. The script is supposed to print the current date and time.
+ However, it fails with the following error:
+ ```
+ bash: ./script.sh: No such file or directory
+ ```
+ What is the likely cause of this error?
+ questiontype: multiplechoice
+ options:
+ - The script does not exist in the current directory.
+ - The script does not have execute permissions.
+ - The script is not in your PATH.
+ - There is a syntax error in the script.
+ correct_options: [0]
+ solution: |
+ The script does not exist in the current directory.
+
+ - The script does not have execute permissions: If this were the case, the error would be `permission denied`, not `No such file or directory`.
+ - The script is not in your PATH: The error message indicates that the script is being called with `./`, which means it is expected to be in the current directory, not in the PATH.
+ - There is a syntax error in the script: A syntax error would occur after the script is found and executed, not before.
+
+ - title: "Debugging 2"
+ description: |
+ Suppose this is the contents of a directory on your computer:
+ ```bash
+ user@computer:~$ ls ~
+ myfile.txt mydata.csv myscript.sh myfolders/
+ ```
+
+ When you type the following commands, you get an error:
+ ```bash
+ user@computer:~$ mv mydata.csv myfolder/
+ mv: cannot move 'mydata.csv' to 'myfolder/': No such file or directory
+ user@computer:~$ mv myfile.txt myfolder/
+ mv: cannot move 'myfile.txt' to 'myfolder/': No such file or directory
+ user@computer:~$ mv myscript.sh myfolder/
+ mv: cannot move 'myscript.sh' to 'myfolder/': No such file or directory
+ ```
+
+ How can you fix this error?
+ questiontype: freeform
+ solution_template: |
+ mv mydata.csv myfolder/
+ mv myfile.txt myfolder/
+ mv myscript.sh myfolder/
+ solution: |
+ ```bash
+ user@computer:~$ mv mydata.csv myfolders/
+ user@computer:~$ mv myfile.txt myfolders/
+ user@computer:~$ mv myscript.sh myfolders/
+ ```
+
+ The error indicates that the directory `myfolder/` does not exist.
+ Ordinarily, we could create the directory using the `mkdir` command, but in this case, it looks like the directory is already created as `myfolders/`.
+ To fix the error, we can either create the directory `myfolder/` or move the files to `myfolders/` instead.
+
+ Note the spelling of myfolder**s**/
+
+ - title: "Organizing files"
+ description: |
+ Suppose this is the contents of a folder on your computer:
+ ```bash
+ user@computer:~$ ls /data/MYPROJECT/scripts
+ analyze_data.py dataset1.db dataset2.db outputimg.png
+ outputimg2.png
+ ```
+
+ You've just opened a new terminal and want to organize the files by moving datasets and outputs in separate folders.
+ Select and order the following commands to accomplish this task.
+ questiontype: parsons
+ options:
+ - "`cd /data/MYPROJECT`"
+ - "`mkdir datasets`"
+ - "`mkdir outputs`"
+ - "`mv dataset* datasets/`"
+ - "`mv scripts/dataset* datasets/`"
+ - "`mv output* outputs/`"
+ - "`mv scripts/output* outputs/`"
+ - "`cd data`"
+ - "`cd outputs`"
+ - "`echo scripts/output*`"
+ - "`movefile dataset* datasets/`"
+ - "`movefile output* outputs/`"
+ - "`cd`"
+ - "`ls`"
+ correct_options: [0, [1, 2], [4, 6]]
+
+ solution: |
+ ```bash
+ user@computer:~$ cd /data/MYPROJECT
+ user@computer:/data/MYPROJECT$ mkdir datasets
+ user@computer:/data/MYPROJECT$ mkdir outputs
+ user@computer:/data/MYPROJECT$ mv scripts/dataset* datasets/
+ user@computer:/data/MYPROJECT$ mv scripts/output* outputs/
+ ```
+
+ First, we need to navigate to the project directory, then create the `datasets` and `outputs` directories.
+ After that, we can move the dataset and output files into their respective directories.
+
+ - Running `mv dataset* datasets/` won't work, because the `dataset*` files are in the `scripts` directory, not the current directory.
+ - The command `ls` can be run to check the contents of the current directory, but it is not necessary to accomplish the task.
+
+
+ - title: "Text files"
+ description: |
+ Suppose you have the following script:
+ ```bash
+ # preview all my data files
+ echo "Data file preview"
+ echo "================="
+ cat mydata/*.txt
+ ```
+
+ When your project had fewer data files, this script worked fine. But now, the output is too long to read.
+ What are some approaches to fix this?
+ questiontype: freeform
+ solution: |
+ There are several ways to fix this issue. Here are a few options:
+ - Redirect the output to a file for later review with less
+ ```bash
+ cat mydata/*.txt > preview.txt
+ less preview.txt
+ ```
+
+ **More advanced strategies not covered in the main session:**
+ - Use the pipe operator to pipe the output to `less` directly.
+ ```bash
+ cat mydata/*.txt | less
+ ```
+ - Use `head` or `tail` to preview only the first or last few lines of each file.
+ ```bash
+ head mydata/*.txt
+ tail mydata/*.txt
+ ```
+
+
+
\ No newline at end of file
diff --git a/03_instructional_team/markdown_slides/images/1-terminal.png b/03_instructional_team/markdown_slides/images/1-terminal.png
new file mode 100644
index 000000000..9489e2955
Binary files /dev/null and b/03_instructional_team/markdown_slides/images/1-terminal.png differ
diff --git a/03_instructional_team/markdown_slides/images/2-shell.png b/03_instructional_team/markdown_slides/images/2-shell.png
new file mode 100644
index 000000000..21c356237
Binary files /dev/null and b/03_instructional_team/markdown_slides/images/2-shell.png differ
diff --git a/03_instructional_team/markdown_slides/images/3-gitbash.png b/03_instructional_team/markdown_slides/images/3-gitbash.png
new file mode 100644
index 000000000..9b56096ae
Binary files /dev/null and b/03_instructional_team/markdown_slides/images/3-gitbash.png differ
diff --git a/03_instructional_team/markdown_slides/images/4-windows_shells.png b/03_instructional_team/markdown_slides/images/4-windows_shells.png
new file mode 100644
index 000000000..5388aa56b
Binary files /dev/null and b/03_instructional_team/markdown_slides/images/4-windows_shells.png differ
diff --git a/03_instructional_team/markdown_slides/images/5-windows_terminals.png b/03_instructional_team/markdown_slides/images/5-windows_terminals.png
new file mode 100644
index 000000000..928455548
Binary files /dev/null and b/03_instructional_team/markdown_slides/images/5-windows_terminals.png differ
diff --git a/03_instructional_team/markdown_slides/images/terminology_explainer.afdesign b/03_instructional_team/markdown_slides/images/terminology_explainer.afdesign
new file mode 100644
index 000000000..97d2dc989
Binary files /dev/null and b/03_instructional_team/markdown_slides/images/terminology_explainer.afdesign differ
diff --git a/03_instructional_team/markdown_slides/images/terminology_explainer.afdesign~lock~ b/03_instructional_team/markdown_slides/images/terminology_explainer.afdesign~lock~
new file mode 100644
index 000000000..cce471a78
Binary files /dev/null and b/03_instructional_team/markdown_slides/images/terminology_explainer.afdesign~lock~ differ
diff --git a/04_instructional_team/markdown_slides/optional_unix_slides.md b/03_instructional_team/markdown_slides/optional_unix_slides.md
similarity index 100%
rename from 04_instructional_team/markdown_slides/optional_unix_slides.md
rename to 03_instructional_team/markdown_slides/optional_unix_slides.md
diff --git a/03_instructional_team/markdown_slides/unix_slides.md b/03_instructional_team/markdown_slides/unix_slides.md
new file mode 100644
index 000000000..21246f56a
--- /dev/null
+++ b/03_instructional_team/markdown_slides/unix_slides.md
@@ -0,0 +1,559 @@
+---
+marp: true
+style: |
+ section {
+ font-family: Inter, -apple-system, BlinkMacSystemFont, 'Helvetica Neue', sans-serif;
+ }
+_class: invert
+paginate: true
+---
+
+# Unix Shell
+
+```
+$ echo "Data Sciences Institute"
+```
+
+---
+### What is Unix?
+
+Unix was a text-based operating system created in 1970. Many of its derivatives are commonly used today, including Linux and MacOS.
+
+Linux powers
+* 90% of global cloud infrastructure
+* 100% of the world's top 500 high performance computers
+* 97% of embedded and IoT devices
+
+---
+*Bash* and similar shells
+* are the primary way of interacting with most production Linux systems
+* empower you to quickly and easily navigate the system, manipulate files, and automate tasks
+
+---
+### So what is the shell?
+
+A *shell* is any user interface/program that takes an input from the user, translates it into instructions that the operating system can understand, and conveys the output back to the user.
+
+---
+There are various types of user interfaces:
+
+- graphical user interfaces (GUI)
+- touch screen interfaces
+- command line interfaces (CLI)
+
+---
+### And what is Bash?
+
+We'll be focusing on command line interfaces (CLI), more
+specifically Bash, which stands for the Bourne Again SHell.
+
+On Windows: open the **Git Bash** or **Windows Terminal** app
+On MacOS or Linux: open the **Terminal** app
+
+On newer macs, the default shell is zsh, which is almost identical to Bash.
+
+---
+### Clearing up an abundance of terminology
+
+
+
+
+
+ 
+
+---
+### Clearing up an abundance of terminology
+
+
+---
+### Clearing up an abundance of terminology
+
+
+---
+### Clearing up an abundance of terminology
+
+
+---
+### Clearing up an abundance of terminology
+
+
+---
+### Let's get started!
+
+First, we'll open our terminal. As mentioned earlier, this is most
+likely called terminal and can be found by searching our
+computer, which on a Mac would be through cmd + space
+
+---
+Let's take a look at the terminal. What do we notice?
+
+- last login
+- name
+- location
+- shell
+
+---
+### Looking at the Shell
+Let's start with a few commands and see what happens in our
+terminal.
+
+```bash
+$ echo Rachael
+$ date
+$ cal
+$ lksjfs
+```
+
+---
+- What happens when we type something that does not exist?
+- What happens with errors?
+
+---
+# Getting help and accessing documentation
+Bash includes built-in documentation for all commands
+
+```bash
+$ man ls
+```
+
+Retrieve the **man**ual for each commands using `man`.
+* Many manuals are also available online
+
+
+---
+View a list of commonly used Bash commands
+
+```bash
+$ help
+```
+
+---
+# Navigate Files / Directories
+
+---
+## Directories
+
+Let's try three commands that help us navigate our system:
+
+1. When using Bash, we always have a *working directory*:
+
+```bash
+$ pwd
+```
+
+`pwd` prints our current working directory. If we ever need to know
+where we are, we can execute this command.
+
+---
+2. To know what files and folders exist in our working directory,
+ we can use the code below:
+
+```bash
+$ ls
+```
+
+---
+3. We can change the working directory using the following command:
+
+```bash
+$ cd
+```
+
+By default, `cd` changes your *working directory* to your *home
+directory*. You can also use `cd` to set your *working directory* by
+including the desired *pathname*
+
+```bash
+$ cd Desktop
+```
+
+---
+
+```bash
+$ cd Desktop
+```
+
+Note #1: In this example
+* We can change the behaviour of the `cd` command by providing *arguments*
+* By default, `cd` changes the *working directory* to our *home directory*
+* By adding `Desktop` after the `cd` command, we change to the `Desktop` directory instead
+* Most other bash commands have their own *arguments* that allow you to modify the behaviour and effect of the command
+
+---
+
+Let's try using a *pathname argument* with the `ls` command too!
+
+```bash
+$ cd
+$ ls Desktop
+```
+
+---
+
+```bash
+$ cd Desktop
+```
+
+Note #2:
+* we were able to refer to the `Desktop` directory using only its directory name because it existed within our *working directory* at the time the command was *called*
+* in this context, `Desktop` is a *relative pathname*
+* to refer to paths outside our working directory, use the full path instead
+
+
+If we wanted to change the working directory to a directory
+outside of our working directory, we would need to specify an *absolute pathname*:
+
+```bash
+$ cd /Users/rachellam/Documents
+$ cd /c/Users/simeo/Downloads
+```
+
+---
+## Paths
+
+As we've seen, directory names separated by slashes are paths.
+There are two types of paths, _absolute_ and _relative_.
+
+- An *absolute pathname* begins at the *root directory* and
+ includes each directory, separated by slashes until the
+ desired directory or file is reached.
+- A *relative pathname* starts from the current *working directory* and
+ uses symbols `.` or `..` to represent relative positions in the
+ file tree.
+
+---
+Using `cd` and `pwd` let's take a look at how we can use
+*absolute* and *relative pathnames*.
+
+```bash
+$ cd /usr/bin
+$ pwd
+```
+
+```bash
+$ cd /usr
+$ pwd
+```
+
+```bash
+$ cd ..
+$ pwd
+```
+
+---
+## Working with Files / Directories
+
+We're going to learn some basic commands to begin some
+preliminary coding. We'll also be using these throughout the
+module, so it's important to understand how they work now:
+
+- create directory `mkdir`
+- create an empty file `touch`
+- copy `cp`
+- move and rename `mv`
+- remove `rm`
+
+---
+## Commands
+
+---
+### mkdir
+
+First let's make a directory. It's important to remember what
+directory you're working in currently, because that's where the
+new directory will be made. Let's assume for now, we're working
+on our Desktop.
+
+```bash
+$ mkdir my_directory
+```
+
+We can also create multiple directories at the same time:
+
+```bash
+$ mkdir dir1 dir2 dir3
+```
+
+---
+### touch
+
+We can also make new empty files from the command line.
+Using `touch`, we can make a new file in our
+*working directory*.
+
+```bash
+$ touch file1
+```
+
+We can also create a specific file type by adding the extension:
+
+```bash
+$ touch file1.txt
+```
+
+---
+### cp
+
+Now we're going to copy a file that we have in our *working directory*. It
+can be any file but remember to include the extension or if it
+has multiple characters, special characters and spaces, to wrap
+it in quotes.
+
+```bash
+$ cp file1 file2
+```
+
+---
+We can also copy files or directories into a directory.
+
+```bash
+$ cp file1 dir1/
+```
+
+And all files from one directory into another using *wildcards*:
+
+```bash
+$ cp dirl/* dir2
+```
+
+---
+#### Wildcards
+*Wildcards* enable us to use commands on more than one file at a time.
+The `*` is a placeholder that represents zero or more characters when used in a *pathname*.
+
+For example:
+* `./*` matches all files and folders in the current directory
+* `./*.txt` matches all files and folders that have a txt extension in the current directory
+* `/home/simeo/project1_*` matches all files and folders that begin with `project1_` in the `/home/simeo` directory
+
+---
+*Wildcards* are one of many reasons why bash so powerful!
+
+Many of the features in bash empower you to work with a large number of files easily.
+
+
+---
+There are some useful *options* that accompany `cp`:
+| Option | Description |
+| ------ | ------------------------------------------------------------- |
+| -i | Before overwriting an existing file, prompt the user for confirmation. |
+| -R | Recursively copy directories and their contents. |
+| -v | Display informative messages as the copy is performed. |
+
+---
+### mv
+
+The mv command enables us to move and rename files and
+directories, depending on how it's used. In th example below, `mv` renames `file1` to `file2`.
+
+Rename a file:
+```bash
+$ mv file1 file2
+```
+
+Here, `mv` moves `file1` from the *working directory* into `./dir1`:
+```bash
+$ mv file1 dir1
+```
+
+---
+We can also move directories into other directories:
+
+```bash
+$ mv dir1 dir2
+```
+
+---
+
+```bash
+$ mv dir1 dir2
+```
+
+In this case, if `dir2` exists, `dir1` will be moved into `dir2` (eg. from `./dir1` to `./dir2/dir1`).
+
+If `dir2` does not exist, `dir1` will be renamed to `dir2`.
+
+In both cases the entire directory will be affected (moved into another directory, or renamed), rather than the contents.
+
+---
+Let's say we're in the directory `Desktop` and we just moved
+`file1` into `dir1` but now we want to put it back in `Desktop`. How would we move a file out of a directory into another one? Unfortunatly we can't just say
+
+```bash
+$ mv file1 Desktop
+```
+
+because `file1` does not exist in `Desktop` any more and the command will try and rename `file1` to `Desktop`.
+
+---
+The answer involves using *absolute pathnames* and the tilde `~` notation:
+
+```
+$ mv dir1/file1 ~/Desktop
+```
+
+The `~` is shortform for your *home directory*.
+
+---
+If we just wanted to move `file1` into `dir2` (if `dir2` is in our *working directory*), we could type:
+
+```bash
+$ mv dir1/file1 dir2
+```
+
+---
+What if we want to move just the contents of dir1 to another
+directory rather than the whole folder?
+
+HINT: it is very similar to copying (`cp`).
+
+---
+Move just the contents of dir1 to another
+directory rather than the whole folder:
+
+```bash
+$ mv dir1/* dir2
+```
+
+This is a combination of the directory `dir1`, pathnames `/` and wildcards `*`. Here, `dir1/*` takes the all the contents of `dir1` and puts it in `dir2`.
+
+---
+We could also use the same technique to specify certain files to move rather than all of them.
+
+How would we move all txt files from `dir1` into `dir2`?
+
+---
+#### Questions?
+
+We're starting to combine our knowledge of files, directories and pathnames with some basic commands. How do we feel up to this point?
+
+---
+### rm
+
+To remove files we use the command `rm`. Because we're now
+deleting files, it's important that you're sure of what you're deleting because there is no way to undo. Fortunately!! there
+are ways to do this.
+
+```bash
+$ rm file1
+```
+
+Without specifying any *options*, `file1` will be deleted
+without any feedback.
+
+---
+To ensure we want to delete something, we can use the option `-i` (interactive) that we learned earlier.
+
+```bash
+$ rm -i file1
+```
+
+This will prompt a question asking us if we want to delete `file1`. We can respond with `y` (yes) or `n` (no).
+
+---
+If we want to delete a directory, we need to use the option `-r` (recursive) as we did when copying (`cp`). This will recursively delete everything inside of the directory and the directory itself.
+
+```bash
+$ rm -r dir1
+```
+
+---
+If we're specifying multiple deletions and a directory does not exist, the shell will tell us. If we don't want that message, we can add the `-option`, `-f` (force). Force will override `-i` if it is included.
+
+1. How do you delete multiple directories?
+2. What happens if you delete multiple directories with `-i`?
+3. What happens if you delete multiple directories with `-i` but one does not exist?
+
+---
+Remember, it's extremely important to remember that you cannot undo `rm`. This means, if you start using wildcards to specify filenames and don't include `-i`, you could delete things by accident. For example, let's say you want to delete all `.txt` files in a directory:
+
+```bash
+$ rm *.txt
+```
+
+If you accidently add a space between `*` and `.txt`,the `rm` command will delete all the files in the directory and then try to find a `.txt` file which does not exist because it delete everything.
+
+
+---
+## Working with text files
+---
+Output the contents of any text file using `cat`
+
+```bash
+$ cat file1.txt
+```
+
+* Quick way to preview file contents
+* Note, this might flood your terminal if the file is too big.
+
+---
+Write the output of a command to a text file using `>` or `>>`
+
+```bash
+$ ls >> dirlist.txt
+```
+
+* `>` replaces the destination file (deletes existing content)
+* `>>` appends to the destination file
+
+---
+
+We can also write custom content
+
+```bash
+$ echo "Hello, world!" > myfile.txt
+```
+
+---
+We can also edit text files in the command line using `nano`
+
+```bash
+$ nano file1.txt
+```
+
+To exit `nano`, press Control + X. The shortcuts are also shown at the bottom of the terminal while in the `nano` editor, where `^` denotes the Control key.
+
+---
+For more complex edits, we can launch Visual Studio Code directly from the command line.
+
+```bash
+$ code file1.txt
+```
+
+Note: MacOS users may need to setup the `code` command first.
+
+---
+## Bash scripts
+---
+We can write down a list of commands in a *script*, useful for
+* A set of commands we need to frequently *execute* together
+* Sharing commands with others
+
+A bash *script* is a text file with commands on different lines.
+* bash will *execute* each command in sequence
+
+---
+Lines that begin with a `#` are *comments* that are ignored by bash.
+* Use *comments* to annotate your thought process
+
+```bash
+# copy text files from temp directory
+cp tempdir/*.txt data/
+
+# delete the rest of the temporary files
+rm tempdir/*
+```
+
+---
+Bash scripts usually have a special *comment* as the very first line that indicates which shell should be used to run the script.
+* This is also known as the sh-bang (ha**sh** symbol + exclamation mark/**bang**)
+
+Typically, the shell used is bash:
+```bash
+#!/bin/bash
+
+# do stuff
+cp file1 dir2/
+```
+
+---
+
+Execute a script by running:
+```bash
+$ bash myscript.sh
+```
diff --git a/04_instructional_team/dsi_certificates_theme.css b/04_instructional_team/dsi_certificates_theme.css
deleted file mode 100644
index 7d4f43a31..000000000
--- a/04_instructional_team/dsi_certificates_theme.css
+++ /dev/null
@@ -1,51 +0,0 @@
-/* dsi_certificates_theme.css */
-/* @theme dsi_certificates_theme */
-
-@import 'uncover';
-
-img[alt~="center"] {
- display: block;
- margin: 0 auto;
-}
-
-
-p {
- text-align: left;
- font-size: 35px
-}
-ul {
- margin: 0;
- font-size: 35px;
-}
-table {
- font-size: 35px;
-}
-ol {
- margin: 0;
- font-size: 35px;
-}
-
-blockquote {
- border-left: 10px solid #ccc;
- margin: 1.5em 10px;
- padding: 0.5em 30px;
- quotes: "\201C""\201D""\2018""\2019";
-}
-
-blockquote:before {
- color: #ccc;
- content: none;
- font-size: 4em;
- line-height: 0.1em;
- margin-right: 0.25em;
- vertical-align: -0.4em;
-}
-
-blockquote:after{
- content: none;
-}
-
-footer {
- margin-bottom: 0px;
- text-align: left;
-}
diff --git a/04_instructional_team/markdown_slides/unix_slides.md b/04_instructional_team/markdown_slides/unix_slides.md
deleted file mode 100644
index cb0ab49cc..000000000
--- a/04_instructional_team/markdown_slides/unix_slides.md
+++ /dev/null
@@ -1,376 +0,0 @@
----
-marp: true
-theme: dsi_certificates_theme
-_class: invert
-paginate: true
----
-
-# Unix Shell
-
-```
-$ echo "Data Sciences Institute"
-```
-
----
-## Unix
-
-### What is Unix?
-
-Unix was created in 1970, and since then, has branched into other versions, including Linux. Linux was created from Unix with very similar features, although there are some minor differences in commands.
-
-Unix shells, more specifically Bash, are powerful tools for quickly and easily navigating and manipulating files, scaling automated tasks, accessing Git and processing data.
-
----
-### So what is the shell?
-
-The shell is any user interface/program that takes an input from the user, translates it into instructions that the operating system can understand, and conveys the output back to the user.
-
----
-There are various types of user interfaces:
-
-- graphical user interfaces (GUI)
-- touch screen interfaces
-- command line interfaces (CLI)
-
----
-### And what is Bash?
-
-We'll be focusing on command line interfaces (CLI), more
-specifically Bash, which stands for Bourne Again SHell.
-
-We'll also need a terminal emulator to interact with the shell.
-This is most likely called "Terminal" on our menu.
-
----
-### Let's get started!
-
-First, we'll open our terminal. As mentioned earlier, this is most
-likely called terminal and can be found by searching our
-computer, which on a Mac would be through cmd + space
-
----
-Let's take a look at the terminal. What do we notice?
-
-- last login
-- name
-- location
-- shell
-
----
-### Looking at the Shell
-
-If we type echo $SHELL in our terminal, the output will tell us
-what shell we are working with. Most often, our shell will
-already be Bash but in newer Macs, it could be zsh which is
-almost identical to Bash. We can also see where Bash is
-located by typing:
-
----
-- whereis Bash
-- whence Bash
-- which Bash
-
----
-Let's start with a few commands and see what happens in our
-terminal.
-
-```
-$ echo Rachael
-$ date
-$ cal
-$ lksjfs
-```
-
----
-- What happens when we type something that does not exist?
-- What happens with errors?
-
----
-# Navigate Files / Directories
-
----
-## Directories
-
-Let's try three commands that help us navigate our system:
-
-1. First, let's run the code below and see what happens:
-
-```
-$ pwd
-```
-
-`pwd` prints our working directory. If we ever need to know
-where we are, we can execute this command.
-
----
-2. Now, let's run the code below and see again what happens:
-
-```
-$ cd
-```
-
-By default, `cd` changes your working directory to your home
-directory. You can also use `cd` to set your working directory by
-including the desired pathname
-
-```
-$ cd Desktop
-```
-
----
-In the previous example, we were able to just state `Desktop`
-because it is a directory in our working directory. If we changed
-our working directory to `Desktop`, and then wanted to change
-it again to a directory in `Desktop`, we could again just specify
-the folder.
-If we wanted to change the working directory to a directory
-outside of our working directory, we would need to specify a
-pathname:
-
-```
-$ cd /Users/rachaellam/Desktop
-```
-
----
-3. To know what files and folders exist in our working directory,
- we can use the code below:
-
-```
-$ ls
-```
-
-We can add a pathname at the end to list the contents of a
-specified directory.
-
----
-## Paths
-
-As we've seen, directory names separated by slashes are paths.
-There are two types of paths, _absolute_ and _relative_.
-
-- An absolute pathname begins at the root directory and
- includes each directory, separated by slashes until the
- desired directory or file is reached.
-- A relative pathname starts from the working directory and
- uses symbols `.` or `..` to represent relative positions in the
- file tree.
-
----
-Using `cd` and `pwd` let's take a look at how we can use
-absolute and relative pathnames.
-
-```
-$ cd /usr/bin
-$ pwd
-```
-
-```
-$ cd /usr
-$ pwd
-```
-
-```
-$ cd ..
-$ pwd
-```
-
----
-## Working with Files / Directories
-
-We're going to learn some basic commands to begin some
-preliminary coding. We'll also be using these throughout the
-module, so it's important to understand how they work now:
-
-- create directory mkdir
-- create file touch
-- copy cp
-- move and rename mv
-- remove rm
-
----
-## Commands
-
----
-### mkdir
-
-First let's make a directory. It's important to remember what
-directory you're working in currently, because that's where the
-new directory will be made. Let's assume for now, we're working
-on our Desktop.
-
-```
-$ mkdir my_directory
-```
-
-We can also create multiple directories at the same time:
-
-```
-$ mkdir dir1 dir2 dir3
-```
-
----
-### touch
-
-We can also make new files from the command line. This is
-particularly useful when we want to make scripts, which we'll
-learn a bit later. Using touch, we can make a new file in our
-working directory.
-
-```
-$ touch file1
-```
-
-We can also create a specific file type by adding the extension:
-
-```
-$ touch file1.sh
-```
-
----
-### cp
-
-Now we're going to copy a file that we have on our Desktop. It
-can be any file but remember to include the extension or if it
-has multiple characters, special characters and spaces, to wrap
-it in quotes.
-
-```
-$ cp file1 file2
-```
-
----
-We can also copy files or directories into a directory.
-
-```
-$ cp file1 dir1
-```
-
-And all files from one directory into another using wildcards:
-
-```
-$ cp dirl/* dir2
-```
-
----
-What does the `/*` in this command mean?
-
-There are some useful `βoptions` that accompany `cp`:
-| Option | Description |
-| ------ | ------------------------------------------------------------- |
-| -i | Before overwriting an existing file, prompt the user for confirmation. |
-| -R | Recursively copy directories and their contents. |
-| -v | Display informative messages as the copy is performed. |
-
----
-### mv
-
-The mv command enables us to move and rename files and
-directories, depending on how it's used. In th example below, `mv` renames file1 to file2.
-
-```
-$ mv file1 file2 (Renames file1 to file2)
-```
-
-Here, `mv` moves file1 to dir1
-
-```
-$ mv file1 dir1 (Moves file1 to dir1)
-```
-
----
-We can also move directories into other directories:
-
-```
-$ mv dir1 dir2
-```
-
----
-In this case, if `dir2` exists, `dir1` will be moved to `dir2`. If `dir2` does not exist, it will be created and `dir1` will be moved to the newly created `dir2`. In both casesm the entire directory will be moved to another/new directory, rather than the contents.
-
----
-Let's say we're in the directory `Desktop` and we just moved
-`file1` into `dir1` but now we want to put it back in `Desktop`. How would we move a file out of a directory into another one? Unfortunatly we can't just say
-
-```
-$ mv file1 Desktop
-```
-
-because `file1` does not exist in `Desktop` any more and the command will try and rename `file1` to `Desktop`.
-
----
-The answer involves using pathnames and the tilde `~` notation:
-
-```
-$ mv dir1/file1 ~/Desktop
-```
-
----
-If we just wanted to move `file1` into `dir2` (if `dir2` is in our working directory), we could type:
-
-```
-$ mv dir1/file1 dir2
-```
-
----
-What if we want to move just the contents of dir1 to another
-directory rather than the whole folder? HINT: it is very (exactly) similar to copying (`cp`).
-
-```
-$ mv dir1/* dir2
-```
-
----
-This is a combination of the directory `dir1`, pathnames `/` and wildcards `*`. Here, `di1/*` takes the all the contents of `dir1` and puts it in `dir2`.
-
-We could also use the same techqniue to specify certain files to move rather than all of them. How do you think this would be done?
-
----
-#### Questions
-
-- We're starting to combine our knowledge of files, directories and pathnames with some basic commands. How do we feel up to this point?
-
----
-### rm
-
-To remove files we use the command `rm`. Because we're now
-deleting files, it's important that you're sure of what you're deleting because there is no way to undo. Fortunately!! there
-are ways to do this.
-
-```
-$ rm file1
-```
-
-Without specifying any `-options`, `file1` will be deleted
-without any feedback.
-
----
-To ensure we want to delete something, we can use the option `-i` (interactive) that we learned earlier.
-
-```
-$ rm -i file1
-```
-
-This will prompt a question asking us if we want to delete `file1`. We can respond with `y` (yes) or `n` (no).
-
----
-If we want to delete a directory, we need to use the option `-r` (recursive) as we did when copying (`cp`). This will recursively delete everything inside of the directory and the directory itself.
-
-```
-$ rm -r dir1
-```
-
----
-If we're specifying multiple deletions and a directory does not exist, the shell will tell us. If we don't want that message, we can add the `-option`, `-f` (force). Force will override `-i` if it is included.
-
-1. How do you delete multiple directories?
-2. What happens if you delete multiple directories with `-i`?
-3. What happens if you delete multiple directories with `-i` but one does not exist?
-
----
-Remember, it's extremely important to remember that you cannot undo `rm`. This means, if you start using wildcards to specify filenames and don't include `-i`, you could delete things by accident. For example, let's say you want to delete all `.txt` files in a directory:
-
-```
-$ rm *.txt
-```
-
-If you accidently add a space between `*` and `.txt`,the `rm` command will delete all the files in the directory and then try to find a `.txt` file which does not exist because it delete everything.
diff --git a/04_this_cohort/additional_resources/.keep b/04_this_cohort/additional_resources/.keep
new file mode 100644
index 000000000..945c9b46d
--- /dev/null
+++ b/04_this_cohort/additional_resources/.keep
@@ -0,0 +1 @@
+.
\ No newline at end of file
diff --git a/04_this_cohort/live_code/.keep b/04_this_cohort/live_code/.keep
new file mode 100644
index 000000000..945c9b46d
--- /dev/null
+++ b/04_this_cohort/live_code/.keep
@@ -0,0 +1 @@
+.
\ No newline at end of file
diff --git a/README.md b/README.md
index 028a3b71c..be615fd54 100644
--- a/README.md
+++ b/README.md
@@ -4,7 +4,7 @@
* [Description](#description)
* [Learning Outcomes](#learning-outcomes)
-* [Assignments](#assignments)
+* [Activities](#activities)
* [Contacts](#contacts)
* [Delivery of the Learning Module](#delivery-of-the-learning-module)
* [Schedule](#schedule)
@@ -12,7 +12,7 @@
* [Resources](#resources)
+ [Cheat sheet](#cheat-sheet)
+ [Videos](#videos)
- + [How to get help](#how-to-get-help)
+ + [How to Get Help](#how-to-get-help)
* [Folder Structure](#folder-structure)
## Description
@@ -22,44 +22,51 @@ This module introduces the Unix shell language and covers file and directory nav
Participants will acquire problem-solving skills through live coding sessions. Additionally, they will explore the concept of reproducibility and its integration into their work.
## Learning Outcomes
-
By the end of the module, participants will be able to:
* Comfortably access and navigate the terminal
* Create, modify and delete directories and files
-## Assignments
-1. [The Secret Password Assignment](https://github.com/UofT-DSI/shell/blob/main/02_assignments/assignment.md)
+## Activities
+This module has two types of activities.
+1. Assignments are mandatory, and form part of your evaluation.
+1. Practice problems are not assessed, but are provided to you for extra practice. We encourage you to work on them together and discuss solutions during Work Periods and on the Slack!
+### Assignments
Participants should review the [Assignment Submission Guide](https://github.com/UofT-DSI/onboarding/blob/main/onboarding_documents/submissions.md) for instructions on how to complete assignments in this module.
+Assignments are typically due on the Sunday following the module's live learning session.
+
+1. [Shell script assignment](./02_activities/assignments/assignment_instructions.md)
+
+### Practice Problems
+1. [Shell Basics](https://uoft-dsi.github.io/shell/interactive_problems.html#shell_basics)
+1. [Shell Moderate](https://uoft-dsi.github.io/shell/interactive_problems.html#shell_moderate)
+1. [Shell Advanced](./02_activities/practice/shell_advanced/shell_advanced.md)
+
+
## Contacts
-**Questions can be submitted to the _#cohort-3-help_ channel on Slack**
+**Questions can be submitted to the #cohort-7-help channel on Slack**
* Technical Facilitator:
- * **Simeon Wong** (he/him)
- simeonm.wong@utoronto.ca
+ * **Simeon Wong**
+ me@simeon.dev
* Learning Support Staff:
- * **Michaela Drouillard** (she/her)
- michaela.drouillard@mail.utoronto.ca
- * **Julia Gallucci** (she/her)
- julia.gallucci@mail.utoronto.ca
- * **Emma Teng**
- e.teng@mail.utoronto.ca
+ * **Dmytro Bonislavskyi**
+ dmytro.bonislavskyi@gmail.com
+ * **Gayathri Girish Kumar**
+ gayathri.girishkumar@mail.utoronto.ca
+ * **Xindi Zhang**
+ xindi.zhang@mail.utoronto.ca
Β
## Delivery of the Learning Module
-This module will include live learning sessions and optional, asynchronous work periods. During live learning sessions, the Technical Facilitator will introduce and explain key concepts and demonstrate core skills. Learning is facilitated during this time. Before and after each live learning session, the instructional team will be available for questions related to the core concepts of the module. Optional work periods are to be used to seek help from peers, the Learning Support team, and to work through the homework and assignments in the learning module, with access to live help. Content is not facilitated, but rather this time should be driven by participants. We encourage participants to come to these work periods with questions and problems to work through.
+This module will include live learning sessions and optional, asynchronous work periods. During live learning sessions, the Technical Facilitator will introduce and explain key concepts and demonstrate core skills. Learning is facilitated during this time. Before and after each live learning session, the instructional team will be available for questions related to the core concepts of the module. Optional work periods are to be used to seek help from peers, the Learning Support team, and to work through the practice problems and assignments in the learning module, with access to live help. Content is not facilitated, but rather this time should be driven by participants. We encourage participants to come to these work periods with questions and problems to work through.
Β
Participants are encouraged to engage actively during the learning module. They key to developing the core skills in each learning module is through practice. The more participants engage in coding along with the instructional team, and applying the skills in each module, the more likely it is that these skills will solidify.
-## Schedule
-
-||Day 1|Day 2|Day 3|Day 4|Day 5|
-|---|---|---|---|---|---|
-|Week 1|Live Learning Session 1 (Shell)|Live Learning Session 2 (Shell)|Live Learning Session 3 ([Git & GitHub](https://github.com/UofT-DSI/git))|Work Period 1|Work Period 2|
Β
## Requirements
@@ -67,7 +74,7 @@ Participants are encouraged to engage actively during the learning module. They
* Participants are encouraged to ask questions, and collaborate with others to enhance their learning experience.
* Participants must have a computer and an internet connection to participate in online activities.
* Participants must not use generative AI such as ChatGPT to generate code in order to complete assignments. It should be used as a supportive tool to seek out answers to questions you may have.
-* We expect Participants to have completed the steps in the [onboarding repo](https://github.com/UofT-DSI/onboarding/).
+* We expect participants to have completed the steps in the [onboarding repo](https://github.com/UofT-DSI/onboarding/).
* We encourage participants to default to having their camera on at all times, and turning the camera off only as needed. This will greatly enhance the learning experience for all participants and provides real-time feedback for the instructional team.
## Resources
@@ -83,27 +90,55 @@ Feel free to use the following as resources:
- [Deleting Files and Directories](https://www.youtube.com/watch?v=-L3XeZPwj_Y)
- [Bash in 100 seconds](https://www.youtube.com/watch?v=I4EWvMFj37g)
-### How to get help
-
-
-+### How to Get Help +#### 1. Gather information about your problem +- Copy and paste your error message +- Copy and paste the code that caused the error, and the last few commands leading up to the error +- Write down what you are trying to accomplish with your code. Include both the specific action, and the bigger picture and context +- (optional) Take a screenshot of your entire workspace + +#### 2. Try searching the web for your error message +- Sometimes, the error has common solutions that can be easy to find! + - This will be faster than waiting for an answer +- If none of the solutions apply, consider asking a Generative AI tool + - Paste your code, the error message, and a description of your overall goals + +#### 3. Try asking in your cohort's Slack help channel +- Since we're all working through the same material, there's a good chance one of your peers has encountered the same error, or has already solved it +- Try searching in the DSI Certificates Slack help channel for whether a similar query has been posted +- If the question has not yet been answered, post your question! + - Describe your the overall goals, the context, and the specific details of what you were trying to accomplish + - Make sure to **copy and paste** your code, your error message + - Copying and pasting helps: + 1. Your peers and teaching team quickly try out your code + 1. Others to find your question in the future + +#### Great resources on how to ask good technical questions that get useful answers +- [Asking for Help - The Odin Project](https://www.theodinproject.com/lessons/foundations-asking-for-help) +- [How do I ask a good question? - Stack Overflow](https://stackoverflow.com/help/how-to-ask) +- [The XY problem: A question pitfall that won't get useful answers](https://xyproblem.info/) +- [How to create a minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) ## Folder Structure Below is an outline of the folder structure for this module: -```markdown +``` . -βββ 01_slides -βββ 02_assignments -βββ 03_homework -βββ 04_instructional_team +βββ .github +βββ 01_materials +βββ 02_activities +βββ 03_instructional_team +βββ 04_this_cohort +βββ .gitignore βββ LICENSE -βββ README.md -βββ steps_to_ask_for_help.png +βββ README.md + ``` +* **.github**: Contains issue templates and pull request templates for the repository. +* **materials**: Module slides and interactive notebooks (.ipynb files) used during learning sessions. +* **activities**: Contains graded assignments and ungraded practice problems to apply concepts covered in the learning module. +* **instructional_team**: Resources for the instructional team. +* **this_cohort**: Additional materials for this cohort. +* **.gitignore**: Files to exclude from this folder, specified by the Technical Facilitator +* **LICENSE**: The license for this repository. +* **README**: This file. -* **slides:** Module slides as PDF files. -* **homework:** Homework to practice concepts covered in learning modules. -* **assignments:** Assignments. -* **instructors:** This folder guides Technical Facilitators and the Learning Support team on teaching methodologies and content delivery. -* README: This file! -* .gitignore: Files to exclude from this repo, specified by the instructing team.