diff --git a/content/guides/sandstone/_index.md b/content/guides/sandstone/_index.md
deleted file mode 100644
index 8e7b551ba04c140a930aba3426d4e5ac2b160f5b..0000000000000000000000000000000000000000
--- a/content/guides/sandstone/_index.md
+++ /dev/null
@@ -1,51 +0,0 @@
-+++
-title = "Sandstone"
-description =  "How to use HCC's sandstone environment"
-weight = "45"
-+++
-
-
-### Overview
-
-The HCC Sandstone environment is a GUI interface to the Crane cluster featuring a file browser, text editor, web terminal and SLURM script helper,
-
-To login to the Sandstone environment, go to [crane.unl.edu](https://crane.unl.edu) in your web browser and sign in using your HCC Login Info and DUO authentication.
-
-Upon login, you will land at the File Browser.
-
-
-### File Browser
-The file broswer allows you to view, access, and transfer files on Crane. On the left side you will have your available spaces, both your home and work directories. In the upper right, you have buttons to upload files, create a file, and create a directory. 
-
-{{< figure src="/images/SandstonefileBrowserOver.png" height="300" >}}
-
-Clicking on either will change your current directory to either your home or work directory and display your user/group usage and quotas. You can navigate directories by clicking through them. 
-
-{{< figure src="/images/SandstonefileOptions.png" height="300" >}}
-
-Clicking on a file or directory will bring up some options such as the permissions and actions to do such as editing the file, duplicating or moving it, deleting it, and downloading it.  
-
-### Editor
-The editor is a basic text editor that allows you to have multiple files loaded and manipulate the files. A small file explorer is available on the left side to access more files. There are similar actions available for files above the mini file browser. 
-
-{{< figure src="/images/Sandstoneeditor.png" height="300" >}}
-
-Like most text editors, basic functions exist to undo and redo changes, find and replace, and most importantly, to save the file. 
-
-{{< figure src="/images/SandstoneedtiorDropDown.png" height="300" >}}
-
-### Terminal
-
-The terminal gives you access to the linux command line on crane, similar to what you would have if you SSH'd directly into Crane. Once the login and quote screen, you can enter commands and interact as you would with a standard terminal.
-{{< figure src="/images/SandstoneTerminal.png" height="300" >}}
-
-### Slurm Assist
-
-Slurm assist is a tool to help create and run slurm submit scripts. The first step is to select a base profile from the profile dropdown menu. Options will appear and the directives will automatically appear. The options are editable to better fit to your specific job with more details found in our submitting jobs documentation. After the directives are filled out, you can then add the commands to start your job in the script section. To save the job, select 'save script for later' and save the script in a known location for later.
-{{< figure src="/images/SandstoneSASettings.png" height="300" >}}
-From here, you can also schedule the script recently create, by selecting "Schedule Job". A confirmation will appear with the Job ID and then an instruction on how to view the status of your job.
-{{< figure src="/images/SandstoneJobConf.png" height="150" >}}
-{{< figure src="/images/SandstoneSAStatus.png" height="300" >}}
-You can view the progress of other jobs from slurm assist by going to the status page. Here you will see the State of the job, its ID, name, group name, runtime, and the start and end times. 
-{{< figure src="/images/SandstoneSAStatusPage.png" height="150" >}}
-{{< figure src="/images/SandstoneSAStatuses.png" height="300" >}}
\ No newline at end of file
diff --git a/content/office_hours/_index.md b/content/office_hours/_index.md
deleted file mode 100644
index 74ea06891b5cc7bfb18368e6ec3fe6ea4eb4958e..0000000000000000000000000000000000000000
--- a/content/office_hours/_index.md
+++ /dev/null
@@ -1,16 +0,0 @@
-+++
-title = "Contact Us"
-description = "HCC Contact Information"
-weight = "90"
-+++
-
-If you have questions, please contact us at
-{{< icon name="envelope" >}}[hcc-support@unl.edu] (mailto:hcc-support@unl.edu)
-or stop by one of our locations.
-
-|                  Lincoln                        |                     Omaha          |
-| ----------------------------------------------- | ---------------------------------- |
-| 118 SHOR<br>1100 T St<br>Lincoln, NE 68588-0150 | 1110 S 67th St<br>Omaha, NE 68106  |
-| [Map](https://maps.google.com/maps?q=Schorr+Center%E2%80%8E+University+of+Nebraska-Lincoln,+Lincoln,+NE+68508) | [Map](https://maps.google.com/maps?cid=15059268209840552421) |
-
-Or contact one of us [directly](https://hcc.unl.edu/contact-us).
diff --git a/content/quickstarts/_index.md b/content/quickstarts/_index.md
index 704737d90190c5556a8c45f90ab23a82f2d1691b..d2f1201d7a2cd269d3625cc8576b1251852e5f91 100644
--- a/content/quickstarts/_index.md
+++ b/content/quickstarts/_index.md
@@ -3,14 +3,8 @@ title = "Quickstarts"
 weight = "10"
 +++
 
-The quick start guides require that you already have a HCC account. You can get a HCC account by applying on the [HCC website] (http://hcc.unl.edu/newusers/).
-
-After you recieve an email stating your account has been created, you will need to setup DUO at either our [Lincoln](https://maps.unl.edu/SHOR) or [Omaha](https://pki.nebraska.edu/new/pages/about-pki/maps-directions-and-parking) office. More details can be found on our [Setting up and Using Duo]({{<relref "setting_up_and_using_duo">}}) page.
-
-Once you have DUO setup, you can connect to either Crane or Tusker using ssh. For Mac, Linux, and Widnows 10, you can use the *ssh* command in the terminal or command prompt. For Windows versions 8.1 and prior, you can use [PuTTY](https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html). For more details on how to connect to Crane or Tusker, or how to tranfers files to and from them, visit our [How to Connect]({{<relref "connecting">}}) page.
-
-To submit work to Crane or Tusker, you would use either the SLURM or HTCondor and a submit script. The submit scripts tell the scheduler, either SLURM or HTCondor, what parameters to use such as resources to request and where to output the results of your job. The script will also contain the neccesarry commands in order to start the job itself. Submitting jobs and the configurations of the submit scripts can be viewed in more detail on our [Submitting Jobs]({{<relref "submitting_jobs">}}) page, with specific details on [SLURM's documentation](https://slurm.schedmd.com/pdfs/summary.pdf) and [HTCondor's documentation](http://research.cs.wisc.edu/htcondor/manual/v8.6/2_5Submitting_Job.html)
-
-Many times HCC users will use specific applications, programs, or compile source code to run on HCC clusters. All software on the clusters require being loaded in with the *module* command. If a piece of software is not offered through module, users can request software to be installed and become available. For more details on running applications, refer to our [Running Applications]({{<relref "running_applications">}}) page.
+The quick start guides require that you already have a HCC account.  You
+can get a HCC account by applying on the
+[HCC website] (http://hcc.unl.edu/newusers/)
 
 {{% children %}}
diff --git a/content/quickstarts/hpc_intro.md b/content/quickstarts/hpc_intro.md
deleted file mode 100644
index 8b05136d9e871bff17bf4328fdea4e0e1d77ab0b..0000000000000000000000000000000000000000
--- a/content/quickstarts/hpc_intro.md
+++ /dev/null
@@ -1,22 +0,0 @@
-+++
-title = "Introduction to HPC"
-description = "What is a cluster and what is HPC"
-weight = "1"
-+++
-High-Performance Computing is the use of groups of computers to solve computations that a user or group would not be able to solve in a reasonable time-frame on their own desktop or laptop. This is often achieved by splitting one large job amongst numerous cores or 'workers'. This is similar to how a skyscraper is built by numerous individuals rather than a single person. Many fields take advantage of HPC including bioinformatics, chemistry, materials engineering, and newer fields such as educational psychology and philosophy.
-
-HPC clusters consist of four primary parts, the login node, management node, workers, and a central storage array. The cullmination of these parts create a high performance cluster that can recieve work from the schedulers.
-{{< figure src="/images/cluster.png" height="450" >}}
-##### [Source](https://training.h3abionet.org/technical_workshop_2015/?page_id=403)
-
-#### Login Node:
-Users will automatically land on the login node when they log in to the clusters. You will [submit jobs] ({{< ref "/quickstarts/submitting_jobs" >}}) using one of the schedulers and pull the results of your jobs. Running jobs on the login node directly will be stopped so others can use the login node to submit jobs.
-</br></br>
-#### Management Node: 
-The management node contains and runs the schedulers and other utilities for managing the cluster.
-</br></br>
-#### Worker Nodes:
-The worker nodes are what run and process your jobs that are submitted from the schedulers. Through the use of the schedulers, more work can be efficiently done by squeezing in all jobs possible for the resources requested throughout the nodes. They also allow for fair use computing by making sure one user or group is not using the entire cluster at once and allowing others to use the clusters.
-</br></br> 
-#### Central Storage Array:
-The central storage array allows all of the nodes within the cluster to have access to the same files without needing to transfer them around. HCC has three arrays mounted on the clusters with more details [here]({{< ref "/guides/handling_data" >}}).
\ No newline at end of file
diff --git a/content/quickstarts/setting_up_and_using_duo.md b/content/quickstarts/setting_up_and_using_duo.md
index 61218e53e4fc2eefeb5119b8b4aafaa919657def..04f0847dc6979387f136f44fe301904ad152c419 100644
--- a/content/quickstarts/setting_up_and_using_duo.md
+++ b/content/quickstarts/setting_up_and_using_duo.md
@@ -75,11 +75,11 @@ this example, the choices are Duo Push notification, SMS message, or
 phone call. Choosing option 1 for Duo Push, a request to verify the
 login will be sent to the user's smartphone.
 
-{{< figure src="/images/DUORequest.jpg" height="350" >}}
+{{< figure src="/images/5832716.png" height="350" >}}
 
 Simply tap `Approve` to verify the login.
 
-{{< figure src="/images/DUOApprove.jpg" height="350" >}}
+{{< figure src="/images/5832717.png" height="350" >}}
 
 {{% notice warning%}}**If you receive a verification request you didn't initiate, deny the 
 request and contact HCC immediately via email at
diff --git a/static/images/5832716.png b/static/images/5832716.png
new file mode 100644
index 0000000000000000000000000000000000000000..831f07225445bcdcd15dbae25004b205aee279d7
Binary files /dev/null and b/static/images/5832716.png differ
diff --git a/static/images/5832717.png b/static/images/5832717.png
new file mode 100644
index 0000000000000000000000000000000000000000..c64d22e4caf01bb59f86f1a530d5c3dc369e1d8d
Binary files /dev/null and b/static/images/5832717.png differ
diff --git a/static/images/DUOApprove.jpg b/static/images/DUOApprove.jpg
deleted file mode 100644
index 3867d9705f59b7553096b347c3356eb64d596b2e..0000000000000000000000000000000000000000
Binary files a/static/images/DUOApprove.jpg and /dev/null differ
diff --git a/static/images/DUORequest.jpg b/static/images/DUORequest.jpg
deleted file mode 100644
index 7bb783c573e4a38e69818f4376b1630a1bd7f9ad..0000000000000000000000000000000000000000
Binary files a/static/images/DUORequest.jpg and /dev/null differ
diff --git a/static/images/SandstoneJobConf.png b/static/images/SandstoneJobConf.png
deleted file mode 100644
index 483fb3d33918ffaf2151c6dab8b24cdd2231fe3b..0000000000000000000000000000000000000000
Binary files a/static/images/SandstoneJobConf.png and /dev/null differ
diff --git a/static/images/SandstoneSA.png b/static/images/SandstoneSA.png
deleted file mode 100644
index cd3f0eda5cc10d5b11ced1dc3deaf06f13410790..0000000000000000000000000000000000000000
Binary files a/static/images/SandstoneSA.png and /dev/null differ
diff --git a/static/images/SandstoneSASettings.png b/static/images/SandstoneSASettings.png
deleted file mode 100644
index 2d59dbd693a3cb8f1e37b7516d0d4028471e994c..0000000000000000000000000000000000000000
Binary files a/static/images/SandstoneSASettings.png and /dev/null differ
diff --git a/static/images/SandstoneSAStatus.png b/static/images/SandstoneSAStatus.png
deleted file mode 100644
index 57211ea430fd0c59a36e8613a76c0ba92aed5248..0000000000000000000000000000000000000000
Binary files a/static/images/SandstoneSAStatus.png and /dev/null differ
diff --git a/static/images/SandstoneSAStatusPage.png b/static/images/SandstoneSAStatusPage.png
deleted file mode 100644
index 43dbe6aece9a6e6f37681fcf6a68c658eb7aa0b8..0000000000000000000000000000000000000000
Binary files a/static/images/SandstoneSAStatusPage.png and /dev/null differ
diff --git a/static/images/SandstoneSAStatuses.png b/static/images/SandstoneSAStatuses.png
deleted file mode 100644
index 5640e4ef6879d541e21edda1d8d06b0eadaf17f6..0000000000000000000000000000000000000000
Binary files a/static/images/SandstoneSAStatuses.png and /dev/null differ
diff --git a/static/images/SandstoneTerminal.png b/static/images/SandstoneTerminal.png
deleted file mode 100644
index c60f62a3068c10bcd99a17ea532b205801562f33..0000000000000000000000000000000000000000
Binary files a/static/images/SandstoneTerminal.png and /dev/null differ
diff --git a/static/images/Sandstoneeditor.png b/static/images/Sandstoneeditor.png
deleted file mode 100644
index 253f92c78072073598c4747d13112da3f452bf0a..0000000000000000000000000000000000000000
Binary files a/static/images/Sandstoneeditor.png and /dev/null differ
diff --git a/static/images/SandstoneedtiorDropDown.png b/static/images/SandstoneedtiorDropDown.png
deleted file mode 100644
index 6f756e60edc662819e7064b51901876b046d8136..0000000000000000000000000000000000000000
Binary files a/static/images/SandstoneedtiorDropDown.png and /dev/null differ
diff --git a/static/images/SandstonefileBrowserOver.png b/static/images/SandstonefileBrowserOver.png
deleted file mode 100644
index d744a54e67515a6f3f0065d0e9ac812d3c8ae8c2..0000000000000000000000000000000000000000
Binary files a/static/images/SandstonefileBrowserOver.png and /dev/null differ
diff --git a/static/images/SandstonefileOptions.png b/static/images/SandstonefileOptions.png
deleted file mode 100644
index 0cbf6dbd7479c1b6443907b4a08435b85ce9f5d4..0000000000000000000000000000000000000000
Binary files a/static/images/SandstonefileOptions.png and /dev/null differ