summaryrefslogtreecommitdiff
path: root/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs
diff options
context:
space:
mode:
authorElizabeth Alexander Hunt <me@liz.coffee>2026-07-02 11:55:17 -0700
committerElizabeth Alexander Hunt <me@liz.coffee>2026-07-02 11:55:17 -0700
commit6bf4b90c90f15f4ab60833bddf5b5756d1a6b1f6 (patch)
treeed97e39ec77c5231ffd2c394493e68d00ddac5a4 /Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs
downloadmisc-undergrad-main.tar.gz
misc-undergrad-main.zip
Diffstat (limited to 'Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs')
-rw-r--r--Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/about.md30
-rw-r--r--Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/img/deleted_todos.pngbin0 -> 9837 bytes
-rw-r--r--Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/img/manager.pngbin0 -> 5198 bytes
-rw-r--r--Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/img/marked_todos.pngbin0 -> 12579 bytes
-rw-r--r--Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/img/mode-placement.pngbin0 -> 163378 bytes
-rw-r--r--Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/img/plugin.pngbin0 -> 9337 bytes
-rw-r--r--Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/img/save_in_normal_mode.pngbin0 -> 23613 bytes
-rw-r--r--Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/img/terminal1.pngbin0 -> 15685 bytes
-rw-r--r--Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/img/vim.pngbin0 -> 52646 bytes
-rw-r--r--Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/img/vim_window.pngbin0 -> 18686 bytes
-rw-r--r--Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/img/vimtodo.pngbin0 -> 15252 bytes
-rw-r--r--Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/img/visual_mode_sample.pngbin0 -> 32573 bytes
-rw-r--r--Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/index.md30
-rw-r--r--Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/intro.md41
-rw-r--r--Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/mov/basic-movement.mp4bin0 -> 235435 bytes
-rw-r--r--Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/mov/delete-yank.mp4bin0 -> 1355260 bytes
-rw-r--r--Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/mov/line-moving.mp4bin0 -> 420921 bytes
-rw-r--r--Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/mov/repeat.mp4bin0 -> 803738 bytes
-rw-r--r--Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/mov/replace-search.mp4bin0 -> 1698702 bytes
-rw-r--r--Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/mov/search.mp4bin0 -> 1032959 bytes
-rw-r--r--Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/mov/word-movement.mp4bin0 -> 235558 bytes
-rw-r--r--Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/quickstart.md167
-rw-r--r--Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/references.md9
-rw-r--r--Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/understanding.md205
24 files changed, 482 insertions, 0 deletions
diff --git a/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/about.md b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/about.md
new file mode 100644
index 0000000..89870ba
--- /dev/null
+++ b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/about.md
@@ -0,0 +1,30 @@
+# About Vim
+<h6>Logan</h6>
+
+Vim is a text editor, like Visual Studio Code or Notepad, but it is aimed at power users. It is a terminal-based editor, which means it does not have the UI of a graphical editor like Notepad. This makes its learning curve a little steep, but it is very worth it - editing code in Vim is significantly faster than a Graphical Editor.
+
+## History
+
+In 1988, Bram Moolenaar created a new text editor called Vim (which stands for "vi improved"). Vim was based on the vi editor, which was created in the 1970s to improve developer efficiency over command line tools like `ed`.
+
+Vim saw its first public release in 1991. Since then, it has undergone significant development, and it is now available on almost every platform - MacOS, Linux, Windows, and even the . In recent years, Vim has gained popularity as a powerful alternative to traditional text editors like Emacs, Sublime Text, and Visual Studio Code. Its large community of volunteer developers has built a large collection of plugins that are free and open source - meaning anyone can contribute to their development.
+
+## Why Use Vim?
+
+Vim is a very efficient text editor. It is designed to make editing code as fast and easy as possible. Vim is also highly configurable, so you can customize it to work exactly the way you want it to.
+
+### Never Leave The Keyboard
+
+Vim is designed to be used entirely from the keyboard without taking time to shift the hand to the mouse. This may seem strange at first, but it is actually very efficient. Once you get used to it, you will find that you can edit code much faster with Vim than with a mouse.
+
+### Vim Has One Job, And It Does It Well
+
+Vim adheres to the UNIX philosophy of "doing one thing and doing it well" - meaning that Vim is very good at editing text, but compared to programs like Emacs, its extensibility is not as big a priority.
+
+### Highly Customizable
+
+Vim is highly configurable - it even has its own programming language, VimScript, allowing users to change literally anything about the editor. Keyboard shortcuts, colors, and even the way the text is displayed are all options that are available through VimScript.
+
+### Available On Any Platform
+
+Vim is available on almost any platform. This includes Windows, macOS, Linux, and even Android - meaning you can use Vim no matter where you are.
diff --git a/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/img/deleted_todos.png b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/img/deleted_todos.png
new file mode 100644
index 0000000..6d1b0e0
--- /dev/null
+++ b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/img/deleted_todos.png
Binary files differ
diff --git a/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/img/manager.png b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/img/manager.png
new file mode 100644
index 0000000..0f0ce21
--- /dev/null
+++ b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/img/manager.png
Binary files differ
diff --git a/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/img/marked_todos.png b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/img/marked_todos.png
new file mode 100644
index 0000000..e9213ad
--- /dev/null
+++ b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/img/marked_todos.png
Binary files differ
diff --git a/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/img/mode-placement.png b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/img/mode-placement.png
new file mode 100644
index 0000000..9acdbab
--- /dev/null
+++ b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/img/mode-placement.png
Binary files differ
diff --git a/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/img/plugin.png b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/img/plugin.png
new file mode 100644
index 0000000..d0cb7ac
--- /dev/null
+++ b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/img/plugin.png
Binary files differ
diff --git a/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/img/save_in_normal_mode.png b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/img/save_in_normal_mode.png
new file mode 100644
index 0000000..0ab5baa
--- /dev/null
+++ b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/img/save_in_normal_mode.png
Binary files differ
diff --git a/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/img/terminal1.png b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/img/terminal1.png
new file mode 100644
index 0000000..af827f9
--- /dev/null
+++ b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/img/terminal1.png
Binary files differ
diff --git a/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/img/vim.png b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/img/vim.png
new file mode 100644
index 0000000..fda07c4
--- /dev/null
+++ b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/img/vim.png
Binary files differ
diff --git a/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/img/vim_window.png b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/img/vim_window.png
new file mode 100644
index 0000000..ddc16ae
--- /dev/null
+++ b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/img/vim_window.png
Binary files differ
diff --git a/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/img/vimtodo.png b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/img/vimtodo.png
new file mode 100644
index 0000000..4e262a2
--- /dev/null
+++ b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/img/vimtodo.png
Binary files differ
diff --git a/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/img/visual_mode_sample.png b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/img/visual_mode_sample.png
new file mode 100644
index 0000000..093474b
--- /dev/null
+++ b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/img/visual_mode_sample.png
Binary files differ
diff --git a/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/index.md b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/index.md
new file mode 100644
index 0000000..4c169fc
--- /dev/null
+++ b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/index.md
@@ -0,0 +1,30 @@
+# Vim
+<h6>Logan</h6>
+
+![Screenshot](img/vim.png)
+
+> Vim is a highly configurable text editor built to make creating and changing any kind of text very efficient. It is included as "vi" with most UNIX systems and with Apple OS X.
+
+> Vim is rock stable and is continuously being developed to become even better. Among its features are:
+>
+> - persistent, multi-level undo tree
+> - extensive plugin system
+> - support for hundreds of programming languages and file formats
+> - powerful search and replace
+> - integrates with many tools
+
+> \- [vim.org](https://www.vim.org/)
+
+## Using This Manual
+
+This manual is meant to serve as a quick reference for Vim, with a glance into some more advanced concepts. One should start with the [QuickStart](quickstart.md), and use [Understanding](understanding.md) as a quick reference for tasks a user would typically expect to be able complete faster with Vim than a traditional editor.
+
+Basic knowledge of using a terminal is required, and if you do not posess such skill, [learn the way of the blade](https://developer.mozilla.org/en-US/docs/Learn/Tools_and_testing/Understanding_client-side_tools/Command_line).
+
+### Pages / TOC
+
+* [Home](index.md)
+* [About Vim](about.md)
+* [Introduction](intro.md)
+* [Quick Start](quickstart.md)
+* [Understanding Vim](understanding.md)
diff --git a/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/intro.md b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/intro.md
new file mode 100644
index 0000000..1d67a13
--- /dev/null
+++ b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/intro.md
@@ -0,0 +1,41 @@
+# Introduction
+
+<h6>Alaina, Logan</h6>
+
+## Why Choose Vim for a Software Documentation Project?
+For our software documentation project we chose to write documentation for Vim. Vim is a text editor - not a text editor as would be used by storybook authors or to write papers for English class, but a text editor used by programmers.
+
+Among the Computer Science world, there is a lot of appeal in using Vim because it allows a programmer to navigate quickly and efficiently among their code without the use of the oh-so-inefficient mouse. Vim provides handy ways for inserting, changing, and deleting text. It also contains a variety of keyboard shortcuts that can make coding or doing repeated tasks on text or groups of text lightning-fast.
+
+However, Vim is also infamous for having an incredibly steep learning curve. It can often seem unintuitive to the new user, since most of Vim’s keyboard shortcuts are unlike the keyboard shortcuts of any “traditional” text editor. For instance, control + c for copy, control + v for paste, and control + s for save do not function to copy, paste, or save text in Vim. Instead, Vim has its own unique collection of shortcuts, or “commands”, whose functions are dependent on the current “mode”. Some commands are prefixed with a colon (“:”), while others are simply bound to a single key.
+
+One member of our group was already familiar with Vim when we began the project. The rest of us had to buckle down and learn how to use this text editor before we began writing our documentation. In a few CS classes at Utah State University, teachers and students have made jokes about opening Vim and than being unable to exit (thus becoming stuck in the text editor and—perhaps incapable of exiting the program in order to use a browser to google a solution—having to shut down their computer just to exit Vim! We started by learning how to exit Vim and insert text, then gradually moved on to the more fancy tasks—such as searching and replacing text, copying and pasting text, and navigating a Vim document the way a programmer would. Most of this learning was through trial-and-error, though there exist many other online resources such as Youtube tutorials and web forums, dedicated to learning Vim.
+
+## Audience
+During the planning stages of this project we decided to cater our documentation to computer scientists, specifically targeting those who have little to no previous knowledge of using Vim. If we had chosen an audience with a little more experience we could have thrown around some more jargon, but as our choice was to build our manual to serve as an introductory course of sorts we purposefully keep the jargon to a minimum in the beginning, and ramp up as we compound on previous topics.
+
+We also know that people who are learning Vim for the first time are likely to get frustrated because of its steep learning curve. We kept in mind that the typical audience searching for the type of manual we provide is composed of fellow tech people, rather than other non-technical professionals. This allowed us to keep more of a straightforward, light, and casual tone throughout the document which most readers of technical documentation would be familiar with. For example, we used exclamation points in “If you see something like this, you are good to go!” and made it seem like we were there with the user by using statements like, “For now, let’s practice adding some text to Vim.”
+
+We also knew that we would be able to use plenty of visuals in our documentation (i.e., screenshots, videos, tables), as screenshots of a terminal would make sense to those working in a tech-related field.
+
+Keeping in mind the typical reader, our manual includes only the necessities of using Vim, with some previews into the advanced concepts. Most people who want to learn to use Vim are not going to be starting with these advanced concepts, so we demonstrated basic tasks such as opening files, inserting text, navigating the document, and installing Vim. Adding such instructions is effective, as it provides our audience with a single reference of the basics in one place. Those of us learning Vim as we compiled our documentation decided that these concepts would have been the most helpful as we started out.
+
+## Appearance
+The software documentation that we wrote is formatted using Markdown. We decided to compile the documentation into a website using Mkdocs, which made it easy to streamline our formatting process. Because we used Markdown we didn’t have to remember to change the fonts and formats for our headings and text — we just let a stylesheet standardize our fonts, colors, alignment, and design. This was a much easier method to collaborate, since it would have been more difficult to format something in a word processor with 5 of us editing the documentation at different times. It was also good practice for us to use some Computer Science type skills, because most modern software documentation is usually presented as a website or blog, and not as a physical document.
+
+We chose the styles that we did with the simple reasoning that they were pleasing to look at. The styles were also minimalist in design, making the reader’s job of focusing on the contents of the document easier.
+
+## Our Experience
+Next time we would probably make decisions faster and get done a little earlier. A lot of time was spent learning Vim while concurrently deciding how to organize the document, the content, and making assignments to group members. It often felt there was less time and organization on the days that we didn’t have class and met as a group to work on writing each task and capability.
+
+While it was typically a difficult process overall, we all (hopefully) enjoyed learning Vim. Or, at least, we are all happy to be more familiar with it — and, especially, know how to exit it.
+
+Since there are so many different things that you can do with Vim, it was difficult to decide just how much of Vim we were going to cover in our documentation. We also had to decide if we wanted to write a tutorial for our documentation, or if we just wanted to include the information and then let the users try the commands by themselves. We did use examples (with example text) for the users to be able to see how Vim would appear during certain steps of the process, but we did not do a full-scale tutorial. It would have been nice to build a cohesive, full-scale tutorial to walk our users through, but it ultimately would have made doing group work difficult in our short span of time and busy schedules.
+
+# General Warnings
+<h6>Eric</h6>
+Vim is a very efficient text editor when a significant amount of time is dedicated to learning its features. Until then, proficiency will come slowly, and with consistent practice. Be patient with yourself as you learn the ins and outs of Vim, and try to learn and use a few new features every day.
+
+# Equipment and Supplies
+<h6>Eric</h6>
+In order to use Vim, a computer is required with either Linux, MacOS, or Windows installed. If Vim is not already installed ([see Quickstart](./quickstart.md)), then an internet connection is required for install.
diff --git a/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/mov/basic-movement.mp4 b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/mov/basic-movement.mp4
new file mode 100644
index 0000000..9a4d136
--- /dev/null
+++ b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/mov/basic-movement.mp4
Binary files differ
diff --git a/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/mov/delete-yank.mp4 b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/mov/delete-yank.mp4
new file mode 100644
index 0000000..9d47dd1
--- /dev/null
+++ b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/mov/delete-yank.mp4
Binary files differ
diff --git a/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/mov/line-moving.mp4 b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/mov/line-moving.mp4
new file mode 100644
index 0000000..18e6985
--- /dev/null
+++ b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/mov/line-moving.mp4
Binary files differ
diff --git a/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/mov/repeat.mp4 b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/mov/repeat.mp4
new file mode 100644
index 0000000..c56ce49
--- /dev/null
+++ b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/mov/repeat.mp4
Binary files differ
diff --git a/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/mov/replace-search.mp4 b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/mov/replace-search.mp4
new file mode 100644
index 0000000..820a450
--- /dev/null
+++ b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/mov/replace-search.mp4
Binary files differ
diff --git a/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/mov/search.mp4 b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/mov/search.mp4
new file mode 100644
index 0000000..64e3323
--- /dev/null
+++ b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/mov/search.mp4
Binary files differ
diff --git a/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/mov/word-movement.mp4 b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/mov/word-movement.mp4
new file mode 100644
index 0000000..a909aa6
--- /dev/null
+++ b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/mov/word-movement.mp4
Binary files differ
diff --git a/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/quickstart.md b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/quickstart.md
new file mode 100644
index 0000000..9dadcd4
--- /dev/null
+++ b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/quickstart.md
@@ -0,0 +1,167 @@
+# Quick Start
+
+Welcome to the QuickStart guide for Vim. This guide will help you get the bare bones knowledge of using Vim and will get you to the point where you can embark on the long but fun, journey to using Vim as your main text editor!
+
+## Installation
+
+<h6>Eric</h6>
+
+### MacOS
+
+Using [homebrew](https://brew.sh/), you can install the latest version of Vim with `brew install vim`, though an older version comes pre-installed on MacOS if you don't wish to use homebrew.
+
+### Windows
+
+If you are on a Windows machine, navigate to [vim.org](https://www.vim.org), [downloads](https://www.vim.org/download.php), and select your version. Afterwards, it will be accessable from the `cmd` Terminal, or if chosen in the installation, can be launched from the Desktop Icon.
+
+### Linux
+
+#### Fedora
+
+```bash
+sudo dnf install vim
+```
+
+#### Arch Linux
+
+```bash
+sudo pacman -S vim
+```
+
+#### Debian/Ubuntu
+
+```bash
+sudo apt install vim
+```
+
+### Verify Installation
+
+Verify that Vim is installed by opening a terminal and running `vim`. If you see something like this, you are good to go! Now you can exit Vim by typing `:q`.
+
+![Vim Screenshot](./img/vim_window.png)
+
+## A Quick Adventure - Making A Todo File
+
+### Creating a New Todo List
+<h6>Tyler</h6>
+
+Creating a new file with vim is really simple just type:
+
+```bash
+vim todo.txt
+```
+
+Whenever you pass a file that doesn't exist vim creates it for you and opens it up for editing.
+
+### Navigating the cursor
+<h6>Tyler</h6>
+
+Vim does not support the usage of a mouse so movement of the cursor is handled entirely with the keyboard.
+The basic movements of the cursor are as follows:
+
+| Command | Description |
+| ------- | ----------------------------------------- |
+| `h` | `(←)` Move the cursor left one character |
+| `j` | `(↓)` Move the cursor down one line |
+| `k` | `(↑)` Move the cursor up one line |
+| `l` | `(→)` Move the cursor right one character |
+
+### Adding a Todo
+
+<h6>Eric</h6>
+
+Now that you have opened a file in Vim, it's time to insert text. For now, press the `i` key to enter into Insert Mode. More details on the different modes will be covered a little further on. For now, lets practice adding some text to Vim.
+
+Inserting text works just like any other text editor, so try and insert some text, following this format:
+
+![TODO List](./img/vimtodo.png)
+
+This will probably end up with something to the likes of:
+
+```
+My Todos
+- [ ] Eat Vegetables
+- [ ] Take a Nap
+- [ ] Learn Vim
+```
+
+#### A Quick Aside: Normal vs Insert Mode
+<h6>Logan</h6>
+
+Insert mode, used to actually type text into the document, can be accessed by pressing `i`. To exit this mode, press the `ESC` key.
+
+For now, think of Normal Mode as the mode to move the text cursor around, and Insert Mode as how to actually insert text into the document (this will be further explained in [Understanding Vim](understanding.md)).
+
+### Saving
+
+###### Authored by Alaina D
+
+Once you have added text to a file (see "Adding a Todo" if you are not sure how to insert text), you will want to save the file for later editing.
+
+In Vim, there are three common ways to save a file:
+
+- using `:w`
+- using `:x`
+- using `:wq`
+
+Before you attempt any of the above commands, hit `ESC` (the "escape" key) to make sure Vim is in Normal mode. You should see a blank line in bottom of your terminal (hint: if the bottom of your terminal says "-- INSERT --", you are **not** in Normal mode).
+
+The following is a screenshot of Vim in normal mode:
+
+![Vim Screenshot](./img/save_in_normal_mode.png)
+
+Once Vim is in normal mode, you can enter any of the previously mentioned "save" commands (`:w`, `:x`, or `:wq`), followed by the `ENTER` key.
+
+**Note**: These commands are case-sensitive (the letters in each command must be lower-case).
+<br><br>
+###### Using `:w`
+
+The command `:w` will save (write) the file that you are currently editing. If you use `:w` to write (save) your file, your file will remain open in Vim. This command is great for saving a file that you would like to continue editing.
+
+###### Using `:x`
+
+The command `:x` will save (write) the file that you are currently editing. If you use `:x` to write (save) your file, your file will only be saved _if_ changes have been made to the file. This command will not change the modification timestamp of the file if you have not made changes to the file after opening it. If you use `:x` to save your file, Vim will exit when you hit enter.
+
+###### Using `:wq`
+
+The command `:wq` will save (write) the file that you are currently editing, _and_ will exit Vim after the file is saved. If you want to save and quit Vim all in the same command, `:wq` should be your weapon of choice.
+<br><br>
+
+**NOTE:** `:wq` is not **_the only_** command to use to exit Vim--it is merely a convenient way to save a file and exit Vim at the same time.
+
+### Exiting
+
+###### Trevor
+
+The Command for exiting vim is `:q`. If the file has been edited since it was opened, `:q` will not work, instead giving a warning about unwritten changes. To bypass this, you can add an `!` to the command, making it `:q!`, which will quit without saving.
+
+### Reopening The File
+<h6>Tyler</h6>
+
+After saving (using `:w`, `:x`, `:wq`, etc.), re-open the todo file to prove that the changes made have been saved:
+
+```bash
+vim todo.txt
+```
+
+### Mark A Todo As Done
+<h6>Tyler</h6>
+
+Navigate the cursor between the brackets of the task you want to mark as done and enter Insert mode `i`.
+
+Mark the task done by entering a capital X.
+
+Then, enter Normal mode by pressing the `Escape` key, press `j` to go down a line to the next todo, and mark it as done the same way.
+
+![Vim Screenshot](./img/marked_todos.png)
+
+### Delete A Todo
+<h6>Tyler</h6>
+
+One way to remove a todo from the list is to delete the entire line. To do this, get into Normal mode and navigate the cursor to the line you want to delete. Then, press the `d` key twice: `dd`, to remove the line.
+
+![Vim Screenshot](./img/deleted_todos.png)
+
+## Further Understanding Vim
+
+Amazing! You've made it this far. Let's take a look at how you can do more by [understanding Vim](understanding.md).
diff --git a/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/references.md b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/references.md
new file mode 100644
index 0000000..351e421
--- /dev/null
+++ b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/references.md
@@ -0,0 +1,9 @@
+# References
+
+_Vim tutorial_. Tutorials Point. (n.d.). Retrieved November 6, 2022, from https://www.tutorialspoint.com/vim/index.htm
+
+Kenlon, S. (n.d.). _How to install vim plugins_. Opensource.com. Retrieved November 6, 2022, from https://opensource.com/article/20/2/how-install-vim-plugins
+
+_Vim - The Ubiquitous Text Editor_. Welcome Home : Vim Online. (n.d.). Retrieved November 6, 2022, from https://www.vim.org/
+
+Matias, G. (n.d.). _A brief history of Vim_. Building VTS. Retrieved November 6, 2022, from https://buildingvts.com/a-brief-history-of-vim-1476ec4a6eb8
diff --git a/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/understanding.md b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/understanding.md
new file mode 100644
index 0000000..f54312e
--- /dev/null
+++ b/Homework/engl3085/Technical-Comm/vim-docs-for-3085/docs/understanding.md
@@ -0,0 +1,205 @@
+# Vim is Modal
+<h6>Logan</h6>
+
+- Hopefully you've done the [Quick Start](intro.md) and are ready to learn more about Vim. Here we will go over some of the concepts behind Vim.
+
+Vim is "modal", meaning that how one interacts with the editor is dependant on the current mode. In other words, modes can be likened to "states", and the state Vim is in determines what actions are available to the user.
+
+This documentation will cover three such "modes": Normal Mode, Insert Mode, and Visual Mode.
+
+The current mode, if it is not normal mode, is displayed in the bottom left corner:
+
+![Vim Modes](./img/mode-placement.png)
+
+## Insert Mode
+<h6>Tyler</h6>
+
+Insert mode is the mode in which text is entered into the document. In this mode, the keyboard is interpreted as text input, and the text cursor is visible.
+Common ways of entering insert mode are listed below.
+
+| Command | Description |
+| ------- | --------------------------------------------- |
+| `i` | Insert before the cursor |
+| `I` | Insert at the beginning of the line |
+| `a` | Append after the cursor |
+| `A` | Append at the end of the line |
+| `o` | Create a new line below the cursor and insert |
+| `O` | Create a new line above the cursor and insert |
+
+## Visual Mode
+
+<h6>Authored by Alaina D</h6>
+
+Visual mode is the mode in which text is selected. In this mode, the text cursor is visible, and the text is highlighted. To enter visual mode, press `v` while in Normal mode (hint: to switch to normal mode, hit `ESC`--then press `v` to get to Visual mode).
+
+In Visual mode, you may highlight text (using your cursor, of course) by navigating around within your file. While you are in visual mode, Vim will highlight the text that is currently selected. For this reason, Visual mode is very useful for selecting multiple words, lines, or paragraphs of text. You can even select the entire file's text in Visual mode, if you would like to.
+
+While Vim is in Visual mode, text will become selected as you move your cursor around the document. Vim will automatically highlight the selected text, which makes it easier (in real-time) for you to see which text you are selecting.
+
+![Vim Screenshot](./img/visual_mode_sample.png)
+
+If you would like to deslect your text, hit `ESC` to go back to Normal mode, navigate your cursor to your desired location, and then re-enter visual mode by pressing `v`.
+
+### Navigation in Visual Mode
+
+In Visual mode, you are free to navigate Vim similar to how you navigate in Normal mode. Below this paragraph, you will find a table of helpful navigation commands in Vim (the commands work the same in normal mode and in Visual mode).
+
+#### Simple Navigation
+
+| Command | Description |
+| ------- | ----------------------------------------- |
+| `h` | `(←)` Move the cursor left one character |
+| `j` | `(↓)` Move the cursor down one line |
+| `k` | `(↑)` Move the cursor up one line |
+| `l` | `(→)` Move the cursor right one character |
+
+#### Word-By-Word Navigation/By-Character Navigation
+
+| Command | Description |
+| ------- | -------------------------------------------------------------------------------------------------------------------- |
+| `w` | Move the cursor to the beginning of the next word |
+| `e` | Move the cursor to the end of the next word |
+| `b` | Move the cursor to the beginning of the previous word |
+| `4j` | Move the cursor down 4 lines (you may combine any number with j or k to move up \_\_\_ number of lines |
+| `3h` | Move the cursor to the left 3 characters (you may combine any number with h or l to move \_\_\_ number of characters |
+
+#### Multi-line Navigation/Line-By-Line Navigation
+
+| Command | Description |
+| ----------- | -------------------------------------------------------------------------------------------------------------------- |
+| `0` | Move the cursor to the beginning of the line |
+| `$` | Move the cursor to the end of the line |
+| `^` | Move the cursor to the first non-whitespace character of the line |
+| `SHIFT + g` | Move the cursor to the end of the file |
+| `gg` | Move the cursor to the beginning of the file |
+| `4j` | Move the cursor down 4 lines (you may combine any number with j or k to move up \_\_\_ number of lines |
+| `3h` | Move the cursor to the left 3 characters (you may combine any number with h or l to move \_\_\_ number of characters |
+
+#### Deleting Text in Visual Mode
+
+To delete your selected block of text, first enter visual mode using `v` (as mentioned above). Once you have selected the text that you would like to delete, press `d` for delete. When you press `d`, the section of text which you have selected will be deleted. If you would like to undo your deletion, press `u` to undo.
+
+**NOTE: when you use `d` to delete text, Vim will automatically return to Normal mode (this means that you will need to press `v` to get back to Visual mode)**
+
+#### Copy/Paste Text Using Visual Mode
+
+To copy text in Visual mode, you must first enter Visual mode (using `v`, as mentioned above). You will then select your desired block of text by moving your cursor over the desired text. Once you have selected the text that you want to copy, press 'y' to copy the text. Once you have copied your selected text, you may return to normal mode and use `SHIFT + p` or `p` to paste your desired text (`SHIFT + p` will paste text _before_ your cursor, while `p` will paste text _after_ your cursor). Please note that the text will be pasted wherever your cursor happens to be at the moment.
+
+**NOTE: when you use `y` to copy (yank) text, Vim will automatically return to Normal mode (this means that you will need to press `v` to get back to Visual mode)**
+
+## Normal mode
+
+<h6>Logan</h6>
+
+Normal mode is the default mode when Vim is first run, and the mode which a user will spend most of their time, as it is the "main" mode; a user enters other modes through Normal mode, and exiting those modes brings the users back to Normal mode. such as navigating text, delete and yank (vim-ology for "cut" and "paste") text, and changing into other .
+
+Normal mode is also the mode in which a user enters other modes, such as Insert Mode and Visual Mode. When in any other mode, a user can always go back to Normal mode by pressing the `<Esc>` key.
+
+### Cursor Movement
+
+In normal mode, no keyboard input is interpreted as text input. Instead, the keyboard is used to move the text cursor around the document.
+
+As an example, the text cursor can be moved using the `h`, `j`, `k`, and `l` keys. These keys are the most efficient way to navigate the cursor due to their placement on the homerow.
+
+Note that this collection is not exhaustive, but rather a collection of the most common and useful commands. For a full list of commands, see this [Vim Cheat Sheet](https://vim.rtorr.com/).
+
+#### The Essentials
+
+| Command | Description |
+| ------- | ----------------------------------------- |
+| `h` | `(←)` Move the cursor left one character |
+| `j` | `(↓)` Move the cursor down one line |
+| `k` | `(↑)` Move the cursor up one line |
+| `l` | `(→)` Move the cursor right one character |
+
+![type:video](./mov/basic-movement.mp4)
+
+#### By Word
+
+| Command | Description |
+| ------- | ----------------------------------------------------- |
+| `w` | Move the cursor to the beginning of the next word |
+| `e` | Move the cursor to the end of the next word |
+| `b` | Move the cursor to the beginning of the previous word |
+
+![type:video](./mov/word-movement.mp4)
+
+#### By Line
+
+| Command | Description |
+| ------- | ----------------------------------------------------------------- |
+| `0` | Move the cursor to the beginning of the line |
+| `$` | Move the cursor to the end of the line |
+| `^` | Move the cursor to the first non-whitespace character of the line |
+
+![type:video](./mov/line-moving.mp4)
+
+### Actions
+
+"Actions" in normal mode are commands that perform some sort of action on the text. These can be anything from deleting text to toggling the case of some text.
+
+Typically there are two parts of a action in normal mode: the "operator" and a (sometimes optional) "motion". The operator is the action to be performed, and the motion is the text to perform the action on.
+
+For example, with the command `d` as the "delete" operator, and the motion `w` as the "forward word" motion, together, form the command `dw`. This would delete any text under the cursor until the end of the word.
+
+#### Repeating
+
+In normal mode, actions and movements can be repeated by prefixing them with a number. For example, `3j` will move the cursor down three lines, and `10w` would go forward ten words.
+
+![type:video](./mov/repeat.mp4)
+
+#### Cut/Copy & Paste
+
+The action of copying a piece of text and pasting it somewhere else is a very common task in text editing, and Vim has a few ways to do this. Though, Vim uses the terminology "yank" and "put" instead of "copy" and "paste".
+
+1. To yank (or copy) text, the `y` operator is used in conjunction with a motion.
+2. To cut text, the `d` operator is used in conjunction with a motion.
+3. To put (or paste) text, the `p` operator is used. This operator puts the text that was last yanked or cut at the cursor.
+
+A specific property exists on the yank and cut operators: repeating them will yank or cut the entire line. For example, `yy` will yank the entire line, and `dd` will cut the entire line.
+
+Therefore, the following are all examples of valid commands:
+
+| Command | Description |
+| ------- | ----------------------------------------------------------------- |
+| `yy` | Yank (copy) the entire line |
+| `dd` | Cut (delete) the entire line |
+| `y$` | Yank (copy) from the cursor to the end of the line |
+| `dw` | Cut (delete) the word under the cursor |
+| `p` | Put (paste) the text that was last yanked or cut after the cursor |
+
+![type:video](./mov/delete-yank.mp4)
+_Examples of the `d` and `y` operators, and repeating actions_
+
+#### Searching
+
+Vim has a built-in search feature that allows users to search for text in the document. The search feature is accessed by pressing the `/` key, and the search term is entered after the `/` key.
+
+![type:video](./mov/search.mp4)
+
+#### Replacing Text
+
+Vim also has a powerful search and replace feature which can accessed via the `:%s` command.
+
+The `:%s` command is similar the `sed` UNIX utility (see [this](https://unix.stackexchange.com/questions/159367/using-sed-to-find-and-replace) stackexchange post as a quick example of the syntax) and takes two regex joined by forward slashes: the first is the text to search for, and the second is the text to replace it with. For example, `:%s/foo/bar/` will replace the first instance of `foo` with `bar` in the document.
+
+![type:video](./mov/replace-search.mp4)
+
+# Making Vim Your Own: Installing Plugins
+<h6>Eric</h6>
+While Vim in it's own element can be a powerful tool, it is still just a text editor. Plugins can be installed to customize and improve the Vim editor, and add more functionality that Vim doesn't have on it's own. Vim version 8+ is required, and you can check by launching Vim.
+
+![Vim Screenshot](./img/vim_window.png)
+
+ Vim looks in a specific directory, ~/.vim/pack/[whatever you want]/start.
+ If this PATH doesn't exist, create one using the `mkdir` command in the terminal, or navigating to the directory in your file manager, and put any downloaded packages inside of it.
+
+ ![File Structure in Terminal](./img/terminal1.png)
+
+ Terminal file structure
+
+ ![File Stucture in Manager](./img/manager.png)
+
+ Manager file structure
+
+ Vim will find them at boot, and they will be applied when it is launched. You can find packages anywhere on the internet, in the form of zipped folders, repositories, etc. A great website to find ones is [Vim Awesome](https://vimawesome.com).