diff --git a/docs/getting-started/using-ale/isd-generate.md b/docs/getting-started/using-ale/isd-generate.md
index f3cc92ee8b7a5ebc61e99b6750aac56f81f47257..deb812a6d819333d4492cdb0d806cba59e8ab5e9 100644
--- a/docs/getting-started/using-ale/isd-generate.md
+++ b/docs/getting-started/using-ale/isd-generate.md
@@ -178,7 +178,7 @@ isd_generate --version
 
 ## Setting Up NAIF Data
 
-For use of NAIF Data with ISIS, see [The ISIS Data Area](https://github.com/DOI-USGS/ISIS3/blob/dev/README.md#the-isis-data-area).  For use of NAIF data with ALE, continue below.
+For use of NAIF Data with ISIS, see the [ISIS Data Area](../../how-to-guides/environment-setup-and-maintenance/isis-data-area.md).  For use of NAIF data with ALE, continue below.
 
 ### Downloading NAIF SPICE Data with wget
 
diff --git a/docs/getting-started/using-isis-first-steps/isis-faq.md b/docs/getting-started/using-isis-first-steps/isis-faq.md
index e9e82e9d6da62a7dba005f0d2593a2b7d7867d37..dcb88c3c8de890dbd8a90831b04eea065ed9a6f0 100644
--- a/docs/getting-started/using-isis-first-steps/isis-faq.md
+++ b/docs/getting-started/using-isis-first-steps/isis-faq.md
@@ -76,9 +76,9 @@
     Some ISIS software updates include mission specific command updates motivated by new information (updated kernels, format changes, etc.) from mission teams. When the software is updated the data area should also be updated, see [Mission Specific Data Downloads][5].
 
     [3]: https://isis.astrogeology.usgs.gov/Application/presentation/Tabbed/spiceinit/spiceinit.html
-    [4]: https://github.com/DOI-USGS/ISIS3?tab=readme-ov-file#full-isis-data-download
-    [5]: https://github.com/DOI-USGS/ISIS3?tab=readme-ov-file#mission-specific-data-downloads
-    [6]: https://github.com/DOI-USGS/ISIS3?tab=readme-ov-file#isis-spice-web-service
+    [4]: ../../how-to-guides/environment-setup-and-maintenance/isis-data-area.md#full-download
+    [5]: ../../how-to-guides/environment-setup-and-maintenance/isis-data-area.md#mission-specific-data-areas
+    [6]: ../../how-to-guides/environment-setup-and-maintenance/isis-data-area.md#isis-spice-web-service
     [7]: ../../getting-started/using-isis-first-steps/locating-and-ingesting-image-data.md
 
 ???+ abstract "Additional Helpful Docs"
diff --git a/docs/how-to-guides/ale-developer-guides/creating-ale-drivers.md b/docs/how-to-guides/ale-developer-guides/creating-ale-drivers.md
index 79186da695088d4a504fde2f0dc18b12eac66046..7edea5b15fd0b17fc8498478c7b4b64275236cdd 100644
--- a/docs/how-to-guides/ale-developer-guides/creating-ale-drivers.md
+++ b/docs/how-to-guides/ale-developer-guides/creating-ale-drivers.md
@@ -4,7 +4,7 @@ This guide provides step-by-step instructions for creating an ALE driver for an
 
 ## Prerequisites 
 1. Clone and build [ISIS](https://github.com/USGS-Astrogeology/ISIS3/wiki/Developing-ISIS3-with-cmake) locally.
-1. Download base and mission kernels related to the driver you plan to implement.  One means of downloading this kernels is through ISIS's [downloadIsisData script](https://github.com/DOI-USGS/ISIS3/blob/dev/README.md#partial-download-of-isis-base-data).
+1. Download base and mission kernels related to the driver you plan to implement.  One means of downloading this kernels is through ISIS's [downloadIsisData script](../../how-to-guides/environment-setup-and-maintenance/isis-data-area.md#downloading-isisdata).
 1. Fork [the ALE repository](https://github.com/USGS-Astrogeology/ale)
 1. Clone from your fork (with the recursive flag to clone submodules as well):
     ```sh
diff --git a/docs/how-to-guides/environment-setup-and-maintenance/installing-isis-via-anaconda.md b/docs/how-to-guides/environment-setup-and-maintenance/installing-isis-via-anaconda.md
index 04970023cf9f9948e12a6d9a5f8fc1e879d067dc..fd06a64cb7586aafc60b0ba03679ad0468135d81 100644
--- a/docs/how-to-guides/environment-setup-and-maintenance/installing-isis-via-anaconda.md
+++ b/docs/how-to-guides/environment-setup-and-maintenance/installing-isis-via-anaconda.md
@@ -1,124 +1,270 @@
-# Installation
+# Installing ISIS
 
-This installation guide is for ISIS users interested in installing ISIS (3.6.0)+ through conda.
+## Prerequisites
 
-## ISIS Installation With Conda
+??? "Conda"
 
-1. Download either the Anaconda or Miniconda installation script for your OS platform. Anaconda is a much larger distribution of packages supporting scientific python, while Miniconda is a minimal installation and not as large: [Anaconda installer](https://www.anaconda.com/download), [Miniconda installer](https://conda.io/miniconda.html)
-1. If you are running on some variant of Linux, open a terminal window in the directory where you downloaded the script, and run the following commands. In this example, we chose to do a full install of Anaconda, and our OS is Linux-based. Your file name may be different depending on your environment.
-    
-    ```bash
-    chmod +x Anaconda3-5.3.0-Linux-x86_64.sh
-    ./Anaconda3-5.3.0-Linux-x86_64.sh
+    If you don't have conda yet, download and install it.  We recommend getting conda through [MiniForge](https://github.com/conda-forge/miniforge?tab=readme-ov-file#miniforge).
+
+    ```sh
+    # Via Miniforge:
+    curl -L -O "https://github.com/conda-forge/miniforge/releases/latest/download/Miniforge3-$(uname)-$(uname -m).sh"
+    bash Miniforge3-$(uname)-$(uname -m).sh
     ```
-    This will start the Anaconda installer which will guide you through the installation process.
 
-1. If you are running Mac OS X, a pkg file (which looks similar to Anaconda3-5.3.0-MacOSX-x86\_64.pkg) will be downloaded. Double-click on the file to start the installation process.
-1. After the installation has finished, open up a bash prompt in your terminal window.
-1. If you have an ARM64 Mac (M1/M2) running Catalina (or later), additional prerequisites must be installed for ISIS to run in emulation:
- - Install [XQuartz](https://www.xquartz.org/). (Tested with XQuartz 2.8.5 on MacOS Catalina)
- - Install Rosetta2. From the terminal run: `/usr/sbin/softwareupdate --install-rosetta --agree-to-license`
- - Include the `# MacOS ARM64 Only` lines below
-1. Next setup your Anaconda environment for ISIS. In the bash prompt, run the following commands:
+??? "x86 emulation on ARM Macs - Rosetta"
+
+    If you have an ARM mac and want to run the x86 version of ISIS, you will need Rosetta.
 
-    ```bash
+    ```sh
+    /usr/sbin/softwareupdate --install-rosetta --agree-to-license
+    ```
     
-    #MacOS ARM64 Only - Setup the new environment as an x86_64 environment
+
+## Conda Environment
+
+=== "Native Mac/Unix"
+
+    ```sh
+    # Create conda environment, then activate it.
+    conda create -n isis 
+    conda activate isis
+    ```
+
+=== "x86 on ARM Macs"
+
+    ```sh
+    # ARM Macs Only - Setup the new environment as x86_64
     export CONDA_SUBDIR=osx-64
     
-    #Create a new conda environment to install ISIS in
-    conda create -n isis python>=3.9
-
-    #Activate the environment
+    # Create conda environment, then activate it.
+    conda create -n isis
     conda activate isis
     
-    #MacOS ARM64 Only - Force installation of x86_64 packages instead of ARM64
+    # ARM Macs Only - Force installation of x86_64 packages, not ARM64
     conda config --env --set subdir osx-64
+    ```
 
-    #Add the following channels to the environment
-    conda config --env --add channels conda-forge
-    conda config --env --add channels usgs-astrogeology
+### Channels
+
+```sh
 
-    #Verify you have the correct channels:
+# Add conda-forge and usgs-astrogeology channels
+conda config --env --add channels conda-forge
+conda config --env --add channels usgs-astrogeology
+
+# Check channel order
+conda config --show channels
+```
+
+??? warning "Channel Order: `usgs-astrogeology` must be higher than `conda-forge`"
+    
+    Show the channel order with:
+
+    ```sh
     conda config --show channels
+    ```
 
-    #You should see:
+    You should see:
 
+    ```
     channels:
         - usgs-astrogeology
         - conda-forge
         - defaults
+    ```
 
-    #The order is important.  If conda-forge is before usgs-astrogeology, you will need to run:
+    If `conda-forge` is before `usgs-astrogeology`, add usgs-astrogeology again to bring up.  Set channel priority to flexible instead of strict.
 
+    ```sh
     conda config --env --add channels usgs-astrogeology
-    
-    #Then set channel_priority to flexible in case there is a global channel_priority=strict setting
     conda config --env --set channel_priority flexible
     ```
 
-1. The environment is now ready to download ISIS and its dependencies:
+## Downloading ISIS
+
+The environment is now ready to download ISIS and its dependencies:
+
+=== "Latest Release"
 
-    ```bash
+    ```sh
     conda install -c usgs-astrogeology isis
     ```
 
-1. Finally, setup the environment variables:
+=== "LTS"
+
+    ```sh
+    conda install -c usgs-astrogeology/label/LTS isis
+    ```
+
+=== "Release Candidate"
+
+    ```sh
+    conda install -c usgs-astrogeology/label/RC isis
+    ```
+
+
+## Environmental Variables
+
+ISIS requires these environment variables to be set in order to run correctly:
+
+- `ISISROOT` - Directory path containing your ISIS install
+- `ISISDATA` - Directory path containing the [ISIS Data Area](../../how-to-guides/environment-setup-and-maintenance/isis-data-area.md)
+
+???+ example "Setting Environmental Variables"
+
+    The **Conda Env** method is recommended, and the **Python Script** automates that method:
+
+    === "Conda Env"
+
+        ??? "Requires Conda 4.8 or above"
+
+            Check your conda version, and update if needed:
 
-    ISIS requires several environment variables to be set in order to run correctly.
-    The variables include: ISISROOT and ISISDATA.
+            ```sh
+            # Check version
+            conda --version
 
-    The following steps are only valid for versions of ISIS after 4.2.0.
-    For older versions of ISIS follow the instructions in [this readme file.](https://github.com/USGS-Astrogeology/ISIS3/blob/adf52de0a04b087411d53f3fe1c9218b06dff92e/README.md)
+            # Update
+            conda update -n base conda
+            ```
 
-    There are two methods to configure the environment variables for ISIS:
+        1.  Activate your ISIS environment.  
+            ```
+            conda activate isis
 
-    A. Using `conda env config vars` *preferred*
+            # Now you can set variables with:
+            # conda config vars set KEY=VALUE
+            ```
 
-       Conda has a built in method for configuring environment variables that are specific to a conda environment since version 4.8.
-       This version number applies only to the conda package, not to the version of miniconda or anaconda that was installed.
+        1.  This command sets both required variables (fill in your `ISISDATA` path):
 
-       To determine if your version of conda is recent enough run:
+                conda env config vars set ISISROOT=$CONDA_PREFIX ISISDATA=[your data path]
 
-           conda --version
+        1.  Re-activate your isis environment. 
+            ```sh
+            conda deactivate
+            conda activate isis
+            ```
 
-       If the version number is less than 4.8, update conda to a newer version by running:
+        The environment variables are now set and ISIS is ready for use every time the isis conda environment is activated.
 
-           conda update -n base conda
 
-       The version number should now be greater than 4.8.
+    === "Python Script"
 
-       To use the built in environment variable configuration feature, first activate the environment by first running:
+        By default, running this script will set `ISISROOT=$CONDA_PREFIX` and `ISISDATA=$CONDA_PREFIX/data`:
 
-           conda activate isis
+            python $CONDA_PREFIX/scripts/isisVarInit.py
+        
+        You can specify a different path for `$ISISDATA` using the optional value:
 
-       After activation, the environment variables can be set using the syntax: `conda config vars set KEY=VALUE`.
-       To set all the environment variables ISIS requires, run the following command, updating the path to `ISISDATA` as needed:
+            python $CONDA_PREFIX/scripts/isisVarInit.py --data-dir=[path to data directory]
 
-           conda env config vars set ISISROOT=$CONDA_PREFIX ISISDATA=[path to data directory]
+        Now every time the isis environment is activated, `$ISISROOT` and `$ISISDATA` will be set to the values passed to isisVarInit.py.
+        This does not happen retroactively, so re-activate the isis environment:
 
-       To make these changes take effect, re-activate the isis environment by running:
+            conda deactivate
+            conda activate isis
 
-           conda activate isis
 
-       The environment variables are now set and ISIS is ready for use every time the isis environment is activated.
+    === "export (shell)"
+
+        `export` sets a variable in your current shell environment until you close it.  Adding `export` commands to your `.bashrc` or `.zshrc` can make them persistent.
+
+        ```sh
+        export ISISROOT=[path to ISIS]
+        export ISISDATA=[path to data]
+        ```
+
+
+    === "ISIS <4.2.0"
+
+        Use the python script per instructions from [the old readme](https://github.com/USGS-Astrogeology/ISIS3/blob/adf52de0a04b087411d53f3fe1c9218b06dff92e/README.md).
+
+
+## The ISIS Data Area
+
+Many ISIS apps need extra data to carry out their functions.  This data varies depending on the mission, and may be quite large, so it is not included with ISIS; You will need to [download it separately](../../how-to-guides/environment-setup-and-maintenance/isis-data-area.md).
+
+-----
+
+!!! success "Installation Complete"
+    
+    If you followed the above steps and didn't encounter any errors, you have completed your installation of ISIS.
+
+-----
+
+
+## Updating ISIS
+
+If ISIS was already installed with Conda, you can update it with:
+
+=== "Latest Release"
+
+    ```sh
+    conda update -c usgs-astrogeology isis
+    ```
+
+=== "LTS"
+
+    ```sh
+    conda update -c usgs-astrogeology/label/LTS isis
+    ```
+
+=== "Release Candidate"
+
+    ```sh
+    conda update -c usgs-astrogeology/label/RC isis
+    ```
+
+
+## Uninstalling ISIS
+
+To uninstall ISIS, deactivate the ISIS Conda Environment, and then remove it.  If you want to uninstall conda as well, see your conda installation's website ([Miniforge](https://github.com/conda-forge/miniforge?tab=readme-ov-file#uninstallation) if you installed conda with the above instructions).
+
+```sh
+conda deactivate
+conda env remove -n isis
+```
 
-    !!! Warning "The above method will not enable tab completion for arguments in C-Shell."
 -----
 
-    B. Using the provided isisVarInit.py script:
+## ISIS in Docker
+
+!!! quote ""
+
+    The ISIS production Dockerfile automates the conda installation process above.
+    You can either build the Dockerfile yourself or use the
+    [usgsastro/isis](https://hub.docker.com/repository/docker/usgsastro/isis)
+    image from DockerHub.
+
+    === "Prebuilt Image"
+
+        ```sh
+        docker run -it usgsastro/isis bash
+        ```
 
-       To use the default values for: `$ISISROOT` and `$ISISDATA`, run the ISIS variable initialization script with default arguments:
+    === "Building the Dockerfile"
 
-           python $CONDA_PREFIX/scripts/isisVarInit.py
 
-       Executing this script with no arguments will result in $ISISROOT=$CONDA\_PREFIX and $ISISDATA=$CONDA\_PREFIX/data. The user can specify different directories for `$ISISDATA` using the optional value:
+        Download [the production Docker file](https://github.com/DOI-USGS/ISIS3/blob/dev/docker/production.dockerfile), build, and run it:
 
-           python $CONDA_PREFIX/scripts/isisVarInit.py --data-dir=[path to data directory]
+        ```sh
+        # Build
+        docker build -t isis -f production.dockerfile .
 
-       Now every time the isis environment is activated, $ISISROOT and $ISISDATA will be set to the values passed to isisVarInit.py.
-       This does not happen retroactively, so re-activate the isis environment with one of the following commands:
+        # Run
+        docker run -it isis bash
+        ```
 
-           for Anaconda 3.4 and up - conda activate isis
-           prior to Anaconda 3.4 - source activate isis
+    ### Mounting the ISIS data area
+
+    Usually you'll want to mount an external directory containing the ISIS data.
+    The data is not included in the Docker image.
+
+    ```
+    docker run -v /my/data/dir:/opt/conda/data -v /my/testdata/dir:/opt/conda/testData -it usgsastro/isis bash
+    ```
 
+    Then [download the data](#the-isis-data-area) into /my/data/dir to make it accessible inside your
+    container.
diff --git a/docs/how-to-guides/environment-setup-and-maintenance/isis-data-area.md b/docs/how-to-guides/environment-setup-and-maintenance/isis-data-area.md
new file mode 100644
index 0000000000000000000000000000000000000000..ecb4a1c247bf4a3f07a521dc2e09131f4bede1b2
--- /dev/null
+++ b/docs/how-to-guides/environment-setup-and-maintenance/isis-data-area.md
@@ -0,0 +1,225 @@
+# Setting Up the ISIS Data Area
+
+Many ISIS apps need extra data to carry out their functions.  This data varies depending on the mission, and may be **quite large**, so it is **not included** with the ISIS binaries. It resides in the **ISIS Data Area**.
+
+??? info "More Info on the ISIS Data Area"
+
+    ### Structure
+
+    Each mission supported by ISIS has a directory with mission-specific processing data (like flat files and SPICE kernels).  There is also a base data area with shared data, and a test data area for ISIS testing and development.
+
+    #### Output of `tree -L 2 $ISISDATA`
+    ```sh
+    ~/isis_data/
+    ├── apollo15
+    │   ├── calibration
+    │   ├── kernels
+    │   └── reseaus
+    ├── apollo16
+    │   ├── kernels
+    │   └── reseaus
+    ├── base
+    │   ├── dems
+    │   ├── examples
+    │   ├── kernelTesting
+    │   └── kernels
+    ├── cassini
+    │   ├── calibration
+    │   ├── kernels
+    │   └── unitVectors
+    ├── chandrayaan1
+    │   ├── bandBin
+    │   └── kernels
+    ├── clementine1
+    │   ├── calibration
+    │   └── kernels
+    ├── dawn
+    │   └── kernels
+    ...
+    ```
+        
+
+    ### Hosting
+
+    The ISIS Data Area is hosted on a combination of AWS S3 buckets and public http servers (NAIF, Jaxa, ESA), not through conda like ISIS binaries.  The `downloadIsisData` script facilitates downloading ISIS data from various sources.
+
+    ### Versions
+
+    For ISIS 4.1.0 and above, some apps require the [`base`](#__tabbed_2_1) and/or [mission-specific](#mission-specific-data-areas) data areas, while other apps may run without them.
+
+    Apps from ISIS versions lower than 4.1.0 require the [`legacybase`](#__tabbed_2_2) area.
+
+    ### Example ISISDATA usage in ISIS Apps
+
+    - **Calibration** apps need **flat files** to do _flat field corrections_.
+    - **Map Projection** apps need **DTMs** to accurately _compute intersections_.
+    - `spiceinit` uses SPICE Data is used to _initialize ISIS cubes_.
+
+    ### Size
+
+    All the ISIS data from various missions adds up to a total of over 2TB.  But, using the [ISIS SPICE Web Service](#isis-spice-web-service) (instead of downloading all the SPICE files) reduces the necessary download to a much more manageable ~10GB base.
+
+
+## Setting the ISISDATA Environmental Variable
+
+Any location can be used for the ISIS Data Area, ISIS just needs the `$ISISDATA` environmental variable to point to it.
+
+=== "Conda"
+
+    ```sh
+    # Activate your environment (assuming it's named isis)
+    conda activate isis
+
+    # Set the variable
+    conda env config vars set ISISDATA=<path/to/isisdata>
+
+    # Reactivate your environment
+    conda deactivate
+    conda activate isis
+    ```
+
+=== "Shell"
+
+    ```sh
+    export ISISDATA=<path/to/isisdata>
+    ```
+
+
+## Downloading ISISDATA
+
+You can use the `downloadIsisData` script to download ISIS data.
+
+```sh
+# General Usage
+downloadIsisData [mission] [download destination] [optional flags]
+
+# More Info
+downloadIsisData --help
+```
+
+### Full Download
+
+To download **ALL** Isis data, including the base and all of the mission data areas:
+
+```sh
+downloadIsisData all $ISISDATA
+```
+
+!!! warning "That's a lot of data!"
+
+    Downloading *all* takes over 2TB of space!  See [Partial Downloads](#partial-downloads) if you want a smaller subset, or try the [ISIS SPICE Web Service](#isis-spice-web-service).
+
+### Partial Downloads
+
+#### The Base Data Area
+
+Some data (like DEMs and Leap Second Kernels) are shared between multiple missions; this is the base data area.
+
+If you work with camera models (using `cam2map`, `campt`, `qview`, etc.), or are using a legacy version of ISIS, we recommend downloading the base data area:
+
+=== "Current"
+
+    ```sh
+    # For ISIS versions 4.1.0 and up
+    downloadIsisData base $ISISDATA
+    ```
+
+=== "Legacy"
+
+    ```sh
+    # For ISIS versions before 4.1.0
+    downloadIsisData legacybase $ISISDATA
+    ```
+
+</br>
+
+#### Mission Specific Data Areas
+
+If you are only working with a few missions, save space by downloading just those data areas (find your download command on the following list).
+
+??? abstract "Mission Names & Download Commands"
+
+    - For versions of ISIS prior to ISIS 4.1.0, please use the `--legacy` flag.
+    
+    - Reference [`rclone.conf`](https://github.com/DOI-USGS/ISIS3/blob/dev/isis/config/rclone.conf) if you can't find/download data for your mission with one of these commands.
+
+    | Mission | Command |
+    | ------ | ------ |
+    | Apollo 15 | `downloadIsisData apollo15 $ISISDATA` |
+    | Apollo 16 | `downloadIsisData apollo16 $ISISDATA` |
+    | Apollo 17 | `downloadIsisData apollo17 $ISISDATA` |
+    | Cassini | `downloadIsisData cassini $ISISDATA` | 
+    | Chandrayaan 1 | `downloadIsisData chandrayaan1 $ISISDATA` |
+    | Clementine 1 | `downloadIsisData clementine1 $ISISDATA` |
+    | Dawn | `downloadIsisData dawn $ISISDATA` |
+    | ExoMars | `downloadIsisData tgo $ISISDATA` |
+    | Galileo | `downloadIsisData galileo $ISISDATA` | 
+    | Hayabusa 2 | `downloadIsisData hayabusa2 $ISISDATA` |
+    | Juno | `downloadIsisData juno $ISISDATA` |
+    | Kaguya | `downloadIsisData kaguya $ISISDATA` |
+    | Lunar Orbiter | `downloadIsisData lo $ISISDATA` |
+    | Lunar Reconnaissance Orbiter | `downloadIsisData lro $ISISDATA` |
+    | Mars Exploration Rover  | `downloadIsisData mer $ISISDATA` |
+    | Mariner10  | `downloadIsisData mariner10 $ISISDATA` |
+    | Messenger | `downloadIsisData messenger $ISISDATA` |
+    | Mars Express  | `downloadIsisData mex $ISISDATA` |
+    | Mars Global Surveyor  | `downloadIsisData mgs $ISISDATA` |
+    | Mars Reconnaissance Orbiter  | `downloadIsisData mro $ISISDATA` |
+    | Mars Science Laboratory  | `downloadIsisData msl $ISISDATA` |
+    | Mars Odyssey  | `downloadIsisData odyssey $ISISDATA` |
+    | Near  | `downloadIsisData near $ISISDATA` |
+    | New Horizons  | `downloadIsisData newhorizons $ISISDATA` |
+    | OSIRIS-REx  | `downloadIsisData osirisrex $ISISDATA` |
+    | Rolo  | `downloadIsisData rolo $ISISDATA` |
+    | Rosetta  | `downloadIsisData rosetta $ISISDATA` |
+    | Smart1  | `downloadIsisData smart1 $ISISDATA` |
+    | Viking 1 | `downloadIsisData viking1 $ISISDATA` |
+    | Viking 2 | `downloadIsisData viking2 $ISISDATA` |
+    | Voyager 1 | `downloadIsisData voyager1 $ISISDATA` |
+    | Voyager 2 | `downloadIsisData voyager2 $ISISDATA` |
+
+-----
+
+## ISIS SPICE Web Service
+
+ISIS can retrieve the SPICE data over the internet with a web service.
+Using the ISIS SPICE Web Service significantly reduces the size 
+of the required downloads from the data area.
+
+??? warning "Not all operations are supported by the SPICE Web Service"
+
+    Some instruments require mission data to be present for **radiometric calibration**, which is not supported by the SPICE Web Server.
+    Some programs that are designed to run an image *from ingestion through the mapping phase* do not have an option to use the SPICE Web Service. 
+
+    - **MEX HRSC** is a commonly used unsupported instrument.
+    - For info on specific apps/instruments, see the [ISIS Application Docs](https://isis.astrogeology.usgs.gov/Application/index.html).
+    
+    
+
+### Enabling the Web Service for `spiceinit`
+
+To use this instead of local SPICE data, 
+click the `WEB` check box in the `spiceinit` window. 
+Or at the command line:
+```sh
+spiceinit from=<yourimage.cub> web=yes
+```
+
+### Skipping Kernel Downloads with `downloadIsisData`
+
+#### --exclude
+
+To skip downloading the SPICE kernels, use the `exclude` argument (like a blacklist) on a mission-specific `downloadIsisData` command.  For example:
+
+    downloadIsisData cassini $ISISDATA --exclude="kernels/**"
+
+#### --include
+
+You can also use the `include` argument (like a whitelist) to partially download specific kernels. For example, to include only `ck`s and `fk`s in your LRO mission download:
+
+    downloadIsisData lro $ISISDATA --include="{ck/**,fk/**}"
+
+
+## The ISIS Test Data Area
+
+There is an ISISTESTDATA area containing files needed to run some of ISIS's older Makefile-based tests.  See [ISIS Test Data](../../how-to-guides/isis-developer-guides/obtaining-maintaining-submitting-test-data.md) for more info.
\ No newline at end of file
diff --git a/docs/how-to-guides/environment-setup-and-maintenance/spice-kernel-updates-in-isis.md b/docs/how-to-guides/environment-setup-and-maintenance/spice-kernel-updates-in-isis.md
index bce2c1bc9a313012f1f64eebc52a7c10f9a121dc..a2df1602df4e81388c5d491719ac963d4c9d9c9b 100644
--- a/docs/how-to-guides/environment-setup-and-maintenance/spice-kernel-updates-in-isis.md
+++ b/docs/how-to-guides/environment-setup-and-maintenance/spice-kernel-updates-in-isis.md
@@ -1,8 +1,8 @@
 SPICE kernels are required for the use of most ISIS applications. ISIS provides SPICE kernels for each mission
-in the ISISDATA area . For information on how to download the ISISDATA area, see: [Download Mission Data](https://github.com/DOI-USGS/ISIS3#mission-specific-data-downloads)
+in the [ISIS Data Area](../../how-to-guides/environment-setup-and-maintenance/isis-data-area.md).
 
-ISIS provides ongoing automated updates of SPICE kernels for some of its supported missions by checking for new mission kernels, and if available, distributing them via the ISISDATA area available from the rsync server. These supported missions are listed in the table below, alongside their ISIS and Mission update cadences. ‘ISIS Update’ refers to how often ISIS looks for and then distributes new SPICE kernel updates and ‘Mission Update’ refers to how often the mission typically provides updated kernels. If the mission update cadence is unknown, please contact the mission for more information. To receive newly updated kernels, it's necessary to re-run the rsync command described in 
-[Download Mission Data](https://github.com/DOI-USGS/ISIS3#mission-specific-data-downloads).
+ISIS provides ongoing automated updates of SPICE kernels for some of its supported missions by checking for new mission kernels, and if available, distributing them via the ISISDATA area available from the rsync server. These supported missions are listed in the table below, alongside their ISIS and Mission update cadences. ‘ISIS Update’ refers to how often ISIS looks for and then distributes new SPICE kernel updates and ‘Mission Update’ refers to how often the mission typically provides updated kernels. If the mission update cadence is unknown, please contact the mission for more information. To receive newly updated kernels for a mission, it's necessary to re-run the rsync command described in 
+[Mission Specific Data Areas](../../how-to-guides/environment-setup-and-maintenance/isis-data-area.md#mission-specific-data-areas).
 
 Missions that are not listed in the table below are provided with a static set of SPICE kernels that are not automatically updated. These are occasionally updated by hand. If you would like to request that the kernels provided with ISIS for one of these missions be updated, please submit a ticket at  [new issue](https://github.com/DOI-USGS/ISIS3/issues/new/choose).
 
diff --git a/docs/how-to-guides/isis-developer-guides/obtaining-maintaining-submitting-test-data.md b/docs/how-to-guides/isis-developer-guides/obtaining-maintaining-submitting-test-data.md
index 4837abf33075b9128948f4abfada5e9255b67249..f5db0f665541bf533a73dff2f5ee90e98620eff8 100644
--- a/docs/how-to-guides/isis-developer-guides/obtaining-maintaining-submitting-test-data.md
+++ b/docs/how-to-guides/isis-developer-guides/obtaining-maintaining-submitting-test-data.md
@@ -1,65 +1,126 @@
-# Obtaining, Maintaining, and Submitting Test Data for ISIS
+# ISIS Test Data
 
-The testing environment for ISIS includes unit tests for nearly every C++ class or struct in the ISIS library, one or more regression tests for all non-interactive applications, and several regression tests for chains of multiple applications (module tests). Many of the tests require input and/or truth files. Due to the large size (nearly 20GB) of these test files, they are not included in the GitHub code repository.
+## Kinds of Tests
 
-Unit tests are designed to test a single class from the ISIS library (e.g., Histogram, ProcessByLine, VoyagerCamera). They use two frameworks: the newer `gtest` and the older, in-house `make`-based tests. Test data for gtest-based tests is usually embedded in the test source code file located in `$ISISROOT/isis/tests`. Input data for the make-based tests can be embedded in the `unittest.cpp` located in the source code directory for the class or an external file located in the ISIS3DATA or ISIS3TESTDATA areas. Output test data for the `make`-based tests is always located in the source code directory for the class.
+### GTests and Legacy Makefile-based Tests
 
-Application and module tests are regression tests designed to test all the functionality of a single ISIS application (e.g., `fx`, `lowpass`, `cam2map`) or a series of ISIS applications (e.g., `vims2isis->spiceinit->cam2map`) respectively. Regression tests have both input and truth data stored in the ISIS3TESTSDATA area. Input and truth data files can be ISIS cubes, control networks, plain text, Parameter Value Language (PVL), Planetary Data System images (PDS3, PDS4), or comma-separated value (CSV) files.
+ISIS has of two types of tests: custom **Makefile** based tests, and **GTests**. The GTests use data from the ISIS repo along with the source, so no special data is required to run those, aside from the ISIS data area.
 
-### Setting Up an ISIS Development Environment
+The Makefile tests depend on a separate source of input and truth data data.  The `$ISISTESTDATA` environmental variable is used to locate that data.  The size of this test data decreases as we convert more Makefile tests to GTests.
 
-To run existing tests and develop new tests, a full development environment is required. The public releases do not contain the tests or test data or the source code for the tests. Follow these steps to get a working ISIS development environment with all the data:
+### Test Types
 
-1. Fork the ISIS source code [repository](https://github.com/DOI-USGS/ISIS3).
-2. Get the ISIS source code on your local machine by cloning your fork.
-3. [Build](../isis-developer-guides/developing-isis3-with-cmake.md) the ISIS library and applications.
-4. [Download](https://github.com/DOI-USGS/ISIS3) the ISIS data files.
+  - **Unit Tests** - tests for nearly every C++ class or struct in the ISIS library
+    - Examples: `Histogram`, `ProcessByLine`, or `VoyagerCamera`
+  - **Application Tests** - regression tests for individual applications
+    - Examples: `fx`, `lowpass`, or `cam2map`
+  - **Module Tests** - regression tests for chains of multiple applications
+    - Example: `vims2isis` → `spiceinit` → `cam2map`
 
-!!! Warning "Be careful where you put the ISISDATA area. It is several hundred GB and growing."
+### Data Locations
 
-### Downloading Test Data
+#### GTests
 
-ISIS unit and regression tests require the data and test data directories to be available and their respective environment variables (`ISISDATA`, `ISIS3TESTDATA`) to be set. This allows the tests to read files from these areas and compare results to known truth data.
+Test data for **GTests** is usually embedded in the test source code under `$ISISROOT/isis/tests`.
 
-Test data is hosted using Amazon S3 storage buckets. We recommend using rclone to pull the data into a local directory. Follow these steps:
+#### Makefile-based Tests
 
-1. Download rclone using their instructions (see: [https://rclone.org/downloads/](https://rclone.org/downloads/)) or by using an Anaconda environment (see: [https://docs.anaconda.com/anaconda/install/](https://docs.anaconda.com/anaconda/install/)).
-2. Install rclone with: `conda install –c conda-forge rclone` if using Anaconda.
-3. Configure rclone using a default S3 configuration. See [https://rclone.org/s3/](https://rclone.org/s3/) for detailed information.
-4. Run `rclone sync remote:asc-isisdata/isis_testData/ $ISISTESTDATA` to download the ISIS3 test data.
+Input data for the make-based tests is embedded in the `unittest.cpp` in the source code directory for the class, or an external file in the `ISISDATA` or `ISISTESTDATA` areas. Output test data for the **make**-based tests is always in the source code directory for the class.
 
-!!! Warning "Warnings"
-    - Users should understand the difference between rclone’s ‘sync’ and ‘copy’ methods. ‘copy’ overwrites all data in the destination with data from source, while ‘sync’ replaces only changed data.
-    - Syncing/copying in either direction (local -> remote or remote -> local) results in any changed data being overwritten. There is no warning message on overwrite.
+Regression tests have both input and truth data stored in the `ISISTESTDATA` area. Input and truth data files can be ISIS cubes, control networks, plain text, Parameter Value Language (PVL), Planetary Data System images (PDS3, PDS4), or comma-separated value (CSV) files.
 
-``` Console 
-rclone sync remote:asc-isisdata/isis_testData/ $ISISTESTDATA
-```
+## Setting Up Tests
 
-Where:
+### ISIS Development Environment
 
-    - $ISISTESTDATA is the environment variable defining the location of the ISISTESTDATA
-    - remote: is the name of the configuration you created earlier. This can be whatever you want to name it, in this case it is named remote.
-    - asc-isisdata/isis_testData/ is the name of the S3 bucket you’re downloading from
+To run and develop tests, you need a [full ISIS development environment](../../how-to-guides/isis-developer-guides/developing-isis3-with-cmake.md). The public releases don't include the test source code or data.
 
-After running the `rclone` command, $ISISTESTDATA should contain a full clone of the ISIS test data for running Makefile based tests.
+### Environmental variables
+The environmental variable `ISISTESTDATA` needs to point to the path where you want to store the ISIS Test Data.
 
-!!! Note "Notes"
-    Users can download specific files from the bucket by adding path data or file information to the first argument, that is, to download only the ‘base’ folder from the isis_testData bucket, the user could call: rclone sync remote:asc-isisdata/isis_testData/base
 
-### Set Up the ISIS environment variables
-The environment variable "ISIS3TESTDATA" needs to be set to point to the "isis" directory created by the rsync command above. Note: Each of the examples below ends with an "isis" directory.
+=== "conda"
 
-Bash and other sh based shells:
-```
-export ISIS3TESTDATA=/path/to/the/test/data/for/isis
-```
-tcsh or other csh based shells:
+    ```sh
+    # Activate your environment
+    conda activate isis
+
+    # Set the variable
+    conda env config vars set ISISTESTDATA=/path/to/your/isis_test_data/
+
+    # Reactivate your environment
+    conda deactivate
+    conda activate isis
+    ```
+
+=== "shell"
+
+    ```sh
+    export ISISTESTDATA=/path/to/your/isis_test_data
+    ```
+
+=== "csh/tcsh"
+
+    ```sh
+    setenv ISISTESTDATA=/path/to/your/isis_test_data
+    ```
+
+### Downloading Test Data
+
+ISIS *unit* and *regression* tests require the data and test data directories to be available, and need their respective environment variables (`ISISDATA`, `ISISTESTDATA`) to be set. This allows the tests to read files from these areas and compare results to known truth data.
+
+Test data is hosted in Amazon S3. We recommend using [rclone](https://rclone.org) to download the data. In conda, you can install rclone with:
+
+```sh
+conda install –c conda-forge rclone
 ```
-setenv ISIS3TESTDATA /path/to/the/test/data/for/isis
+
+Isis's rclone config is located at `isis/config/rclone.conf` in the ISIS repo.  To download the ISIS Test Data:
+
+```sh
+rclone --config isis/config/rclone.conf sync asc_s3:asc-isisdata/isis_testData/ $ISISTESTDATA
 ```
 
+??? quote "Test data rclone command breakdown"
+
+    - `$ISISTESTDATA` is an environmental variable pointing to the test data location
+    - `--config .../rclone.conf` points to ISIS's rclone.conf
+    - `asc_s3:` is the name of S3 configuration in ISIS's rclone.conf
+    - `asc-isisdata/isis_testData/` is the name of the S3 bucket you’re downloading from
+
+??? warning "rclone copy/sync can overwrite data!"
+
+    Note the difference between rclone `sync` and `copy`:
+
+    -  `copy` will overwrite all data in the destination with data from source.
+    - `sync` replaces only changed data.
+    
+    Syncing or copying in either direction (local → remote; remote → local) results in any changed data being overwritten without warning.
+
+After running the `rclone` command, `$ISISTESTDATA` should contain a full clone of the ISIS test data for running Makefile-based tests.
+
+-----
+
+#### Downloading specific files
+
+!!! quote ""
+
+    You can download specific files from the bucket by adding path data or file information to the first argument.  Take note of the [rclone config](https://rclone.org/s3/), or, use the ISIS included `isis/config/rclone.conf`.
+    
+    To download only the `base` folder from the isis_testData bucket:
+
+    ```sh
+    rclone --config isis/config/rclone.conf sync asc_s3:asc-isisdata/isis_testData/base
+    ```
+
+-----
+
 ## Contributing New Tests and Tests Fixtures
-The source code for the unit and regression tests is located with the ISIS source code repository on GitHub, but the data used by the tests is currently internal to USGS and is made available through AWS S3 servers. 
 
-All changes to ISIS classes and applications are required to be well-tested, which may require modifications or additions to test data. Tests and test data should be created as part of the GitHub pull request.  Because all tests are now written in gtest, no modifications to the S3-hosted data are currently accepted, and all test data/fixtures should be created according to the guidelines in the [testing documentation](../isis-developer-guides/writing-isis-tests-with-ctest-and-gtest.md).
\ No newline at end of file
+Source code for *unit* and *regression* GTests is in the ISIS GitHub repo.  Data used by legacy Makefile tests is hosted on AWS S3. 
+
+Testing is required for changes to ISIS classes and apps. This may entail changes or additions to the test data. Tests and test data should be created as part of GitHub PRs.  Any contributions of test data/fixtures should follow our [testing guidelines](../isis-developer-guides/writing-isis-tests-with-ctest-and-gtest.md).
+
+!!! failure "No new Makefile-based tests or data"
+
+    Because all tests are now written in gtest, no changes to the S3-hosted ISISTESTDATA area are currently accepted.
\ No newline at end of file
diff --git a/mkdocs.yml b/mkdocs.yml
index 7263a7d5454afc83bcffb40355f7f903f10c28b7..fba0d1888bc6b389145f33d2f9550dd0580d8b5a 100644
--- a/mkdocs.yml
+++ b/mkdocs.yml
@@ -55,7 +55,8 @@ nav:
   - How-To Guides: 
     - Home: how-to-guides/index.md
     - Environment Setup and Maintenance:
-      - Installing ISIS Via Anaconda:      how-to-guides/environment-setup-and-maintenance/installing-isis-via-anaconda.md
+      - Installing ISIS:                   how-to-guides/environment-setup-and-maintenance/installing-isis-via-anaconda.md
+      - Setting up the ISIS Data Area:     how-to-guides/environment-setup-and-maintenance/isis-data-area.md
       - Anaconda in a Network Environment: how-to-guides/environment-setup-and-maintenance/anaconda-in-a-network-environment.md
       - SPICE Kernel Updates in ISIS:      how-to-guides/environment-setup-and-maintenance/spice-kernel-updates-in-isis.md
       - Adding USGSCSM Plugin to ISIS:     how-to-guides/environment-setup-and-maintenance/adding-usgscsm-plugin-to-isis.md
@@ -77,14 +78,14 @@ nav:
       - Guidelines for Pull Requests:      how-to-guides/software-management/guidelines-for-pull-requests.md
       - ISIS Release Schedule:             how-to-guides/software-management/isis-release-schedule.md
     - ISIS Developer Guides:
-      - Getting Started Contributing to ISIS:         how-to-guides/isis-developer-guides/contributing-to-isis.md
-      - How To Write ISIS Tests with CTest and GTest: how-to-guides/isis-developer-guides/writing-isis-tests-with-ctest-and-gtest.md
+      - Contributing to ISIS:                         how-to-guides/isis-developer-guides/contributing-to-isis.md
+      - Writing Tests with CTest and GTest:           how-to-guides/isis-developer-guides/writing-isis-tests-with-ctest-and-gtest.md
       - App Testing CookBook:                         how-to-guides/isis-developer-guides/app-testing-cookbook.md
-      - Class Requirements For Using Doxygen Tags:    how-to-guides/isis-developer-guides/class-requirements-for-using-doxygen-tags.md
+      - Doxygen Tag Class Requirement:                how-to-guides/isis-developer-guides/class-requirements-for-using-doxygen-tags.md
       - Developing ISIS3 with cmake:                  how-to-guides/isis-developer-guides/developing-isis3-with-cmake.md
       - ISIS Development on ARM Macs:    how-to-guides/isis-developer-guides/developing-mac-m1-arm-systems.md
       - Building and Contributing to ISIS Tutorial:   how-to-guides/isis-developer-guides/building-and-contributing-to-isis-tutorial.md
-      - Obtaining, Maintaining, and Submitting Test Data: how-to-guides/isis-developer-guides/obtaining-maintaining-submitting-test-data.md
+      - ISIS Test Data:                               how-to-guides/isis-developer-guides/obtaining-maintaining-submitting-test-data.md
       - ISIS Programming Exercises:
         - Exercise 1:                                 how-to-guides/isis-developer-guides/exercise-1.md
         - Exercise 2:                                 how-to-guides/isis-developer-guides/exercise-2.md