From 2d4889360279dcbc9c4e1683cd9e98baeb791cbe Mon Sep 17 00:00:00 2001
From: dannyrb <danny.ri.brown@gmail.com>
Date: Fri, 10 May 2019 09:18:28 -0400
Subject: [PATCH 01/26] Remove publicserver example (we get this for free with
 CRA)

---
 docker/Nginx/docker-compose-publicserver.yml | 13 -------------
 1 file changed, 13 deletions(-)
 delete mode 100644 docker/Nginx/docker-compose-publicserver.yml

diff --git a/docker/Nginx/docker-compose-publicserver.yml b/docker/Nginx/docker-compose-publicserver.yml
deleted file mode 100644
index be969291a..000000000
--- a/docker/Nginx/docker-compose-publicserver.yml
+++ /dev/null
@@ -1,13 +0,0 @@
-version: '3.5'
-
-services:
-  viewer:
-    container_name: ohif-viewer
-    build:
-      context: ../
-      dockerfile: Dockerfile
-    ports:
-      - '80:80'
-    environment:
-      - NODE_ENV=production
-      - REACT_APP_CONFIG=config/public_dicomweb

From ed91e2678f0573132fee575548a1e0454a34e553 Mon Sep 17 00:00:00 2001
From: dannyrb <danny.ri.brown@gmail.com>
Date: Fri, 10 May 2019 09:18:46 -0400
Subject: [PATCH 02/26] This is outdated - refer to /docs

---
 docker/OpenResty-Orthanc-Keycloak/README.md | 31 ---------------------
 1 file changed, 31 deletions(-)
 delete mode 100644 docker/OpenResty-Orthanc-Keycloak/README.md

diff --git a/docker/OpenResty-Orthanc-Keycloak/README.md b/docker/OpenResty-Orthanc-Keycloak/README.md
deleted file mode 100644
index 3582f8dbf..000000000
--- a/docker/OpenResty-Orthanc-Keycloak/README.md
+++ /dev/null
@@ -1,31 +0,0 @@
-# Guide
-
-Build docker container using:
-
-- Build: `docker build -t authproxy .`
-- Tag: `docker tag authproxy:latest authproxy:staging`
-
-> Start your docker container, and volume mount the directory containing the
-> `nginx-keycloak.conf` configuration file. We also mount the current directory
-> under `/usr/share/nginx/html` so any html files in the current directory will
-> be hosted behind the authenticating proxy. Finally, we mapped port 80 on the
-> host to port 80 in the container.
-
-`docker run -d -it -p 80:80 -v $PWD/:/config -v /:/usr/share/nginx/html authproxy -c /config/nginx.conf`
-docker run -d -it -p 80:80 -v /:/config -v /:/usr/share/nginx/html authproxy -c
-/config/nginx-keycloak.conf
-
-## Orthanc
-
-- Configuration
-  - http://book.orthanc-server.com/users/configuration.html#configuration
-
-## Keycloak
-
-### Setup
-
-Library we use to manage OpenID-Connect `implicit` flow:
-https://github.com/maxmantz/redux-oidc
-
-- Set admin user/pass in `docker-compose`
-- What are realms?

From 5c8b4c7e0e774a0b76f962eaf32943eb214d3a20 Mon Sep 17 00:00:00 2001
From: dannyrb <danny.ri.brown@gmail.com>
Date: Fri, 10 May 2019 09:25:51 -0400
Subject: [PATCH 03/26] Requirements for local data source

---
 docs/latest/essentials/data-source.md | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/docs/latest/essentials/data-source.md b/docs/latest/essentials/data-source.md
index 116495dba..a0840985f 100644
--- a/docs/latest/essentials/data-source.md
+++ b/docs/latest/essentials/data-source.md
@@ -27,7 +27,12 @@ For our purposes, we will be using `Orthanc`, but you can see a list of
 
 ### Requirements
 
