+
+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/dsi_logo_v4.svg b/03_instructional_team/markdown_slides/images/dsi_logo_v4.svg
new file mode 100644
index 000000000..2c575f823
--- /dev/null
+++ b/03_instructional_team/markdown_slides/images/dsi_logo_v4.svg
@@ -0,0 +1,656 @@
+
+
\ No newline at end of file
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/03_instructional_team/markdown_slides/optional_unix_slides.md b/03_instructional_team/markdown_slides/optional_unix_slides.md
index c0411a268..5ddc4b9b7 100644
--- a/03_instructional_team/markdown_slides/optional_unix_slides.md
+++ b/03_instructional_team/markdown_slides/optional_unix_slides.md
@@ -1,7 +1,6 @@
---
marp: true
theme: dsi_certificates_theme
-_class: invert
paginate: true
---
# Advanced Unix Shell
diff --git a/03_instructional_team/markdown_slides/themes/dsi_certificates_theme.css b/03_instructional_team/markdown_slides/themes/dsi_certificates_theme.css
new file mode 100644
index 000000000..a209091bf
--- /dev/null
+++ b/03_instructional_team/markdown_slides/themes/dsi_certificates_theme.css
@@ -0,0 +1,42 @@
+/* @theme dsi_certificates_theme */
+@import 'default';
+
+section { position: relative; }
+
+/* Logo β bottom-right */
+section::after {
+ content: "";
+ position: absolute;
+ right: 0px;
+ bottom: 0px;
+ width: 325px;
+ height: 70px;
+ background-image: url("./images/dsi_logo_v4.svg");
+ background-repeat: no-repeat;
+ background-position: right bottom;
+ background-size: contain;
+
+ /* Anti-aliasing improvements */
+ image-rendering: auto;
+ transform: translateZ(0);
+ will-change: transform;
+ backface-visibility: hidden;
+
+ pointer-events: none;
+}
+
+/* Make tables smaller in Marp slides */
+section table {
+ font-size: 0.8em !important;
+ line-height: 1.2 !important;
+}
+
+section table th,
+section table td {
+ padding: 0.25em 0.5em !important;
+}
+
+/* Optional: slightly smaller headers too */
+section table th {
+ font-size: 0.9em !important;
+}
\ No newline at end of file
diff --git a/03_instructional_team/markdown_slides/unix_slides.md b/03_instructional_team/markdown_slides/unix_slides.md
index 4f5c3b2b2..5a4f25d06 100644
--- a/03_instructional_team/markdown_slides/unix_slides.md
+++ b/03_instructional_team/markdown_slides/unix_slides.md
@@ -1,10 +1,10 @@
---
marp: true
+theme: dsi_certificates_theme
style: |
section {
font-family: Inter, -apple-system, BlinkMacSystemFont, 'Helvetica Neue', sans-serif;
}
-_class: invert
paginate: true
---
@@ -52,6 +52,26 @@ 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!
diff --git a/README.md b/README.md
index de8bbe0f9..cc5d54cb3 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
@@ -30,46 +30,41 @@ By the end of the module, participants will be able to:
## Activities
This module has two types of activities.
1. Assignments are mandatory, and form part of your evaluation.
-1. Homework is not assessed, but are provided to you for extra practice. We encourage you to check each other's homework solutions during Work Periods or ask a Learning Support!
+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)
-### Homework
-1. [Shell Homework](./02_activities/homework/homework.sh)
+### 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-4-help_ channel on Slack**
+**Questions can be submitted to the #cohort-8-help channel on Slack**
* Technical Facilitator:
- * **Simeon Wong** (he/him)
- simeonm.wong@utoronto.ca
+ * **Simeon Wong**
+ me@simeon.dev
* Learning Support Staff:
- * **Emma Teng** (she/her)
- e.teng@mail.utoronto.ca
- * **Sidra Bushra** (she/her)
- contact.sidra.bushra@gmail.com
- * **Pedram Asli** (he/him)
- pedram.aliniayeasli@gmail.com
+ * **Dmytro Bonislavskyi**
+ dmytro.bonislavskyi@gmail.com
+ * **Moniz Chan**
+ chanmoniz526@gmail.com
+ * **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
@@ -77,7 +72,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/blob/main/environment_setup/README.md).
* 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
@@ -93,7 +88,7 @@ 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
@@ -113,8 +108,8 @@ Feel free to use the following as resources:
- 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
+ 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)
@@ -122,11 +117,6 @@ Feel free to use the following as resources:
- [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)
-#### Getting help: A summary
-
-
-- ## Folder Structure Below is an outline of the folder structure for this module: ``` @@ -138,15 +128,17 @@ Below is an outline of the folder structure for this module: βββ 04_this_cohort βββ .gitignore βββ LICENSE -βββ README.md -βββ steps_to_ask_for_help.png +βββ SETUP.md +βββ 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, exercises, and homework to practice concepts covered in the learning module. +* **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. -* **steps_to_ask_for_help.png**: Guide on how to ask for help. +* **SETUP.md**: Contains the steps required to set up this repo for the module. +* **README.md**: This file. + diff --git a/SETUP.md b/SETUP.md new file mode 100644 index 000000000..a803e4b7d --- /dev/null +++ b/SETUP.md @@ -0,0 +1,11 @@ +## Setup + +Before using this repo, make sure youβve completed the [environment setup guide](https://github.com/UofT-DSI/onboarding/blob/main/environment_setup/README.md), which installs the core tools youβll need for this module, such as: + +- Git +- Git Bash (for Windows) +- Visual Studio Code + +This module does not require any additional packages. + +Once thatβs done, simply open your terminal (macOS/Linux) or Git Bash (Windows), and youβre ready to begin this module. \ No newline at end of file