-...
+- Docker
+  - [Docker for Mac](https://docs.docker.com/docker-for-mac/)
+  - [Docker for Windows](https://docs.docker.com/docker-for-windows/)
+
+_Not sure if you have `docker` installed already? Try running `docker --version`
+in command prompt or terminal_
 
 ### Running Orthanc
 

From 522f29d3593ff0bb0ec7c8ec624b8a4253ff91f0 Mon Sep 17 00:00:00 2001
From: dannyrb <danny.ri.brown@gmail.com>
Date: Fri, 10 May 2019 09:26:03 -0400
Subject: [PATCH 04/26] Note about other image archives

---
 docs/latest/essentials/data-source.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/docs/latest/essentials/data-source.md b/docs/latest/essentials/data-source.md
index a0840985f..3a7f79d66 100644
--- a/docs/latest/essentials/data-source.md
+++ b/docs/latest/essentials/data-source.md
@@ -96,6 +96,9 @@ The `REACT_APP_CONFIG` value tells our app which file to load on to
 
 ## Open Source DICOM Image Archives
 
+Our example uses `Orthanc`, but there are a lot of options available to you.
+Here are some of the more popular ones:
+
 | Archive                                       | Installation                       |
 | --------------------------------------------- | ---------------------------------- |
 | [DCM4CHEE Archive 5.x][dcm4chee]              | [W/ Docker][dcm4chee-docker]       |

From 74cac08ce7f71b135870751ddb89a0c2e2ee2111 Mon Sep 17 00:00:00 2001
From: dannyrb <danny.ri.brown@gmail.com>
Date: Fri, 10 May 2019 09:29:18 -0400
Subject: [PATCH 05/26] Add a snapshot of our config

---
 docs/latest/essentials/data-source.md | 26 +++++++++++++++++++++++++-
 1 file changed, 25 insertions(+), 1 deletion(-)

diff --git a/docs/latest/essentials/data-source.md b/docs/latest/essentials/data-source.md
index 3a7f79d66..7d828e8a0 100644
--- a/docs/latest/essentials/data-source.md
+++ b/docs/latest/essentials/data-source.md
@@ -92,7 +92,31 @@ cross-env PORT=5000 REACT_APP_CONFIG=config/docker_nginx-orthanc.js react-script
 
 The `REACT_APP_CONFIG` value tells our app which file to load on to
 `window.config`. By default, our app uses the file at
-`<project-root>/public/config/default.js`.
+`<project-root>/public/config/default.js`. Here is what that configuration looks
+like:
+
+```js
+window.config = {
+  routerBasename: '/',
+  relativeWebWorkerScriptsPath: '',
+  servers: {
+    dicomWeb: [
+      {
+        name: 'Orthanc',
+        wadoUriRoot: 'http://localhost:8899/wado',
+        qidoRoot: 'http://localhost:8899/dicom-web',
+        wadoRoot: 'http://localhost:8899/dicom-web',
+        qidoSupportsIncludeField: false,
+        imageRendering: 'wadors',
+        thumbnailRendering: 'wadors',
+      },
+    ],
+  },
+}
+```
+
+To learn more about how you can configure the OHIF Viewer, check out our
+[Configuration Guide](./configuration.md).
 
 ## Open Source DICOM Image Archives
 

From f8d8e1ad5130a680dd1041b9dc75b28c4f0fc8ff Mon Sep 17 00:00:00 2001
From: dannyrb <danny.ri.brown@gmail.com>
Date: Fri, 10 May 2019 09:33:39 -0400
Subject: [PATCH 06/26] Remove empty deployment page

---
 docs/latest/SUMMARY.md               | 1 -
 docs/latest/essentials/deployment.md | 1 -
 2 files changed, 2 deletions(-)
 delete mode 100644 docs/latest/essentials/deployment.md

diff --git a/docs/latest/SUMMARY.md b/docs/latest/SUMMARY.md
index 1e8e13635..a7ae5632a 100644
--- a/docs/latest/SUMMARY.md
+++ b/docs/latest/SUMMARY.md
@@ -7,7 +7,6 @@
   - [Themeing](essentials/themeing.md)
   - [Troubleshooting](essentials/troubleshooting.md)
 - [Architecture](essentials/architecture.md)
-- [Deployment](essentials/deployment.md)
 
 ---
 
diff --git a/docs/latest/essentials/deployment.md b/docs/latest/essentials/deployment.md
deleted file mode 100644
index d36c65e59..000000000
--- a/docs/latest/essentials/deployment.md
+++ /dev/null
@@ -1 +0,0 @@
-# Deployment

From 5609070fd811b5a4a93678202b20606bf863d00a Mon Sep 17 00:00:00 2001
From: dannyrb <danny.ri.brown@gmail.com>
Date: Fri, 10 May 2019 09:46:58 -0400
Subject: [PATCH 07/26] Add installation

---
 docs/latest/SUMMARY.md                 |  1 +
 docs/latest/essentials/installation.md | 42 ++++++++++++++++++++++++++
 2 files changed, 43 insertions(+)
 create mode 100644 docs/latest/essentials/installation.md

diff --git a/docs/latest/SUMMARY.md b/docs/latest/SUMMARY.md
index a7ae5632a..c06ce54ab 100644
--- a/docs/latest/SUMMARY.md
+++ b/docs/latest/SUMMARY.md
@@ -2,6 +2,7 @@
 
 - Essentials
   - [Getting Started](essentials/getting-started.md)
+  - [Installation](essentials/installation.md)
   - [Data Source](essentials/data-source.md)
   - [Configuration](essentials/configuration.md)
   - [Themeing](essentials/themeing.md)
diff --git a/docs/latest/essentials/installation.md b/docs/latest/essentials/installation.md
new file mode 100644
index 000000000..326b5f0d2
--- /dev/null
+++ b/docs/latest/essentials/installation.md
@@ -0,0 +1,42 @@
+# Installation
+
+It's important to know that the OHIF Viewer project provides two different build
+processes:
+
+```bash
+# Static Asset output: For deploying PWAs
+yarn run build:web
+
+# Single `.js` script, for embedding viewer into existing apps
+yarn run build:package
+```
+
+## create-react-app (PWA)
+
+> [create-react-app](https://github.com/facebook/create-react-app) provides
+> pre-configured build process for developing front-end applications with
+> [React](https://reactjs.org/).
+
+The ohif-viewer package can be run as a create-react-app application. This is
+useful for development, debugging, or evolving the OHIF Viewer into your own
+custom imaging application.
+
+You can read more about this particular strategy in our
+[Build for Production Deployment Guide](./../deployment/recipes/build-for-production.md)
+
+## Rollup (Packaged Script)
+
+> [Rollup](https://rollupjs.org/guide/en) is a module bundler for JavaScript. It
+> uses the new standardized format for code modules included in the ES6 revision
+> of JavaScript.
+
+The [ohif-viewer](https://www.npmjs.com/package/ohif-viewer) package can be
+built with Rollup to provide a set of React components which can be dropped into
+a larger application. Specifically, the ohif-viewer package provides a React
+component named `OHIFViewer` which is the entire viewer, configurable via React
+`props`. This is useful for including the OHIF Viewer in a larger web
+application, as the entire application can be provided via a `<script>` tag with
+no build process required.
+
+You can read more about this particular strategy in our
+[Embedded Viewer Deployment Guide](./../deployment/recipes/embedded-viewer.md)

From 2f0c40f64a3280f2e8317fcd5a1d1b0f76d0a504 Mon Sep 17 00:00:00 2001
From: dannyrb <danny.ri.brown@gmail.com>
Date: Fri, 10 May 2019 09:47:12 -0400
Subject: [PATCH 08/26] CTA for troubleshooting

---
 docs/latest/essentials/troubleshooting.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/docs/latest/essentials/troubleshooting.md b/docs/latest/essentials/troubleshooting.md
index 8c2d5a2bf..01ed804e2 100644
--- a/docs/latest/essentials/troubleshooting.md
+++ b/docs/latest/essentials/troubleshooting.md
@@ -1,5 +1,9 @@
 # Troubleshooting
 
+Common GitHub issues that are not easily remedied with cleaner code or
+documentation will be recorded here. Please feel free to make PRs to update this
+page.
+
 ## Common Problems
 
 | Problem                                      | Most Common Reasons                                                                                                                                         |

From 2632824feb77dfa0e8d07ae98f3ce5de4f211609 Mon Sep 17 00:00:00 2001
From: dannyrb <danny.ri.brown@gmail.com>
Date: Fri, 10 May 2019 09:47:34 -0400
Subject: [PATCH 09/26] Architecture --> Scope of project

---
 docs/latest/SUMMARY.md                                          | 2 +-
 docs/latest/essentials/{architecture.md => scope-of-project.md} | 0
 2 files changed, 1 insertion(+), 1 deletion(-)
 rename docs/latest/essentials/{architecture.md => scope-of-project.md} (100%)

diff --git a/docs/latest/SUMMARY.md b/docs/latest/SUMMARY.md
index c06ce54ab..d55c77812 100644
--- a/docs/latest/SUMMARY.md
+++ b/docs/latest/SUMMARY.md
@@ -7,7 +7,7 @@
   - [Configuration](essentials/configuration.md)
   - [Themeing](essentials/themeing.md)
   - [Troubleshooting](essentials/troubleshooting.md)
-- [Architecture](essentials/architecture.md)
+- [Scope of Project](essentials/scope-of-project.md)
 
 ---
 
diff --git a/docs/latest/essentials/architecture.md b/docs/latest/essentials/scope-of-project.md
similarity index 100%
rename from docs/latest/essentials/architecture.md
rename to docs/latest/essentials/scope-of-project.md

From c1eeba27fc3b0446fdda6e4169015d03e97d61f0 Mon Sep 17 00:00:00 2001
From: dannyrb <danny.ri.brown@gmail.com>
Date: Fri, 10 May 2019 09:49:53 -0400
Subject: [PATCH 10/26] Delete dcm4chee-with-docker guide. If we do this, we'll
 expose it the same way we did w/ orthanc

---
 .../latest/essentials/dcm4chee-with-docker.md | 41 -------------------
 1 file changed, 41 deletions(-)
 delete mode 100644 docs/latest/essentials/dcm4chee-with-docker.md

diff --git a/docs/latest/essentials/dcm4chee-with-docker.md b/docs/latest/essentials/dcm4chee-with-docker.md
deleted file mode 100644
index 64f5fb65b..000000000
--- a/docs/latest/essentials/dcm4chee-with-docker.md
+++ /dev/null
@@ -1,41 +0,0 @@
-# DCM4CHEE with Docker
-
-1. Install Docker (https://www.docker.com/)
-2. Follow the DCM4CHEE Guidelines for Running on Docker.
-
-    The easiest path is to use Docker-Compose which will start and stop multiple containers for you. There are excellent instructions provided by the DCM4CHEE team on the 'light archive' repository:
-
-    https://github.com/dcm4che/dcm4chee-arc-light/wiki/Running-on-Docker#use-docker-compose
-
-    * Create docker-compose.yml and docker-compose.env files
-    * Start the containers:
-
-    ```` bash
-    docker-compose start
-    ````
-
-    **Note:** If you are running this on Mac OSX you will probably need to change the default docker-compose.yml file slightly. Specifically, the paths that refer to /var/local/ will likely need to be changed to /opt/
-
-3. Run the OHIF Viewer or Lesion Tracker using the dcm4cheeDIMSE.json configuration file
-
-````bash
-cd OHIFViewer
-PACKAGE_DIRS="../Packages" meteor --settings ../config/dcm4cheeDIMSE.json
-````
-
-## Web Service URLs from DCM4CHEE:
-Original source here: https://github.com/dcm4che/dcm4chee-arc-light/wiki/Running-on-Docker#web-service-urls
-
-> - Archive UI: <http://localhost:8080/dcm4chee-arc/ui> - if secured, login with
-
->     Username | Password | Role
->     --- | --- | ---
->     `user` | `user` | `user`
->     `admin` | `admin` | `user` + `admin`
-> - Keycloak Administration Console: <http://localhost:8080/auth>, login with Username: `admin`, Password: `admin`.
-> - Wildfly Administration Console: <http://localhost:9990>, login with Username: `admin`, Password: `admin`.
-> - Kibana UI: <http://localhost:5601>
-> - DICOM QIDO-RS Base URL: <http://localhost:8080/dcm4chee-arc/aets/DCM4CHEE/rs>
-> - DICOM STOW-RS Base URL: <http://localhost:8080/dcm4chee-arc/aets/DCM4CHEE/rs>
-> - DICOM WADO-RS Base URL: <http://localhost:8080/dcm4chee-arc/aets/DCM4CHEE/rs>
-> - DICOM WADO-URI: <http://localhost:8080/dcm4chee-arc/aets/DCM4CHEE/wado>

From 5acb30d7f0f467b27e8b6f5aed7ea43f463dc050 Mon Sep 17 00:00:00 2001
From: dannyrb <danny.ri.brown@gmail.com>
Date: Fri, 10 May 2019 09:51:41 -0400
Subject: [PATCH 11/26] Auto-format

---
 docs/latest/advanced/architecture.md | 73 ++++++++++++++++++++--------
 1 file changed, 54 insertions(+), 19 deletions(-)

diff --git a/docs/latest/advanced/architecture.md b/docs/latest/advanced/architecture.md
index e91372c4b..0d7e6007d 100644
--- a/docs/latest/advanced/architecture.md
+++ b/docs/latest/advanced/architecture.md
@@ -1,17 +1,35 @@
 # Architecture
 
-Looking to extend your instance of the OHIF Viewer? Want learn how to reuse _a portion_ of the Viewer in your own application? Or maybe you want to get involved and draft or suggest a new feature? Regardless, you're in the right place!
+Looking to extend your instance of the OHIF Viewer? Want learn how to reuse _a
+portion_ of the Viewer in your own application? Or maybe you want to get
+involved and draft or suggest a new feature? Regardless, you're in the right
+place!
 
-The OHIF Viewer aims to be decoupled, configurable, and extensible; while this allows our code to be used in more ways, it also increases complexity. Below, we aim to demistify that complexity by providing insight into how our Viewer is architected, and the role each of it's dependent libraries plays.
+The OHIF Viewer aims to be decoupled, configurable, and extensible; while this
+allows our code to be used in more ways, it also increases complexity. Below, we
+aim to demistify that complexity by providing insight into how our Viewer is
+architected, and the role each of it's dependent libraries plays.
 
 ## Overview
 
-The [`OHIF/Viewers`](https://github.com/OHIF/Viewers/tree/react) repository contains the source code for the OHIF Medical Imaging Viewer. It is effectively a React [progressive web app](https://developers.google.com/web/progressive-web-apps/) (PWA) that combines the business logic housed in [`OHIF/ohif-core`](https://github.com/OHIF/ohif-core) and the components in our React Component library [`OHIF/react-viewerbase`](https://github.com/OHIF/react-viewerbase). It provides customization for common use cases through [configuration](../essentials/configuration.md) and for adding functionality via [extensions](./extensions.md).
-
+The [`OHIF/Viewers`](https://github.com/OHIF/Viewers/tree/react) repository
+contains the source code for the OHIF Medical Imaging Viewer. It is effectively
+a React
+[progressive web app](https://developers.google.com/web/progressive-web-apps/)
+(PWA) that combines the business logic housed in
+[`OHIF/ohif-core`](https://github.com/OHIF/ohif-core) and the components in our
+React Component library
+[`OHIF/react-viewerbase`](https://github.com/OHIF/react-viewerbase). It provides
+customization for common use cases through
+[configuration](../essentials/configuration.md) and for adding functionality via
+[extensions](./extensions.md).
 
 ### Business Logic
 
-Our goal is to maintain the majority of our business logic in [`OHIF/ohif-core`](https://github.com/OHIF/ohif-core). `ohif-core` offers pre-packaged solutions for features common to Web-based medical imaging viewers. For example:
+Our goal is to maintain the majority of our business logic in
+[`OHIF/ohif-core`](https://github.com/OHIF/ohif-core). `ohif-core` offers
+pre-packaged solutions for features common to Web-based medical imaging viewers.
+For example:
 
 - Hotkeys
 - DICOM Web
@@ -22,33 +40,46 @@ Our goal is to maintain the majority of our business logic in [`OHIF/ohif-core`]
 - [And many others](https://github.com/OHIF/ohif-core/blob/master/src/index.js#L49-L69)
 
 It does this while remaining decoupled from any particular view library or
-rendering logic. While we use it to power our React Viewer, it can be used with Vue, React, Vanilla JS, or any number of other frameworks.
-
+rendering logic. While we use it to power our React Viewer, it can be used with
+Vue, React, Vanilla JS, or any number of other frameworks.
 
 ### React Component Library
 
-[`OHIF/react-viewerbase`](https://github.com/OHIF/react-viewerbase) is a React Component library that contains the reusable components that power the OHIF Viewer. It allows us to build, compose, and test components in isolation; easing the development process by reducing the need to stand-up a local PACS with test case data.
+[`OHIF/react-viewerbase`](https://github.com/OHIF/react-viewerbase) is a React
+Component library that contains the reusable components that power the OHIF
+Viewer. It allows us to build, compose, and test components in isolation; easing
+the development process by reducing the need to stand-up a local PACS with test
+case data.
 
 [Check out our component library!](https://react.ohif.org/)
 
-
 ### Misc. Extensions
 
-Want to add custom logic or UI Components to the OHIF Viewer, but don't want to maintain a fork? We expose common integration points via [extensions](./extensions.md) to make that possible. For a list of extensions maintained by OHIF, [check out this helpful table](./extensions.html#ohif-maintained-extensions).
+Want to add custom logic or UI Components to the OHIF Viewer, but don't want to
+maintain a fork? We expose common integration points via
+[extensions](./extensions.md) to make that possible. For a list of extensions
+maintained by OHIF,
+[check out this helpful table](./extensions.html#ohif-maintained-extensions).
 
-
-If you find yourself thinking "I wish the Viewer could do X", and you can't accomplish it with an extension today, create a GitHub issue! We're actively looking for ways to improve our extensibility ^_^
+If you find yourself thinking "I wish the Viewer could do X", and you can't
+accomplish it with an extension today, create a GitHub issue! We're actively
+looking for ways to improve our extensibility ^\_^
 
 [Click here to read more about extensions!](./extensions.md)
 
 ### Diagram
 
-This diagram is a conceptual illustration of how the Viewer is architected. 
+This diagram is a conceptual illustration of how the Viewer is architected.
 
-0. (optional) `extensions` can be registered with `ohif-core`'s extension manager
-1. `ohif-core` provides bussiness logic and a way for `viewer` to access registered extensions
-2. The `viewer` composes and provides data to components from our component library (`react-viewerbase`)
-3. The `viewer` can be built and served as a stand-alone PWA, or as an embeddable package ([`ohif-viewer`](https://www.npmjs.com/package/ohif-viewer))
+0. (optional) `extensions` can be registered with `ohif-core`'s extension
+   manager
+1. `ohif-core` provides bussiness logic and a way for `viewer` to access
+   registered extensions
+1. The `viewer` composes and provides data to components from our component
+   library (`react-viewerbase`)
+1. The `viewer` can be built and served as a stand-alone PWA, or as an
+   embeddable package
+   ([`ohif-viewer`](https://www.npmjs.com/package/ohif-viewer))
 
 ![Architecture Diagram](../assets/img/architecture-diagram.png)
 
@@ -56,10 +87,14 @@ This diagram is a conceptual illustration of how the Viewer is architected.
 
 ## Common Questions
 
-> When should I use the packaged source `ohif-viewer` versus building a PWA from the source?
+> When should I use the packaged source `ohif-viewer` versus building a PWA from
+> the source?
 
 ...
 
 > Can I create my own Viewer using Vue.js or Angular.js?
 
-You can, but you will not be able to leverage as much of the existing code and components. `ohif-core` could still be used for business logic, and to provide a model for extensions. `react-viewerbase` would then become a guide for the components you would need to recreate.
\ No newline at end of file
+You can, but you will not be able to leverage as much of the existing code and
+components. `ohif-core` could still be used for business logic, and to provide a
+model for extensions. `react-viewerbase` would then become a guide for the
+components you would need to recreate.

From e53b57a642a40f8dfa61d991c915c40eae6d6bc7 Mon Sep 17 00:00:00 2001
From: dannyrb <danny.ri.brown@gmail.com>
Date: Fri, 10 May 2019 09:55:24 -0400
Subject: [PATCH 12/26] Configuration

---
 .../recipes/build-for-production.md           |  6 +-
 docs/latest/essentials/configuration.md       | 58 ++++++++++++++++++-
 2 files changed, 59 insertions(+), 5 deletions(-)

diff --git a/docs/latest/deployment/recipes/build-for-production.md b/docs/latest/deployment/recipes/build-for-production.md
index 92673e69a..37b675941 100644
--- a/docs/latest/deployment/recipes/build-for-production.md
+++ b/docs/latest/deployment/recipes/build-for-production.md
@@ -65,10 +65,8 @@ how to configure the project for your own imaging archive below.
 ### Configuration
 
 > This step assumes you have an imaging archive. If you need assistance setting
-> one up, check out the [`Data` section](./../index.md#data) of our Deployment
-> Guide, or `Getting Started`'s
-> ["Set up a local DICOM server"](./../../essentials/getting-started.md#set-up-a-local-dicom-server),
-> or a deployment recipe that contains an open source Image Archive
+> one up, check out the [`Data Source` Guide](./../essentials/data-source.md) or
+> a deployment recipe that contains an open source Image Archive
 
 #### How it Works
 
diff --git a/docs/latest/essentials/configuration.md b/docs/latest/essentials/configuration.md
index af4abbfe2..7017b4d97 100644
--- a/docs/latest/essentials/configuration.md
+++ b/docs/latest/essentials/configuration.md
@@ -1 +1,57 @@
-# Configuration
\ No newline at end of file
+# Configuration
+
+> This step assumes you have an imaging archive. If you need assistance setting
+> one up, check out the [`Data Source` Guide](./data-source.md) or a deployment
+> recipe that contains an open source Image Archive
+
+## How it Works
+
+The configuration for our project is in the `/public/config` directory. Our
+build process knows which configuration file to use based on the
+`REACT_APP_CONFIG` environment variable. By default, its value is
+[`default.js`](https://github.com/OHIF/Viewers/blob/react/public/config/default.js).
+When we build, the `%REACT_APP_CONFIG%` value in
+our[`/public/index.html`](https://github.com/OHIF/Viewers/blob/react/public/index.html#L12-L15)
+file is substituted for the correct configuration file's name. This sets the
+`window.config` equal to our configuration file's value.
+
+## How do I configure my project?
+
+The simplest way is to update the existing default config:
+
+_/public/config/default.js_
+
+```js
+window.config = {
+  routerBasename: '/',
+  relativeWebWorkerScriptsPath: '',
+  servers: {
+    dicomWeb: [
+      {
+        name: 'DCM4CHEE',
+        wadoUriRoot: 'https://server.dcmjs.org/dcm4chee-arc/aets/DCM4CHEE/wado',
+        qidoRoot: 'https://server.dcmjs.org/dcm4chee-arc/aets/DCM4CHEE/rs',
+        wadoRoot: 'https://server.dcmjs.org/dcm4chee-arc/aets/DCM4CHEE/rs',
+        qidoSupportsIncludeField: true,
+        imageRendering: 'wadors',
+        thumbnailRendering: 'wadors',
+        requestOptions: {
+          requestFromBrowser: true,
+        },
+      },
+    ],
+  },
+}
+```
+
+You can also create a new config file and specify its path relative to the build
+output's root by setting the `REACT_APP_CONFIG` environment variable. You can
+set the value of this environment variable a few different ways:
+
+- [Add a temporary environment variable in your shell](https://facebook.github.io/create-react-app/docs/adding-custom-environment-variables#adding-temporary-environment-variables-in-your-shell)
+- [Add environment specific variables in `.env` file(s)](https://facebook.github.io/create-react-app/docs/adding-custom-environment-variables#adding-development-environment-variables-in-env)
+- Using the `cross-env` package in an npm script:
+  - `"build": "cross-env REACT_APP_CONFIG=config/my-config.js react-scripts build"`
+
+After updating the configuration, `yarn run build:web` to generate updated build
+output.

From e90913b0a525288650e2cf03d78fcd3f2d0eef79 Mon Sep 17 00:00:00 2001
From: dannyrb <danny.ri.brown@gmail.com>
Date: Fri, 10 May 2019 13:58:04 -0400
Subject: [PATCH 13/26] Fix link

---
 docs/latest/deployment/recipes/build-for-production.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/latest/deployment/recipes/build-for-production.md b/docs/latest/deployment/recipes/build-for-production.md
index 37b675941..19dc5563a 100644
--- a/docs/latest/deployment/recipes/build-for-production.md
+++ b/docs/latest/deployment/recipes/build-for-production.md
@@ -65,8 +65,8 @@ how to configure the project for your own imaging archive below.
 ### Configuration
 
 > This step assumes you have an imaging archive. If you need assistance setting
-> one up, check out the [`Data Source` Guide](./../essentials/data-source.md) or
-> a deployment recipe that contains an open source Image Archive
+> one up, check out the [`Data Source` Guide](./../../essentials/data-source.md)
+> or a deployment recipe that contains an open source Image Archive
 
 #### How it Works
 

From 90d79ec9e26a55f7c1b8a2ec580915078f186f29 Mon Sep 17 00:00:00 2001
From: dannyrb <danny.ri.brown@gmail.com>
Date: Fri, 10 May 2019 13:58:30 -0400
Subject: [PATCH 14/26] White labeling (custom logo) notes

---
 docs/latest/essentials/themeing.md | 38 ++++++++++++++++++++++++++++++
 src/index.js                       | 24 -------------------
 2 files changed, 38 insertions(+), 24 deletions(-)

diff --git a/docs/latest/essentials/themeing.md b/docs/latest/essentials/themeing.md
index 8dc5c574b..f67f0e2c9 100644
--- a/docs/latest/essentials/themeing.md
+++ b/docs/latest/essentials/themeing.md
@@ -57,3 +57,41 @@ open to pull requests and discussion issues.
   --viewport-border-thickness: 1px;
 }
 ```
+
+## White Labeling
+
+> A white-label product is a product or service produced by one company (the
+> producer) that other companies (the marketers) rebrand to make it appear as if
+> they had made it - [Wikipedia: White-Label Product][wikipedia]
+
+Current white-labeling options are limited. We expose the ability to replace the
+"Logo" section of the application with a custom "Logo" component. You can do
+this by adding a `whiteLabelling` key to your
+[configuration file](./configuration.md).
+
+```js
+function RadicalImagingLogo() {
+  return React.createElement(
+    'a',
+    {
+      target: '_blank',
+      rel: 'noopener noreferrer',
+      className: 'header-brand',
+      href: 'http://radicalimaging.com',
+    },
+    React.createElement('h5', {}, 'RADICAL IMAGING')
+  )
+}
+
+props.whiteLabelling = {
+  logoComponent: RadicalImagingLogo(),
+}
+```
+
+<!--
+  Links
+  -->
+
+<!-- prettier-ignore-start -->
+[wikipedia]: https://en.wikipedia.org/wiki/White-label_product
+<!-- prettier-ignore-end -->
diff --git a/src/index.js b/src/index.js
index 2cbb8889a..51ad953cb 100644
--- a/src/index.js
+++ b/src/index.js
@@ -130,27 +130,3 @@ Plugins
       "displaySetCount": 1
     }
  */
-
-/*
-
-White labelling example
-
-// Note that you can't write JSX here, so you can use the online JSX compiler:
-// https://babeljs.io/repl/#?babili=false&browsers=&build=&builtIns=false&spec=false&loose=false&code_lz=GYVwdgxgLglg9mABACwKYBt1wBQEpEDeAUIogE6pQhlIA8AholPWQOaUC8ARAPoBG6emADWXchm5g4cAA6owqMoikVgiimTERBAZx0A5egFtU3NPQAmigLR8yQi2OSqzUKDIBcAei_2LMCHp0GCN6VhgwVgA6CDgjLgA-ElIU1LS02hDWRB0yCA4AcmQ3Tx8_AKCQsIjo2KMvAHcZa1iwKHkoLxAZLEsdLwAmAAYARgB2LxGRrwgyWTkLFrmZBetwMGNURYGomUiCxC8k9JOU2i96BIBuIgBfIiA&debug=false&forceAllTransforms=false&shippedProposals=false&circleciRepo=&evaluate=false&fileSize=false&timeTravel=false&sourceType=module&lineWrap=true&presets=react&prettier=false&targets=&version=6.26.0&envVersion=
-*/
-/*function RadicalImagingLogo() {
-  return React.createElement(
-    'a',
-    {
-      target: '_blank',
-      rel: 'noopener noreferrer',
-      className: 'header-brand',
-      href: 'http://radicalimaging.com'
-    },
-    React.createElement('h5', {}, 'RADICAL IMAGING')
-  );
-}
-
-props.whiteLabelling = {
-  logoComponent: RadicalImagingLogo()
-};*/

From 169399f9cb2e29ab7c0a7bd1a2b79389d3130bc2 Mon Sep 17 00:00:00 2001
From: dannyrb <danny.ri.brown@gmail.com>
Date: Fri, 10 May 2019 13:58:45 -0400
Subject: [PATCH 15/26] Clear out scope-of-project file

---
 docs/latest/essentials/scope-of-project.md | 27 +---------------------
 1 file changed, 1 insertion(+), 26 deletions(-)

diff --git a/docs/latest/essentials/scope-of-project.md b/docs/latest/essentials/scope-of-project.md
index 7b8465a5b..82280156a 100644
--- a/docs/latest/essentials/scope-of-project.md
+++ b/docs/latest/essentials/scope-of-project.md
@@ -1,26 +1 @@
-# Architecture
-
-The ohif-viewer package provides two different build processes:
-
-## create-react-app
-
-> [create-react-app](https://github.com/facebook/create-react-app) provides
-> pre-configured build process for developing front-end applications with
-> [React](https://reactjs.org/).
-
-The ohif-viewer package can be run as a create-react-app application. This is
-useful for development, debugging, or evolving ohif-viewer into your own custom
-imaging application.
-
-## Rollup
-
-> [Rollup](https://rollupjs.org/guide/en) is a module bundler for JavaScript. It
-> uses the new standardized format for code modules included in the ES6 revision
-> of JavaScript.
-
-The ohif-viewer package can be built with Rollup to provide a set of React
-components which can be dropped into a larger application. Specifically, the
-ohif-viewer package provides a React component named `OHIFViewer` which is the
-entire viewer, configurable via React `props`. This is useful for including the
-OHIF Viewer in a larger web application, as the entire application can be
-provided via a `<script>` tag with no build process required.
+# Scope of Project

From 65724394bdb933254ddfe253945bbe9898d4c2aa Mon Sep 17 00:00:00 2001
From: dannyrb <danny.ri.brown@gmail.com>
Date: Fri, 10 May 2019 14:04:57 -0400
Subject: [PATCH 16/26] Blurb regarding current state of tool management

---
 docs/latest/advanced/custom-tools.md | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/docs/latest/advanced/custom-tools.md b/docs/latest/advanced/custom-tools.md
index 399b04c8b..bed6c344f 100644
--- a/docs/latest/advanced/custom-tools.md
+++ b/docs/latest/advanced/custom-tools.md
@@ -1 +1,8 @@
 # Tool Management
+
+This is not yet exposed in an easy/convenient way. Most tools are currently
+added by creating new Viewport, Toolbar, and SOPInstanceHandler extension
+modules. You can read more about that approach in [extensions](./extensions.md).
+
+In the near future, we intend to improve the extensibility of tools for existing
+Viewports (like our Cornerstone.js and VTK.js viewports).

From 90812d123e4ea37e759a91718356912efa0637aa Mon Sep 17 00:00:00 2001
From: dannyrb <danny.ri.brown@gmail.com>
Date: Fri, 10 May 2019 14:51:59 -0400
Subject: [PATCH 17/26] Remove docker outline

---
 docs/latest/deployment/index.md | 12 ------------
 1 file changed, 12 deletions(-)

diff --git a/docs/latest/deployment/index.md b/docs/latest/deployment/index.md
index fd75f7192..493406dae 100644
--- a/docs/latest/deployment/index.md
+++ b/docs/latest/deployment/index.md
@@ -85,18 +85,6 @@ _Advanced_
 - [GCP + Cloudflare](/deployment/recipes/static-assets.md#gcp--cloudflare)
 - [Azure](/deployment/recipes/static-assets.md#azure)
 
-...
-
-#### Docker
-
-- Why Docker?
-  - Ship your environment
-  - "It works on my machine"
-
-_Ship Archive w/ Client:_ todo
-
-...
-
 ## Data
 
 The OHIF Viewer is able to connect to any data source that implements the [DICOM

From 252921c47012fe8581cc24e6c2984391eb21b9a1 Mon Sep 17 00:00:00 2001
From: dannyrb <danny.ri.brown@gmail.com>
Date: Fri, 10 May 2019 14:52:14 -0400
Subject: [PATCH 18/26] Point prepared users to the configuration docs

---
 docs/latest/deployment/index.md | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/docs/latest/deployment/index.md b/docs/latest/deployment/index.md
index 493406dae..a1172bbd2 100644
--- a/docs/latest/deployment/index.md
+++ b/docs/latest/deployment/index.md
@@ -95,7 +95,10 @@ support it yet, but it is gaining wider adoption.
 
 ### Configure Connection
 
-...
+If you have an existing archive and intend to host the OHIF Viewer at the same
+domain name as your archive, then connecting the two is as simple as following
+the steps layed out in our
+[Configuration Essentials Guide](./../essentials/configuration.md).
 
 ### What if I don't have an imaging archive?
 

From cc2d7e0864cfbe7b110bdb9ba82ffe1b63e82fda Mon Sep 17 00:00:00 2001
From: dannyrb <danny.ri.brown@gmail.com>
Date: Fri, 10 May 2019 14:52:31 -0400
Subject: [PATCH 19/26] No image archive? No problem

---
 docs/latest/deployment/index.md | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/docs/latest/deployment/index.md b/docs/latest/deployment/index.md
index a1172bbd2..b56941e74 100644
--- a/docs/latest/deployment/index.md
+++ b/docs/latest/deployment/index.md
@@ -100,7 +100,12 @@ domain name as your archive, then connecting the two is as simple as following
 the steps layed out in our
 [Configuration Essentials Guide](./../essentials/configuration.md).
 
-### What if I don't have an imaging archive?
+#### What if I don't have an imaging archive?
+
+We provide some guidance on configuring a local image archive in our
+[Data Source Essentials](./../essentials/data-source.md) guide. Hosting an
+archive remotely is a little trickier. You can check out some of our
+[advanced recipes](#recipes) for modeled setups that may work for you.
 
 ...
 

From bcf1e4058dc8299b94460469a98a8e3184b33a9f Mon Sep 17 00:00:00 2001
From: dannyrb <danny.ri.brown@gmail.com>
Date: Fri, 10 May 2019 14:52:46 -0400
Subject: [PATCH 20/26] On proxy and cors

---
 docs/latest/deployment/index.md | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/docs/latest/deployment/index.md b/docs/latest/deployment/index.md
index b56941e74..f8270cb87 100644
--- a/docs/latest/deployment/index.md
+++ b/docs/latest/deployment/index.md
@@ -107,6 +107,24 @@ We provide some guidance on configuring a local image archive in our
 archive remotely is a little trickier. You can check out some of our
 [advanced recipes](#recipes) for modeled setups that may work for you.
 
+#### What if I intend to host the OHIF Viewer at a different domain?
+
+There are two important steps to making sure this setup works:
+
+1. Your Image Archive needs to be exposed, in some way, to the open web. This
+   can be directly, or through a `reverse proxy`, but the Viewer needs _some
+   way_ to request it's data.
+2. \* Your Image Archive needs to have appropriate CORS (Cross-Origin Resource
+   Sharing) Headers
+
+> \* Cross-Origin Resource Sharing (CORS) is a mechanism that uses additional
+> HTTP headers to tell a browser to let a web application running at one origin
+> (domain) have permission to access selected resources from a server at a
+> different origin. - [MDN Web Docs: Web - Http - CORS][cors]
+
+Most image archives do not provide either of these features "out of the box".
+It's common to use IIS, Nginx, or Apache to route incoming requests and append
+appropriate headers. You
 ...
 
 #### Making sure your archive is accessible

From 24c807bc601c8d271f77923c8ce602f08f592e72 Mon Sep 17 00:00:00 2001
From: dannyrb <danny.ri.brown@gmail.com>
Date: Fri, 10 May 2019 14:53:09 -0400
Subject: [PATCH 21/26] What if my archive doesn't support DicomWeb?

---
 docs/latest/deployment/index.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/docs/latest/deployment/index.md b/docs/latest/deployment/index.md
index f8270cb87..291f54c86 100644
--- a/docs/latest/deployment/index.md
+++ b/docs/latest/deployment/index.md
@@ -125,6 +125,12 @@ There are two important steps to making sure this setup works:
 Most image archives do not provide either of these features "out of the box".
 It's common to use IIS, Nginx, or Apache to route incoming requests and append
 appropriate headers. You
+
+#### What if my archive doesn't support DicomWeb?
+
+> This is possible to do with the OHIF Viewer, but not as straightforward. Look
+> out for documentation on this subject in the near future.
+
 ...
 
 #### Making sure your archive is accessible

From c8130d1dc8ce963c1e15e11053d1d2c66e882394 Mon Sep 17 00:00:00 2001
From: dannyrb <danny.ri.brown@gmail.com>
Date: Fri, 10 May 2019 14:53:23 -0400
Subject: [PATCH 22/26] Outlining security section

---
 docs/latest/deployment/index.md | 28 +++++++++++++++++-----------
 1 file changed, 17 insertions(+), 11 deletions(-)

diff --git a/docs/latest/deployment/index.md b/docs/latest/deployment/index.md
index 291f54c86..70819826d 100644
--- a/docs/latest/deployment/index.md
+++ b/docs/latest/deployment/index.md
@@ -133,21 +133,27 @@ appropriate headers. You
 
 ...
 
-#### Making sure your archive is accessible
+### Securing Your Data
 
-- CORS
-- Proxy (dangers)
-- Note: PACS not meant to be directly accesible from Web
+> Feeling lost? Securing your data is important, and it can be hard to tell if
+> you've gotten it right. Don't hesitate to work with professional auditors, or
+> [enlist help from experts](./../help.md).
 
-#### Securing your data
+- Oauth OpenID-Connect
+- Experts
 
-- Reach out to experts
-- Recipes
+### Recipes
 
-### What if my archive doesn't support DICOM Web?
+We've included a few recipes for common deployment scenarios. There are many,
+many possible configurations, so please don't feel limited to these setups.
 
-- Mapping layer
-- GraphQL?
+- Script Include
+  - [Embedding the Viewer](deployment/recipes/embedded-viewer.md)
+- Stand-Alone
+  - [Build for Production](deployment/recipes/build-for-production.md)
+  - [Static](deployment/recipes/static-assets.md)
+  - [Nginx + Image Archive](deployment/recipes/nginx--image-archive.md)
+  - [User Account Control](deployment/recipes/user-account-control.md)
 
 <!--
   Links
@@ -162,5 +168,5 @@ appropriate headers. You
 [dicom-web-standard]: https://www.dicomstandard.org/dicomweb/
 [dicom-web]: https://en.wikipedia.org/wiki/DICOMweb
 [host-static-assets]: https://www.netlify.com/blog/2016/05/18/9-reasons-your-site-should-be-static/
-
+[cors]: https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS
 <!-- prettier-ignore-end -->

From 10e5f849fecec4dc296a36fa2861b69e7a69cf13 Mon Sep 17 00:00:00 2001
From: dannyrb <danny.ri.brown@gmail.com>
Date: Fri, 10 May 2019 15:09:13 -0400
Subject: [PATCH 23/26] Update data link

---
 docs/latest/SUMMARY.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/latest/SUMMARY.md b/docs/latest/SUMMARY.md
index d55c77812..f0483f59a 100644
--- a/docs/latest/SUMMARY.md
+++ b/docs/latest/SUMMARY.md
@@ -35,7 +35,7 @@
 - [Deployment](deployment/index.md)
   - [Embedded](deployment/index.md#embedded-viewer)
   - [Stand-alone](deployment/index.md#stand-alone-viewer)
-  - [Data]()
+  - [Data](deployment/index.md#data)
 - Recipes
   - Script Include
     - [Embedding the Viewer](deployment/recipes/embedded-viewer.md)

From e6eec6b1ad27576ce270f18f5f5d61614990edba Mon Sep 17 00:00:00 2001
From: dannyrb <danny.ri.brown@gmail.com>
Date: Fri, 10 May 2019 15:09:31 -0400
Subject: [PATCH 24/26] OIDC settings and security

---
 docs/latest/deployment/index.md | 43 ++++++++++++++++++++++++++++++---
 1 file changed, 40 insertions(+), 3 deletions(-)

diff --git a/docs/latest/deployment/index.md b/docs/latest/deployment/index.md
index 70819826d..8d5c19b16 100644
--- a/docs/latest/deployment/index.md
+++ b/docs/latest/deployment/index.md
@@ -124,7 +124,8 @@ There are two important steps to making sure this setup works:
 
 Most image archives do not provide either of these features "out of the box".
 It's common to use IIS, Nginx, or Apache to route incoming requests and append
-appropriate headers. You
+appropriate headers. You can find an example of this setup in our
+[Nginx + Image Archive Deployment Recipe](deployment/recipes/nginx--image-archive.md).
 
 #### What if my archive doesn't support DicomWeb?
 
@@ -139,8 +140,43 @@ appropriate headers. You
 > you've gotten it right. Don't hesitate to work with professional auditors, or
 > [enlist help from experts](./../help.md).
 
-- Oauth OpenID-Connect
-- Experts
+The OHIF Viewer can be configured to work with authorization servers that
+support one or more of the OpenID-Connect authorization flows. The Viewer finds
+it's OpenID-Connect settings on the `oidc` configuration key. You can set these
+values following the instructions laid out in the
+[Configuration Essentials Guide](./../essentials/configuration.md).
+
+_Example OpenID-Connect Settings:_
+
+```js
+window.config = {
+  ...
+  oidc: [
+    {
+      // ~ REQUIRED
+      // Authorization Server URL
+      authority: 'http://127.0.0.1/auth/realms/ohif',
+      client_id: 'ohif-viewer',
+      redirect_uri: 'http://127.0.0.1/callback', // `OHIFStandaloneViewer.js`
+      response_type: 'code', // "Authorization Code Flow"
+      scope: 'openid', // email profile openid
+      // ~ OPTIONAL
+      post_logout_redirect_uri: '/logout-redirect.html',
+    },
+  ],
+}
+```
+
+You can find an example of this setup in our
+[User Account Control Deployment Recipe](deployment/recipes/user-account-control.md).
+
+#### Choosing a Flow for the Viewer
+
+In general, we recommend using the "Authorization Code Flow" ( [see
+`response_type=code` here][code-flows]); however, the "Implicit Flow" ( [see
+`response_type=token` here][code-flows]) can work if additonal precautions are
+taken. If the flow you've chosen produces a JWT Token, it's validity can be used
+to secure access to your Image Archive as well.
 
 ### Recipes
 
@@ -169,4 +205,5 @@ many possible configurations, so please don't feel limited to these setups.
 [dicom-web]: https://en.wikipedia.org/wiki/DICOMweb
 [host-static-assets]: https://www.netlify.com/blog/2016/05/18/9-reasons-your-site-should-be-static/
 [cors]: https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS
+[code-flows]: https://medium.com/@darutk/diagrams-of-all-the-openid-connect-flows-6968e3990660
 <!-- prettier-ignore-end -->

From 83987f297c1f003ebd40ab1e920888fbf64720ac Mon Sep 17 00:00:00 2001
From: dannyrb <danny.ri.brown@gmail.com>
Date: Fri, 10 May 2019 15:12:46 -0400
Subject: [PATCH 25/26] Remove empty data blurb for now

---
 docs/latest/advanced/data.md | 9 ---------
 1 file changed, 9 deletions(-)
 delete mode 100644 docs/latest/advanced/data.md

diff --git a/docs/latest/advanced/data.md b/docs/latest/advanced/data.md
deleted file mode 100644
index 0279df004..000000000
--- a/docs/latest/advanced/data.md
+++ /dev/null
@@ -1,9 +0,0 @@
-# Data
-
-## Hierarchy
-
-Studies, Series, Instances, Frames
-
-## Display Sets
-
-## Measurements and Annotation

From 23eb3a427dca83c12ade7a1094413da80d6b8f99 Mon Sep 17 00:00:00 2001
From: dannyrb <danny.ri.brown@gmail.com>
Date: Fri, 10 May 2019 15:12:59 -0400
Subject: [PATCH 26/26] Remove data links from sidebar

---
 docs/latest/SUMMARY.md | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/docs/latest/SUMMARY.md b/docs/latest/SUMMARY.md
index f0483f59a..17944ac91 100644
--- a/docs/latest/SUMMARY.md
+++ b/docs/latest/SUMMARY.md
@@ -19,10 +19,6 @@
   - [Extensions](advanced/architecture.md#misc-extensions)
   - [Diagram](advanced/architecture.md#diagram)
   - [Common Questions](advanced/architecture.md#common-questions)
-- [Data](advanced/data.md)
-  - [Hierarchy](advanced/data.md#hierarchy)
-  - [Display Sets](advanced/data.md#display-sets)
-  - [Measurements & Annotations](advanced/data.md#measurements-and-annotations)
 - [Extensions](advanced/extensions.md)
   - [Overview](advanced/extensions.md#overview)
   - [Modules](advanced/extensions.md#modules)