chore(release): publish %s [skip ci]

- @ohif/extension-cornerstone@0.0.39-alpha.0 - @ohif/extension-dicom-html@0.0.4-alpha.0 - @ohif/extension-dicom-microscopy@0.0.9-alpha.0 - @ohif/extension-dicom-pdf@0.0.8-alpha.0 - @ohif/extension-vtk@0.1.4-alpha.0 - @ohif/core@0.11.1-alpha.0 - @ohif/i18n@0.2.3-alpha.0 - @ohif/ui@0.2.18-alpha.0 - @ohif/viewer@0.0.22-alpha.0
Catch more updates
2019-08-05 14:45:09 -04:00 · 2019-08-05 14:44:45 -04:00 · 2019-08-05 14:44:20 -04:00 · 2019-08-05 14:29:14 -04:00 · 2019-08-05 14:00:20 -04:00 · 2019-08-05 13:52:02 -04:00
2598 changed files with 106025 additions and 146439 deletions
@@ -1,6 +0,0 @@
-# Browsers that we support
-
-> 1%
-IE 11
-not dead
-not op_mini all
@@ -9,48 +9,33 @@ version: 2.1
 # create pull request previews and to update `https://docs.ohif.org`
 ###

-## https://github.com/cypress-io/circleci-orb
-##
 orbs:
  codecov: codecov/codecov@1.0.5
-  cypress: cypress-io/cypress@1.26.0
-executors:
-  # Custom executor to override Cypress config
-  deploy-to-prod-executor:
-    docker:
-      - image: cimg/node:16.14
-        environment:
-          CYPRESS_BASE_URL: https://ohif-staging.netlify.com/
-  chrome-and-pacs:
-    docker:
-      # Primary container image where all steps run.
-      - image: 'cypress/browsers:node16.14.2-slim-chrome103-ff102'

 defaults: &defaults
  docker:
-    - image: cimg/node:16.14-browsers
-      environment:
-        TERM: xterm # Enable colors in term
-        QUICK_BUILD: true
+    - image: circleci/node:10.16.0
  working_directory: ~/repo

 jobs:
-  ###
-  # Workflow: PR_CHECKS
-  ###
-  UNIT_TESTS:
+  PR_UNIT_TESTS:
    <<: *defaults
+
    steps:
-      # Update yarn
-      - run: yarn -v
+      # Enable yarn workspaces
+      - run: yarn config set workspaces-experimental true
+
      # Checkout code and ALL Git Tags
-      - checkout
+      - checkout:
+          post:
+            - git fetch --all
      - restore_cache:
          name: Restore Yarn and Cypress Package Cache
          keys:
            # when lock file changes, use increasingly general patterns to restore cache
-            - yarn-packages-{{ checksum "yarn.lock" }}
-            - yarn-packages-
+            - yarn-packages-v1-{{ .Branch }}-{{ checksum "yarn.lock" }}
+            - yarn-packages-v1-{{ .Branch }}-
+            - yarn-packages-v1-
      - run:
          name: Install Dependencies
          command: yarn install --frozen-lockfile
@@ -58,27 +43,30 @@ jobs:
          name: Save Yarn Package Cache
          paths:
            - ~/.cache ## Cache yarn and Cypress
-          key: yarn-packages-{{ checksum "yarn.lock" }}
+          key: yarn-packages-v1-{{ .Branch }}-{{ checksum "yarn.lock" }}
+
      # RUN TESTS
      - run:
-          name: 'JavaScript Test Suite'
+          name: "JavaScript Test Suite"
          command: yarn run test:unit:ci
-      # platform/app
+
+      # PLATFORM/VIEWER
      - run:
-          name: 'VIEWER: Combine report output'
+          name: "VIEWER: Combine report output"
          command: |
-            viewerCov="/home/circleci/repo/platform/app/coverage"
+            viewerCov="/home/circleci/repo/platform/viewer/coverage"
            touch "${viewerCov}/reports"
            cat "${viewerCov}/clover.xml" >> "${viewerCov}/reports"
            echo "\<<\<<\<< EOF" >> "${viewerCov}/reports"
            cat "${viewerCov}/lcov.info" >>"${viewerCov}/reports"
            echo "\<<\<<\<< EOF" >> "${viewerCov}/reports"
      - codecov/upload:
-          file: '/home/circleci/repo/platform/app/coverage/reports'
-          flags: 'viewer'
+          file: "/home/circleci/repo/platform/viewer/coverage/reports"
+          flags: "viewer"
+
      # PLATFORM/CORE
      - run:
-          name: 'CORE: Combine report output'
+          name: "CORE: Combine report output"
          command: |
            coreCov="/home/circleci/repo/platform/core/coverage"
            touch "${coreCov}/reports"
@@ -87,60 +75,27 @@ jobs:
            cat "${coreCov}/lcov.info" >> "${coreCov}/reports"
            echo "\<<\<<\<< EOF" >> "${coreCov}/reports"
      - codecov/upload:
-          file: '/home/circleci/repo/platform/core/coverage/reports'
-          flags: 'core'
+          file: "/home/circleci/repo/platform/core/coverage/reports"
+          flags: "core"

-  ###
-  # Workflow: PR_OPTIONAL_DOCKER_PUBLISH
-  ###
-  DOCKER_PR_PUBLISH:
+  MERGE_UNIT_TESTS:
    <<: *defaults
+
    steps:
      # Enable yarn workspaces
      - run: yarn config set workspaces-experimental true

      # Checkout code and ALL Git Tags
-      - checkout
+      - checkout:
+          post:
+            - git fetch --all
      - restore_cache:
          name: Restore Yarn and Cypress Package Cache
          keys:
            # when lock file changes, use increasingly general patterns to restore cache
-            - yarn-packages-{{ checksum "yarn.lock" }}
-            - yarn-packages-
-
-      - run:
-          name: Install Dependencies
-          command: yarn install --frozen-lockfile
-
-      - setup_remote_docker:
-          docker_layer_caching: false
-
-      - run:
-          name: Build and push Docker image
-          command: |
-            # Remove npm config
-            rm -f ./.npmrc
-            # Set our version number using vars
-            echo $CIRCLE_BUILD_NUM
-            # Build our image, auth, and push
-            docker build --tag ohif/app:PR_BUILD-$CIRCLE_BUILD_NUM .
-            echo $DOCKER_PWD | docker login -u $DOCKER_LOGIN --password-stdin
-            docker push ohif/app:PR_BUILD-$CIRCLE_BUILD_NUM
-
-  ###
-  # Workflow: DEPLOY
-  ###
-  BUILD:
-    <<: *defaults
-    steps:
-      # Checkout code and ALL Git Tags
-      - checkout
-      - restore_cache:
-          name: Restore Yarn and Cypress Package Cache
-          keys:
-            # when lock file changes, use increasingly general patterns to restore cache
-            - yarn-packages-{{ checksum "yarn.lock" }}
-            - yarn-packages-
+            - yarn-packages-v1-{{ .Branch }}-{{ checksum "yarn.lock" }}
+            - yarn-packages-v1-{{ .Branch }}-
+            - yarn-packages-v1-
      - run:
          name: Install Dependencies
          command: yarn install --frozen-lockfile
@@ -148,109 +103,150 @@ jobs:
          name: Save Yarn Package Cache
          paths:
            - ~/.cache ## Cache yarn and Cypress
-          key: yarn-packages-{{ checksum "yarn.lock" }}
-      # Build & Test
+          key: yarn-packages-v1-{{ .Branch }}-{{ checksum "yarn.lock" }}
+
+      # RUN TESTS
      - run:
-          name: 'Perform the versioning before build'
-          command: node ./version.mjs
+          name: "JavaScript Test Suite"
+          command: yarn run test:unit:ci
+
+      # PLATFORM/VIEWER
      - run:
-          name: 'Build the OHIF Viewer'
-          command: yarn run build
-          no_output_timeout: 45m
-      - run:
-          name: 'Upload SourceMaps, Send Deploy Notification'
+          name: "VIEWER: Combine report output"
          command: |
-            # export FILE_1=$(find ./build/static/js -type f -name "2.*.js" -exec basename {} \;)
-            # export FILE_MAIN=$(find ./build/static/js -type f -name "main.*.js" -exec basename {} \;)
-            # export FILE_RUNTIME_MAIN=$(find ./build/static/js -type f -name "runtime~main.*.js" -exec basename {} \;)
-            # curl https://api.rollbar.com/api/1/sourcemap -F source_map=@build/static/js/$FILE_1.map -F access_token=$ROLLBAR_TOKEN -F version=$CIRCLE_SHA1 -F minified_url=https://$GOOGLE_STORAGE_BUCKET/static/js/$FILE_1
-            # curl https://api.rollbar.com/api/1/sourcemap -F source_map=@build/static/js/$FILE_MAIN.map -F access_token=$ROLLBAR_TOKEN -F version=$CIRCLE_SHA1 -F minified_url=https://$GOOGLE_STORAGE_BUCKET/static/js/$FILE_MAIN
-            # curl https://api.rollbar.com/api/1/sourcemap -F source_map=@build/static/js/$FILE_RUNTIME_MAIN.map -F access_token=$ROLLBAR_TOKEN -F version=$CIRCLE_SHA1 -F minified_url=https://$GOOGLE_STORAGE_BUCKET/static/js/$FILE_RUNTIME_MAIN
-            curl --request POST https://api.rollbar.com/api/1/deploy/ -F access_token=$ROLLBAR_TOKEN -F environment=$GOOGLE_STORAGE_BUCKET -F revision=$CIRCLE_SHA1 -F local_username=CircleCI
+            viewerCov="/home/circleci/repo/platform/viewer/coverage"
+            touch "${viewerCov}/reports"
+            cat "${viewerCov}/clover.xml" >> "${viewerCov}/reports"
+            echo "\<<\<<\<< EOF" >> "${viewerCov}/reports"
+            cat "${viewerCov}/lcov.info" >>"${viewerCov}/reports"
+            echo "\<<\<<\<< EOF" >> "${viewerCov}/reports"
+      - codecov/upload:
+          file: "/home/circleci/repo/platform/viewer/coverage/reports"
+          flags: "viewer"
+
+      # PLATFORM/CORE
+      - run:
+          name: "CORE: Combine report output"
+          command: |
+            coreCov="/home/circleci/repo/platform/core/coverage"
+            touch "${coreCov}/reports"
+            cat "${coreCov}/clover.xml" >> "${coreCov}/reports"
+            echo "\<<\<<\<< EOF" >> "${coreCov}/reports"
+            cat "${coreCov}/lcov.info" >> "${coreCov}/reports"
+            echo "\<<\<<\<< EOF" >> "${coreCov}/reports"
+      - codecov/upload:
+          file: "/home/circleci/repo/platform/core/coverage/reports"
+          flags: "core"
+
      # Persist :+1:
      - persist_to_workspace:
          root: ~/repo
-          paths:
-            - platform/app/dist
-            - Dockerfile
-            - version.txt
-            - commit.txt
-            - version.json
+          paths: .

-  # DEPLOY_TO_DEV:
-  #   docker:
-  #     - image: circleci/node:16.14.0
-  #       environment:
-  #         TERM: xterm
-  #         NETLIFY_SITE_ID: 32708787-c9b0-4634-b50f-7ca41952da77
-  #   working_directory: ~/repo
-  #   steps:
-  #     - attach_workspace:
-  #         at: ~/repo
-  #     - run: cd .netlify && npm install
-  #     - run: cp .netlify/deploy-workflow/_redirects platform/app/dist/_redirects
-  #     - run: cd .netlify && npm run deploy
-
-  # DEPLOY_TO_STAGING:
-  #   docker:
-  #     - image: circleci/node:16.14.0
-  #       environment:
-  #         TERM: xterm
-  #         NETLIFY_SITE_ID: c7502ae3-b150-493c-8422-05701e44a969
-  #   working_directory: ~/repo
-  #   steps:
-  #     - attach_workspace:
-  #         at: ~/repo
-  #     - run: cd .netlify && npm install
-  #     - run: cp .netlify/deploy-workflow/_redirects platform/app/dist/_redirects
-  #     - run: cd .netlify && npm run deploy
-
-  # DEPLOY_TO_PRODUCTION:
-  #   docker:
-  #     - image: circleci/node:16.14.0
-  #       environment:
-  #         TERM: xterm
-  #         NETLIFY_SITE_ID: 79c4a5da-5c95-4dc9-84f7-45fd9dfe21b0
-  #   working_directory: ~/repo
-  #   steps:
-  #     - attach_workspace:
-  #         at: ~/repo
-  #     - run: cd .netlify && npm install
-  #     - run: cp .netlify/deploy-workflow/_redirects platform/app/dist/_redirects
-  #     - run: cd .netlify && npm run deploy
-
-  #   DEPLOY_TO_RELEASE_DEV:
-  #     docker:
-  #       - image: circleci/node:16.14.0
-  #         environment:
-  #           TERM: xterm
-  #           NETLIFY_SITE_ID: 3270878-22
-  #     working_directory: ~/repo
-  #     steps:
-  #       - attach_workspace:
-  #           at: ~/repo
-  #       - run: cd .netlify && npm install
-  #       - run:
-  #           cp .netlify/deploy-workflow/_redirects platform/app/dist/_redirects
-  #       - run: cd .netlify && npm run deploy
-
-  ###
-  # Workflow: RELEASE
-  ###
-  NPM_PUBLISH:
-    <<: *defaults
+  e2e_test:
+    working_directory: ~/repo
+    docker:
+      - image: cypress/base:8
+        environment:
+          ## this enables colors in the output
+          TERM: xterm
    steps:
-      - run: yarn -v
-      # Checkout code and ALL Git Tags
-      - checkout
      - attach_workspace:
          at: ~/repo
-      # Use increasingly general patterns to restore cache
      - restore_cache:
          name: Restore Yarn and Cypress Package Cache
          keys:
-            - yarn-packages-{{ checksum "yarn.lock" }}
-            - yarn-packages-
+            # when lock file changes, use increasingly general patterns to restore cache
+            - yarn-packages-v1-{{ .Branch }}-{{ checksum "yarn.lock" }}
+            - yarn-packages-v1-{{ .Branch }}-
+            - yarn-packages-v1-
+      # - run: $(yarn bin)/cypress run --record
+      # Shouldn't be needed if we're using a package cache that contains Cypress
+      # Could do a check here, if it doesn't exist, install cypress?
+      - run: yarn install
+      - run: yarn run test:e2e:ci
+
+  npm_publish:
+    <<: *defaults
+    steps:
+      - attach_workspace:
+          at: ~/repo
+      - run:
+          name: Avoid hosts unknown for github
+          command:
+            mkdir ~/.ssh/ && echo -e "Host github.com\n\tStrictHostKeyChecking
+            no\n" > ~/.ssh/config
+      # --no-ci argument is not ideal; however, semantic-rlease thinks we're
+      # attempting to run it from a `pr`, which is not the case
+      - run:
+          name: Publish using Semantic Release
+          command: npx semantic-release --debug
+      # Persist :+1:
+      - persist_to_workspace:
+          root: ~/repo
+          paths: .
+
+  docs_publish:
+    <<: *defaults
+    steps:
+      - attach_workspace:
+          at: ~/repo
+      - run:
+          name: Avoid hosts unknown for github
+          command:
+            mkdir ~/.ssh/ && echo -e "Host github.com\n\tStrictHostKeyChecking
+            no\n" > ~/.ssh/config
+      - run: git config --global user.email "gh-pages@localhost"
+      - run: git config --global user.name "npm gh-pages"
+      - run: yarn global add gh-pages
+      - run:
+          name: Generate Docs
+          command: yarn run staticDeploy
+      - run:
+          name: Publish Docs
+          command: yarn run docs:publish
+
+  docker_publish:
+    <<: *defaults
+    steps:
+      - attach_workspace:
+          at: ~/repo
+      - setup_remote_docker:
+          docker_layer_caching: true
+      - run:
+          name: Build and push Docker image
+          command: |
+            # This file will exist if a new version was published by
+            # our `semantic-release` command in the previous job
+            if [[ ! -e tmp/updated-version.txt ]]; then
+              exit 0
+            else
+              # Remove npm config
+              rm -f ./.npmrc
+              # Set our version number using vars
+              export IMAGE_VERSION=$(cat tmp/updated-version.txt)
+              export IMAGE_VERSION_FULL=v$IMAGE_VERSION.${CIRCLE_BUILD_NUM}
+              echo $IMAGE_VERSION
+              echo $IMAGE_VERSION_FULL
+              # Build our image, auth, and push
+              docker build --tag ohif/$IMAGE_NAME:$IMAGE_VERSION_FULL --tag ohif/$IMAGE_NAME:latest .
+              echo $DOCKER_PWD | docker login -u $DOCKER_LOGIN --password-stdin
+              docker push ohif/$IMAGE_NAME:$IMAGE_VERSION_FULL
+              docker push ohif/$IMAGE_NAME:latest
+            fi
+
+  build_demo_site:
+    <<: *defaults
+    steps:
+      # Download and cache dependencies
+      - checkout
+      - restore_cache:
+          name: Restore Yarn Package Cache
+          keys:
+            # when lock file changes, use increasingly general patterns to restore cache
+            - yarn-packages-v1-{{ .Branch }}-{{ checksum "yarn.lock" }}
+            - yarn-packages-v1-{{ .Branch }}-
+            - yarn-packages-v1-
      - run:
          name: Install Dependencies
          command: yarn install --frozen-lockfile
@@ -258,251 +254,90 @@ jobs:
          name: Save Yarn Package Cache
          paths:
            - ~/.cache/yarn
-          key: yarn-packages-{{ checksum "yarn.lock" }}
+          key: yarn-packages-v1-{{ .Branch }}-{{ checksum "yarn.lock" }}
+      # Build & Test
      - run:
-          name: Avoid hosts unknown for github
+          name: "Build Demo Site, Upload SourceMaps, Send Deploy Notification"
          command: |
-            rm -rf ~/.ssh
-            mkdir ~/.ssh/
-            echo -e "Host github.com\n\tStrictHostKeyChecking no\n" > ~/.ssh/config
-            git config --global user.email "danny.ri.brown+ohif-bot@gmail.com"
-            git config --global user.name "ohif-bot"
-      - run:
-          name: Authenticate with NPM registry
-          command:
-            echo "//registry.npmjs.org/:_authToken=$NPM_TOKEN" > ~/repo/.npmrc
-      - run:
-          name: Increase the event emitter limit
-          command: |
-            node ./increaseEventEmitterLimit.mjs
-      - run:
-          name: build half of the packages (to avoid out of memory in circleci)
-          command: |
-            yarn run build:package-all
-      - run:
-          name: build the other half of the packages
-          command: |
-            yarn run build:package-all-1
-      - run:
-          name: publish package versions
-          command: |
-            node ./publish-version.mjs
-      - run:
-          name: Again set the NPM registry (was deleted in the version script)
-          command:
-            echo "//registry.npmjs.org/:_authToken=$NPM_TOKEN" > ~/repo/.npmrc
-      - run:
-          name: publish package dist
-          command: |
-            node ./publish-package.mjs
+            yarn build:demo:ci
+            perl -i -pe 's#</head>#`cat .circleci/rollbar.html` #e' build/index.html
+            export FILE_1=$(find ./build/static/js -type f -name "2.*.js" -exec basename {} \;)
+            export FILE_MAIN=$(find ./build/static/js -type f -name "main.*.js" -exec basename {} \;)
+            export FILE_RUNTIME_MAIN=$(find ./build/static/js -type f -name "runtime~main.*.js" -exec basename {} \;)
+            curl https://api.rollbar.com/api/1/sourcemap -F source_map=@build/static/js/$FILE_1.map -F access_token=$ROLLBAR_TOKEN -F version=$CIRCLE_SHA1 -F minified_url=https://$GOOGLE_STORAGE_BUCKET/static/js/$FILE_1
+            curl https://api.rollbar.com/api/1/sourcemap -F source_map=@build/static/js/$FILE_MAIN.map -F access_token=$ROLLBAR_TOKEN -F version=$CIRCLE_SHA1 -F minified_url=https://$GOOGLE_STORAGE_BUCKET/static/js/$FILE_MAIN
+            curl https://api.rollbar.com/api/1/sourcemap -F source_map=@build/static/js/$FILE_RUNTIME_MAIN.map -F access_token=$ROLLBAR_TOKEN -F version=$CIRCLE_SHA1 -F minified_url=https://$GOOGLE_STORAGE_BUCKET/static/js/$FILE_RUNTIME_MAIN
+            curl --request POST https://api.rollbar.com/api/1/deploy/ -F access_token=$ROLLBAR_TOKEN -F environment=$GOOGLE_STORAGE_BUCKET -F revision=$CIRCLE_SHA1 -F local_username=CircleCI
+      # Persist :+1:
      - persist_to_workspace:
          root: ~/repo
-          paths:
-            - .
+          paths: .

-  DOCKER_RELEASE_PUBLISH:
-    <<: *defaults
+  demo_site_publish:
+    working_directory: ~/repo
+    docker:
+      - image: google/cloud-sdk
    steps:
      - attach_workspace:
          at: ~/repo
      - setup_remote_docker:
-          docker_layer_caching: false
+          docker_layer_caching: true
      - run:
-          name: Build and push Docker image from the release branch
+          name: Deploy latest version to viewer.ohif.org
          command: |
            # This file will exist if a new version was published by
-            # our command in the previous job.
-            if [[ ! -e version.txt ]]; then
-              exit 0
-            else
-              # Remove npm config
-              rm -f ./.npmrc
-              # Set our version number using vars
-              export IMAGE_VERSION=$(cat version.txt)
-              export IMAGE_VERSION_FULL=v$IMAGE_VERSION
-              echo $IMAGE_VERSION
-              echo $IMAGE_VERSION_FULL
-              # Build our image, auth, and push
-              docker build --tag ohif/app:$IMAGE_VERSION_FULL --tag ohif/app:latest .
-              echo $DOCKER_PWD | docker login -u $DOCKER_LOGIN --password-stdin
-              docker push ohif/app:$IMAGE_VERSION_FULL
-              docker push ohif/app:latest
-            fi
+            # our `semantic-release` command in the previous job
+            #if [[ ! -e tmp/updated-version.txt ]]; then
+            #  exit 0
+            #else
+              echo $GCLOUD_SERVICE_KEY | gcloud auth activate-service-account --key-file=-
+              gcloud --quiet config set project ${GOOGLE_PROJECT_ID}
+              gcloud --quiet config set compute/zone ${GOOGLE_COMPUTE_ZONE}

-  DOCKER_BETA_PUBLISH:
-    <<: *defaults
-    steps:
-      - attach_workspace:
-          at: ~/repo
-      - setup_remote_docker:
-          docker_layer_caching: false
-      - run:
-          name:
-            Build and push Docker image from the master branch (beta releases)
-          command: |
-            echo $(ls -l)
-
-            # This file will exist if a new version was published by
-            # our command in the previous job.
-            if [[ ! -e version.txt ]]; then
-              echo "don't have version txt"
-              exit 0
-            else
-              echo "Building and pushing Docker image from the master branch (beta releases)"
-              rm -f ./.npmrc
-              # Set our version number using vars
-              export IMAGE_VERSION=$(cat version.txt)
-              export IMAGE_VERSION_FULL=v$IMAGE_VERSION
-              echo $IMAGE_VERSION
-              echo $IMAGE_VERSION_FULL
-              # Build our image, auth, and push
-
-              echo "starting docker build"
-              docker build --tag ohif/app:$IMAGE_VERSION_FULL .
-              echo $DOCKER_PWD | docker login -u $DOCKER_LOGIN --password-stdin
-
-              echo "starting docker push"
-              docker push ohif/app:$IMAGE_VERSION_FULL
-            fi
+              gsutil -m rm gs://$GOOGLE_STORAGE_BUCKET/**
+              gsutil -m rsync -R build gs://$GOOGLE_STORAGE_BUCKET
+            #fi

 workflows:
  version: 2

-  PR_CHECKS:
+  # PULL REQUESTS
+  pull_requests:
    jobs:
-      - UNIT_TESTS
+      - PR_UNIT_TESTS:
+          filters:
+            branches:
+              ignore:
+                - master
+                - feature/*
+                - hotfix/*

-      # E2E: PWA
-      - cypress/run:
-          name: 'E2E: PWA'
-          executor: chrome-and-pacs
-          browser: chrome
-          pre-steps:
-            - run: |
-                # Clear yarn cache; use yarn from image (update image to update yarn)
-                rm -rf ~/.yarn
-                yarn -v
-          yarn: true
-          record: true
-          store_artifacts: true
-          working_directory: platform/app
-          build: yarn test:data
-          start: yarn run test:e2e:serve
-          spec: 'cypress/integration/**/*'
-          wait-on: 'http://localhost:3000'
-          cache-key: 'yarn-packages-{{ checksum "yarn.lock" }}'
-          no-workspace: true # Don't persist workspace
-          post-steps:
-            - store_artifacts:
-                path: platform/app/cypress/screenshots
-            - store_artifacts:
-                path: platform/app/cypress/videos
-            - store_test_results:
-                path: platform/app/cypress/results
-          requires:
-            - UNIT_TESTS
-
-  PR_OPTIONAL_VISUAL_TESTS:
+  # MERGE TO MASTER
+  cut_release:
    jobs:
-      - AWAIT_APPROVAL:
-          type: approval
-      # Update hub.docker.org
-      - cypress/run:
-          name: 'Generate Percy Snapshots'
-          executor: cypress/browsers-chrome76
-          browser: chrome
-          pre-steps:
-            - run: 'rm -rf ~/.yarn && yarn -v && yarn global add wait-on'
-          yarn: true
-          store_artifacts: false
-          working_directory: platform/app
-          build:
-            yarn test:data && npx cross-env QUICK_BUILD=true
-            APP_CONFIG=config/dicomweb-server.js yarn run build
-          # start server --> verify running --> percy + chrome + cypress
-          command: yarn run test:e2e:dist
-          cache-key: 'yarn-packages-{{ checksum "yarn.lock" }}'
-          no-workspace: true # Don't persist workspace
-          post-steps:
-            - store_artifacts:
-                path: platform/app/cypress/screenshots
-            - store_artifacts:
-                path: platform/app/cypress/videos
-          requires:
-            - AWAIT_APPROVAL
-
-  # Our master branch deploys to viewer-dev.ohif.org, the viewer.ohif.org is
-  # deployed from the release branch which is more stable and less frequently updated.
-  DEPLOY_MASTER:
-    jobs:
-      - BUILD:
+      - MERGE_UNIT_TESTS:
          filters:
            branches:
              only: master
-      - NPM_PUBLISH:
+      - e2e_test:
          requires:
-            - BUILD
-      - DOCKER_BETA_PUBLISH:
+            - MERGE_UNIT_TESTS
+      # Update NPM
+      - npm_publish:
          requires:
-            - NPM_PUBLISH
-
-  # Our release branch deploys to viewer.ohif.org and is more stable and less
-  # frequently updated after being tested in the staging environment.
-  DEPLOY_RELEASE:
-    jobs:
-      - BUILD:
-          filters:
-            branches:
-              only: release
-      - NPM_PUBLISH:
+            - e2e_test
+      # Update docs.ohif.org
+      - docs_publish:
          requires:
-            - BUILD
-      - DOCKER_RELEASE_PUBLISH:
+            - e2e_test
+      # Update hub.docker.org
+      - docker_publish:
          requires:
-            - NPM_PUBLISH
-  ###
-  # Unit and E2E tests have already run for PR_CHECKS
-  # Re-running should not gain us any confidence here
-  ###
-  # RELEASE:
-  #   jobs:
-  #     - NPM_PUBLISH:
-  #         filters:
-  #           branches:
-  #             only: master
-  #     - DOCS_PUBLISH:
-  #         filters:
-  #           branches:
-  #             only: master
-  #     # Update base branch snapshots
-  #     # and record a Cypress dashboard test run
-  #     - cypress/run:
-  #         name: 'Generate Percy Snapshots'
-  #         executor: cypress/browsers-chrome76
-  #         browser: chrome
-  #         pre-steps:
-  #           - run: 'rm -rf ~/.yarn && npm i -g yarn && yarn -v && yarn global
-  #               add wait-on' # Use yarn latest
-  #         yarn: true
-  #         store_artifacts: false
-  #         working_directory: platform/app
-  #         build:
-  #           npx cross-env QUICK_BUILD=true APP_CONFIG=config/e2e.js yarn run
-  #           build
-  #         # start server --> verify running --> percy + chrome + cypress
-  #         command: yarn run test:e2e:dist
-  #         cache-key: 'yarn-packages-{{ checksum "yarn.lock" }}'
-  #         no-workspace: true # Don't persist workspace
-  #         post-steps:
-  #           - store_artifacts:
-  #               path: platform/app/cypress/screenshots
-  #           - store_artifacts:
-  #               path: platform/app/cypress/videos
-  #           - store_test_results:
-  #               path: platform/app/cypress/results
-  #         filters:
-  #           branches:
-  #             only: master
-  #     - DOCKER_MASTER_PUBLISH:
-  #         requires:
-  #           - NPM_PUBLISH
+            - npm_publish
+      # Update viewer.ohif.org
+      - build_demo_site:
+          requires:
+            - e2e_test
+      - demo_site_publish:
+          requires:
+            - build_demo_site
@@ -0,0 +1,15 @@
+<script>
+// Note: This is a client access token so there is no issue with having it publicly available
+var _rollbarConfig = {
+    accessToken: "739c64cd39e84592ba062bc29aac9769",
+    captureUncaught: true,
+    captureUnhandledRejections: true,
+    payload: {
+        environment: "viewer.ohif.org"
+    }
+};
+// Rollbar Snippet
+!function(r){var e={};function o(n){if(e[n])return e[n].exports;var t=e[n]={i:n,l:!1,exports:{}};return r[n].call(t.exports,t,t.exports,o),t.l=!0,t.exports}o.m=r,o.c=e,o.d=function(r,e,n){o.o(r,e)||Object.defineProperty(r,e,{enumerable:!0,get:n})},o.r=function(r){"undefined"!=typeof Symbol&&Symbol.toStringTag&&Object.defineProperty(r,Symbol.toStringTag,{value:"Module"}),Object.defineProperty(r,"__esModule",{value:!0})},o.t=function(r,e){if(1&e&&(r=o(r)),8&e)return r;if(4&e&&"object"==typeof r&&r&&r.__esModule)return r;var n=Object.create(null);if(o.r(n),Object.defineProperty(n,"default",{enumerable:!0,value:r}),2&e&&"string"!=typeof r)for(var t in r)o.d(n,t,function(e){return r[e]}.bind(null,t));return n},o.n=function(r){var e=r&&r.__esModule?function(){return r.default}:function(){return r};return o.d(e,"a",e),e},o.o=function(r,e){return Object.prototype.hasOwnProperty.call(r,e)},o.p="",o(o.s=0)}([function(r,e,o){var n=o(1),t=o(4);_rollbarConfig=_rollbarConfig||{},_rollbarConfig.rollbarJsUrl=_rollbarConfig.rollbarJsUrl||"https://cdnjs.cloudflare.com/ajax/libs/rollbar.js/2.7.1/rollbar.min.js",_rollbarConfig.async=void 0===_rollbarConfig.async||_rollbarConfig.async;var a=n.setupShim(window,_rollbarConfig),l=t(_rollbarConfig);window.rollbar=n.Rollbar,a.loadFull(window,document,!_rollbarConfig.async,_rollbarConfig,l)},function(r,e,o){var n=o(2);function t(r){return function(){try{return r.apply(this,arguments)}catch(r){try{console.error("[Rollbar]: Internal error",r)}catch(r){}}}}var a=0;function l(r,e){this.options=r,this._rollbarOldOnError=null;var o=a++;this.shimId=function(){return o},"undefined"!=typeof window&&window._rollbarShims&&(window._rollbarShims[o]={handler:e,messages:[]})}var i=o(3),d=function(r,e){return new l(r,e)},c=function(r){return new i(d,r)};function s(r){return t(function(){var e=Array.prototype.slice.call(arguments,0),o={shim:this,method:r,args:e,ts:new Date};window._rollbarShims[this.shimId()].messages.push(o)})}l.prototype.loadFull=function(r,e,o,n,a){var l=!1,i=e.createElement("script"),d=e.getElementsByTagName("script")[0],c=d.parentNode;i.crossOrigin="",i.src=n.rollbarJsUrl,o||(i.async=!0),i.onload=i.onreadystatechange=t(function(){if(!(l||this.readyState&&"loaded"!==this.readyState&&"complete"!==this.readyState)){i.onload=i.onreadystatechange=null;try{c.removeChild(i)}catch(r){}l=!0,function(){var e;if(void 0===r._rollbarDidLoad){e=new Error("rollbar.js did not load");for(var o,n,t,l,i=0;o=r._rollbarShims[i++];)for(o=o.messages||[];n=o.shift();)for(t=n.args||[],i=0;i<t.length;++i)if("function"==typeof(l=t[i])){l(e);break}}"function"==typeof a&&a(e)}()}}),c.insertBefore(i,d)},l.prototype.wrap=function(r,e,o){try{var n;if(n="function"==typeof e?e:function(){return e||{}},"function"!=typeof r)return r;if(r._isWrap)return r;if(!r._rollbar_wrapped&&(r._rollbar_wrapped=function(){o&&"function"==typeof o&&o.apply(this,arguments);try{return r.apply(this,arguments)}catch(o){var e=o;throw e&&("string"==typeof e&&(e=new String(e)),e._rollbarContext=n()||{},e._rollbarContext._wrappedSource=r.toString(),window._rollbarWrappedError=e),e}},r._rollbar_wrapped._isWrap=!0,r.hasOwnProperty))for(var t in r)r.hasOwnProperty(t)&&(r._rollbar_wrapped[t]=r[t]);return r._rollbar_wrapped}catch(e){return r}};for(var p="log,debug,info,warn,warning,error,critical,global,configure,handleUncaughtException,handleUnhandledRejection,captureEvent,captureDomContentLoaded,captureLoad".split(","),u=0;u<p.length;++u)l.prototype[p[u]]=s(p[u]);r.exports={setupShim:function(r,e){if(r){var o=e.globalAlias||"Rollbar";if("object"==typeof r[o])return r[o];r._rollbarShims={},r._rollbarWrappedError=null;var a=new c(e);return t(function(){e.captureUncaught&&(a._rollbarOldOnError=r.onerror,n.captureUncaughtExceptions(r,a,!0),n.wrapGlobals(r,a,!0)),e.captureUnhandledRejections&&n.captureUnhandledRejections(r,a,!0);var t=e.autoInstrument;return!1!==e.enabled&&(void 0===t||!0===t||"object"==typeof t&&t.network)&&r.addEventListener&&(r.addEventListener("load",a.captureLoad.bind(a)),r.addEventListener("DOMContentLoaded",a.captureDomContentLoaded.bind(a))),r[o]=a,a})()}},Rollbar:c}},function(r,e){function o(r,e,o){if(e.hasOwnProperty&&e.hasOwnProperty("addEventListener")){for(var n=e.addEventListener;n._rollbarOldAdd&&n.belongsToShim;)n=n._rollbarOldAdd;var t=function(e,o,t){n.call(this,e,r.wrap(o),t)};t._rollbarOldAdd=n,t.belongsToShim=o,e.addEventListener=t;for(var a=e.removeEventListener;a._rollbarOldRemove&&a.belongsToShim;)a=a._rollbarOldRemove;var l=function(r,e,o){a.call(this,r,e&&e._rollbar_wrapped||e,o)};l._rollbarOldRemove=a,l.belongsToShim=o,e.removeEventListener=l}}r.exports={captureUncaughtExceptions:function(r,e,o){if(r){var n;if("function"==typeof e._rollbarOldOnError)n=e._rollbarOldOnError;else if(r.onerror){for(n=r.onerror;n._rollbarOldOnError;)n=n._rollbarOldOnError;e._rollbarOldOnError=n}var t=function(){var o=Array.prototype.slice.call(arguments,0);!function(r,e,o,n){r._rollbarWrappedError&&(n[4]||(n[4]=r._rollbarWLine truncated
+// End Rollbar Snippet
+</script>
+</head>
@@ -8,13 +8,11 @@ coverage:
  status:
    project:
      default:
-        threshold: 0.5%
+        threshold: 0.10%
      core:
        flags: core
-        threshold: 0.5%
      viewer:
        flags: viewer
-        threshold: 0.5%
    patch: off
 flags:
  core:
@@ -22,4 +20,4 @@ flags:
      - platform/core
  viewer:
    paths:
-      - platform/app
+      - platform/viewer
@@ -1,23 +0,0 @@
-version: '3.5'
-
-services:
-  orthanc:
-    image: jodogne/orthanc-plugins:1.11.0
-    hostname: orthanc
-    volumes:
-      # Config
-      - ./config/orthanc.json:/etc/orthanc/orthanc.json:ro
-      # Persist data
-      - ./volumes/orthanc-db/:/var/lib/orthanc/db/
-    ports:
-      - '4242:4242' # DICOM
-      - '8042:8042' # Web
-    restart: unless-stopped
-  nginx:
-    image: nginx:latest
-    volumes:
-      - ./config/nginx.conf:/etc/nginx/nginx.conf
-    ports:
-      - '80:80' #ngnix proxy
-    depends_on:
-      - orthanc
@@ -1,43 +0,0 @@
-# Docker compose files
-
-This folder contains docker-compose files used to spin up OHIF-Viewer with
-different options such as locally or with any PAS you desire to
-
-## Public Server
-
-## Local Orthanc
-
-### Build
-
-`$ docker-compose -f docker-compose-orthanc.yml build`
-
-### Run
-
-Starts containers and leaves them running in the background.
-
-`$ docker-compose -f docker-compose-orthanc.yml up -d`
-
-then, access the application at [http://localhost](http://localhost)
-
-**remember that you have to access orthanc application and include your studies
-there**
-
-## Local Dcm4chee
-
-#### build
-
-`$ docker-compose -f docker-compose-dcm4chee.yml build`
-
-#### run
-
-`$ docker-compose -f docker-compose-dcm4chee.yml up -d`
-
-then, access the application at [http://localhost](http://localhost)
-
-**remember that you have to access dcm4chee application and include your studies
-there** You can use the following command to import your studies into dcm4che
-
-`$ docker run -v {YOUR_STUDY_FOLDER}:/tmp --rm --network=docker_dcm4che_default dcm4che/dcm4che-tools:5.14.0 storescu -cDCM4CHEE@arc:11112 /tmp`
-
-**make sure that your Docker network name is docker_dcm4chee_default or change
-it to the right one**
@@ -1,19 +0,0 @@
-server {
-  listen ${PORT};
-  location / {
-    root   /usr/share/nginx/html;
-    index  index.html index.htm;
-    try_files $uri $uri/ /index.html;
-    add_header Cross-Origin-Opener-Policy same-origin;
-    add_header Cross-Origin-Embedder-Policy require-corp;
-    add_header Cross-Origin-Resource-Policy same-origin;
-    proxy_set_header Host $host;
-    proxy_set_header X-Real-IP $remote_addr;
-    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
-    proxy_set_header X-Forwarded-Proto $http_x_forwarded_proto;
-  }
-  error_page   500 502 503 504  /50x.html;
-  location = /50x.html {
-    root   /usr/share/nginx/html;
-  }
-}
@@ -1,35 +0,0 @@
-#!/bin/sh
-
-envsubst '${PORT}' < /usr/src/default.conf.template > /etc/nginx/conf.d/default.conf
-
-if [ -n "$CLIENT_ID" ] || [ -n "$HEALTHCARE_API_ENDPOINT" ]
-  then
-    # If CLIENT_ID is specified, use the google.js configuration with the modified ID
-    if [ -n "$CLIENT_ID" ]
-      then
-  	    echo "Google Cloud Healthcare \$CLIENT_ID has been provided: "
-  	    echo "$CLIENT_ID"
-  	    echo "Updating config..."
-
-  	    # - Use SED to replace the CLIENT_ID that is currently in google.js
-	      sed -i -e "s/YOURCLIENTID.apps.googleusercontent.com/$CLIENT_ID/g" /usr/share/nginx/html/google.js
-	  fi
-
-    # If HEALTHCARE_API_ENDPOINT is specified, use the google.js configuration with the modified endpoint
-    if [ -n "$HEALTHCARE_API_ENDPOINT" ]
-      then
-        echo "Google Cloud Healthcare \$HEALTHCARE_API_ENDPOINT has been provided: "
-        echo "$HEALTHCARE_API_ENDPOINT"
-        echo "Updating config..."
-
-        # - Use SED to replace the HEALTHCARE_API_ENDPOINT that is currently in google.js
-        sed -i -e "s+https://healthcare.googleapis.com/v1+$HEALTHCARE_API_ENDPOINT+g" /usr/share/nginx/html/google.js
-    fi
-
-	  # - Copy google.js to overwrite app-config.js
-	  cp /usr/share/nginx/html/google.js /usr/share/nginx/html/app-config.js
-fi
-
-echo "Starting Nginx to serve the OHIF Viewer..."
-
-exec "$@"
@@ -1,30 +0,0 @@
-# Reduces size of context and hides
-# files from Docker (can't COPY or ADD these)
-
-# Output
-dist/
-build/
-
-# Dependencies
-node_modules/
-
-# Root
-README.md
-Dockerfile
-dockerfile
-
-# Misc. Config
-.git
-.DS_Store
-.gitignore
-.vscode
-.circleci
-
-# Unnecessary things to pull into container
-.circleci/
-.github/
-.netlify/
-.scripts/
-.vscode/
-coverage/
-docs/
@@ -1 +0,0 @@
-PERCY_TOKEN=<your token here>
@@ -1,4 +0,0 @@
-config/**
-docs/**
-img/**
-node_modules
@@ -0,0 +1,23 @@
+{
+  "extends": [
+    "react-app",
+    "eslint:recommended",
+    "plugin:react/recommended",
+    "plugin:prettier/recommended"
+  ],
+  "parser": "babel-eslint",
+  "env": {
+    "jest": true
+  },
+  "settings": {
+    "react": {
+      "version": "detect"
+    }
+  },
+  "globals": {
+    "cy": true,
+    "context": true,
+    "Cypress": true,
+    "assert": true
+  }
+}
@@ -1,31 +0,0 @@
-{
-  "plugins": [
-    "@typescript-eslint",
-    "import",
-    "eslint-plugin-tsdoc",
-    "prettier"
-  ],
-  "extends": [
-    "react-app",
-    "eslint:recommended",
-    "plugin:react/recommended",
-    "plugin:@typescript-eslint/recommended",
-    "plugin:prettier/recommended"
-  ],
-  "parser": "@typescript-eslint/parser",
-  "env": {
-    "jest": true
-  },
-  "settings": {
-    "react": {
-      "version": "detect"
-    }
-  },
-  "globals": {
-    "cy": true,
-    "before": true,
-    "context": true,
-    "Cypress": true,
-    "assert": true
-  }
-}
@@ -1,5 +0,0 @@
-# Set the default behavior,
-# in case people don't have core.autocrlf set.
-* text=auto
-# Declares that files will always have CRLF line ends
-*.sh text eol=lf
@@ -1 +0,0 @@
-custom: https://giving.massgeneral.org/ohif
@@ -1,86 +0,0 @@
-name: 'Bug report'
-description: Create a report to help us improve
-title: '[Bug] '
-labels: ['Community: Report :bug:', 'Awaiting Reproduction']
-
-body:
-  - type: markdown
-    attributes:
-      value: |
-        👋 Hello, and thank you for contributing to our project! Your support is greatly appreciated.
-
-        🔍 Before proceeding, please make sure to read our [Rules of Conduct](https://github.com/OHIF/Viewers/blob/master/CODE_OF_CONDUCT.md) and familiarize yourself with our [development process](https:/docs.ohif.org/development/our-process).
-
-        ❓ If you're here to seek general support or ask a question, we encourage you to visit our [community discussion board](https://community.ohif.org/)
-
-        🐞 For bug reports, please complete the following template in as much detail as possible. This will help us reproduce and address the issue efficiently.
-
-        🧪 Finally, ensure that you're using the latest version of the software and check if your issue has already been reported to avoid duplicates.
-
-  - type: textarea
-    id: bug_description
-    attributes:
-      label: Describe the Bug
-      description: 'A clear and concise description of what the bug is.'
-    validations:
-      required: true
-
-  - type: textarea
-    id: reproduction_steps
-    attributes:
-      label: Steps to Reproduce
-      description: 'Please describe the steps to reproduce the issue.'
-      placeholder: "1. First step\n2. Second step\n3. ..."
-    validations:
-      required: true
-
-  - type: textarea
-    id: current_behavior
-    attributes:
-      label: The current behavior
-      description:
-        'A clear and concise description of what happens instead of the expected
-        behavior.'
-    validations:
-      required: true
-
-  - type: textarea
-    id: expected_behavior
-    attributes:
-      label: The expected behavior
-      description:
-        'A clear and concise description of what you expected to happen.'
-    validations:
-      required: true
-
-  - type: input
-    id: os
-    attributes:
-      label: 'OS'
-      description: 'Your operating system.'
-      placeholder: 'e.g., Windows 10, macOS 10.15.4'
-    validations:
-      required: true
-  - type: input
-    id: node-version
-    attributes:
-      label: 'Node version'
-      description: 'Your Node.js version.'
-      placeholder: 'e.g., 16.14.0'
-    validations:
-      required: true
-  - type: input
-    id: browser
-    attributes:
-      label: 'Browser'
-      description: 'Your browser.'
-      placeholder: 'e.g., Chrome 83.0.4103.116, Firefox 77.0.1, Safari 13.1.1'
-    validations:
-      required: true
-
-  - type: markdown
-    attributes:
-      value: >
-        > :warning: Reports we cannot reproduce are at risk of being marked
-        stale and > closed. The more information you can provide, the more
-        likely we are to look > into and address your issue.
@@ -1,5 +0,0 @@
-blank_issues_enabled: false
-contact_links:
-  - name: 🤗 Support Question
-    url: https://community.ohif.org/
-    about: Please use our forum if you have questions or need help.
@@ -1,36 +0,0 @@
-name: Feature request
-description: Create a feature request
-labels: ['Community: Request :hand:']
-title: '[Feature Request] '
-body:
-  - type: markdown
-    attributes:
-      value: |
-        👋 Hello and thank you for your interest in our project!
-
-        🔍 Before you proceed, please read our [Rules of Conduct](https://github.com/OHIF/Viewers/blob/master/CODE_OF_CONDUCT.md).
-
-        🚀 If your request is specific to your needs, consider contributing it yourself! Read our [contributing guides](https://docs.ohif.org/development/contributing) to get started.
-
-        🖊️ Please provide as much detail as possible for your feature request. Mock-up screenshots, workflow or logic flow diagrams are very helpful. Discuss how your requested feature would interact with existing features.
-
-        ⏱️ Lastly, tell us why we should prioritize your feature. What impact would it have?
-
-  - type: textarea
-    attributes:
-      label: 'What feature or change would you like to see made?'
-      description:
-        'Please include as much detail as possible including possibly mock up
-        screen shots, workflow or logic flow diagrams etc.'
-      placeholder: '...'
-    validations:
-      required: true
-  - type: textarea
-    attributes:
-      label: 'Why should we prioritize this feature?'
-      description:
-        'Discuss if and how the requested feature interacts with existing
-        features.'
-      placeholder: '...'
-    validations:
-      required: true
@@ -1,93 +0,0 @@
-<!-- Do Not Delete This! pr_template -->
-<!-- Please read our Rules of Conduct: https://github.com/OHIF/Viewers/blob/master/CODE_OF_CONDUCT.md -->
-<!-- 🕮 Read our guide about our Contributing Guide here https://docs.ohif.org/development/contributing -->
-<!-- :hand: Thank you for starting this amazing contribution! -->
-
-<!--
-⚠️⚠️ Please make sure the checklist section below is complete before submitting your PR.
-To complete the checklist, add an 'x' to each item: [] -> [x]
-(PRs that do not have all the checkboxes marked will not be approved)
-->
-
-### Context
-
-<!--
-Provide a clear explanation of the reasoning behind this change, such as:
- A link to the issue being addressed, using the format "Fixes #ISSUE_NUMBER"
- An image showing the issue or problem being addressed (if not already in the issue)
- Error logs or callStacks to help with the understanding of the problem (if not already in the issue)
-->
-
-### Changes & Results
-
-<!--
-List all the changes that have been done, such as:
- Add new components
- Remove old components
- Update dependencies
-
-What are the effects of this change?
- Before vs After
- Screenshots / GIFs / Videos
-->
-
-### Testing
-
-<!--
-Describe how we can test your changes.
- open a URL
- visit a page
- click on a button
- etc.
-->
-
-### Checklist
-
-#### PR
-
-<!--
-https://semantic-release.gitbook.io/semantic-release/#how-does-it-work
-
-Examples:
-Please note the letter casing in the provided examples (upper or lower).
-
- feat(MeasurementService): add ...
- fix(Toolbar): fix ...
- docs(Readme): update ...
- style(Whitespace): fix ...
- refactor(ExtensionManager): ...
- test(HangingProtocol): Add test ...
- chore(git): update ...
- perf(VolumeLoader): ...
-
-You don't need to have each commit within the Pull Request follow the rule,
-but the PR title must comply with it, as it will be used as the commit message
-after the commits are squashed.
-->
-
- [] My Pull Request title is descriptive, accurate and follows the
-  semantic-release format and guidelines.
-
-#### Code
-
- [] My code has been well-documented (function documentation, inline comments,
-  etc.)
-
-#### Public Documentation Updates
-
-<!-- https://docs.ohif.org/ -->
-
- [] The documentation page has been updated as necessary for any public API
-  additions or removals.
-
-#### Tested Environment
-
- [] OS: <!--[e.g. Windows 10, macOS 10.15.4]-->
- [] Node version: <!--[e.g. 16.14.0]-->
- [] Browser:
-  <!--[e.g. Chrome 83.0.4103.116, Firefox 77.0.1, Safari 13.1.1]-->
-
-<!-- prettier-ignore-start -->
-[blog]: https://circleci.com/blog/triggering-trusted-ci-jobs-on-untrusted-forks/
-[script]: https://github.com/jklukas/git-push-fork-to-upstream-branch
-<!-- prettier-ignore-end -->
@@ -1,26 +0,0 @@
-# GitHub App: Stale
-# https://github.com/apps/stale
-#
-# Number of days of inactivity before an issue becomes stale
-daysUntilStale: 180
-# Number of days of inactivity before a stale issue is closed
-daysUntilClose: 60
-# Issues with these labels will never be considered stale
-exemptLabels:
-  - 'Bug: Verified :bug:'
-  - 'PR: Awaiting Review 👀'
-  - 'Announcement 🎉'
-  - 'IDC:priority'
-  - 'IDC:candidate'
-  - 'IDC:collaboration'
-  - 'Community: Request :hand:'
-  - 'Community: Report :bug:'
-# Label to use when marking an issue as stale
-staleLabel: 'Stale :baguette_bread:'
-# Comment to post when marking an issue as stale. Set to `false` to disable
-markComment: >
-  This issue has been automatically marked as stale because it has not had
-  recent activity. It will be closed if no further activity occurs. Thank you
-  for your contributions.
-# Comment to post when closing a stale issue. Set to `false` to disable
-closeComment: false
@@ -8,13 +8,11 @@ docs/_book
 src/version.js
 junit.xml
 coverage/
-.docz/
-.yarn/

 # YALC (for Erik)
 .yalc
 yalc.lock
-*.dcm
+
 # Logging, System files, misc.
 .idea/
 .npm
@@ -22,8 +20,6 @@ npm-debug.log
 package-lock.json
 yarn-error.log
 .DS_Store
-.env
-*.code-workspace

 # Common Example Data Directories
 sampledata/
@@ -31,14 +27,4 @@ example/deps/
 docker/dcm4che/dcm4che-arc

 # Cypress test results
-videos/
-screenshots/
-
-# Locize settings
-.locize
-
-# autogenerated files
-platform/app/src/pluginImports.js
-/Viewers.iml
-platform/app/.recipes/Nginx-Dcm4Che/dcm4che/dcm4che-arc/*
-platform/app/.recipes/OpenResty-Orthanc/logs/*
+cypress/videos/
@@ -1,3 +0,0 @@
-[submodule "testdata"]
-	path = testdata
-	url = https://github.com/OHIF/viewer-testdata-dicomweb.git
@@ -3,30 +3,79 @@
 # Set directory to location of this script
 # https://stackoverflow.com/a/3355423/1867984
 cd "$(dirname "$0")"
-cd .. # Up to project root

 # Helpful to verify which versions we're using
-echo 'My yarn version is... '
-
 yarn -v
 node -v

-# Build && Move PWA Output
-yarn run build:ci
-mkdir -p ./.netlify/www/pwa
-mv platform/app/dist/* .netlify/www/pwa -v
-echo 'Web application built and copied'
+# Install GitBook CLI
+echo 'Installing Gitbook CLI'
+yarn global add gitbook-cli
+npm install -g gitbook-cli

-# Build && Move Docusaurus Output (for the docs themselves)
-cd platform/docs
-yarn install
-yarn run build
-cd ../..
-mkdir -p ./.netlify/www/docs
-mv platform/docs/build/* .netlify/www/docs -v
-echo 'Docs built (docusaurus) and copied'
+echo 'Running Gitbook installation'
+# Generate all version's GitBook output
+# For each directory in /docs ...
+cd ./../docs/
+for D in *; do
+    if [ -d "${D}" ]; then
+
+			echo "Generating output for: ${D}"
+			cd "${D}"
+
+			# Clear previous output, generate new
+			rm -rf _book
+			node /opt/buildhome/.nvm/versions/node/v10.16.0/lib/node_modules/gitbook-cli/bin/gitbook.js install
+			node /opt/buildhome/.nvm/versions/node/v10.16.0/lib/node_modules/gitbook-cli/bin/gitbook.js build
+			cd ..
+
+		fi
+done
+
+# Move CNAME File into `latest`
+cp CNAME ./latest/_book/CNAME
+
+# Create a history folder in our latest version's output
+mkdir ./latest/_book/history
+
+# Move each version's files to latest's history folder
+for D in *; do
+  # If it's a directory
+	if [ -d "${D}" ]; then
+	  # If the directory name starts with `v` (v1, v2, etc.)
+		if [ "${D}" == v* ] ; then
+
+			echo "Moving ${D} to the latest version's history folder"
+
+			mkdir "./latest/_book/history/${D}"
+			cp -v -r "./${D}/_book"/* "./latest/_book/history/${D}"
+
+		fi
+	fi
+done
+cd ..
+
+# Build and copy the PWA Viewer into the demo directory
+mkdir ./docs/latest/_book/demo/
+
+# Install build deps and all monorepo package dependencies. Yarn Workspaces
+# should also symlink all projects appropriately
+yarn install --no-ignore-optional --pure-lockfile
+
+# Navigate to our Viewer project
+cd ./platform/viewer/
+
+# Create a Versions File
+# node -p -e '"export default "' + require(\"./../package.json\").version + '";"' > src/version.js
+yarn run version
+# Copy over wado-image-loader codecs and worker file
+cp ./../../node_modules/cornerstone-wado-image-loader/dist/*.min.js* public -v
+# Build using react-scripts
+# npx cross-env PUBLIC_URL=/demo REACT_APP_CONFIG=config/netlify.js react-scripts --max_old_space_size=4096 build
+# Build using WebPack
+# TODO: consume public/config correctly instead of hardcode
+npx webpack --config config/webpack.prod.js --mode production --env.production
+# Copy output to the folder that is our publish target
+npx cpx "dist/**/*" ./../../docs/latest/_book/demo --verbose

-# Cache all of the node_module dependencies in
-# extensions, modules, and platform packages
-yarn run lerna:cache
 echo 'Nothing left to see here. Go home, folks.'
@@ -1,5 +0,0 @@
-# Specific to our non-deploy-preview deploys
-# Confgure redirects using netlify.toml
-
-# PWA Redirect
-/* /index.html 200
@@ -1,15 +0,0 @@
-{
-  "name": "root",
-  "private": true,
-  "engines": {
-    "node": ">=14",
-    "npm": ">=6",
-    "yarn": ">=1.16.0"
-  },
-  "scripts": {
-    "deploy": "netlify deploy --prod --dir ./../platform/app/dist"
-  },
-  "devDependencies": {
-    "netlify-cli": "^2.21.0"
-  }
-}
@@ -0,0 +1,13 @@
+#!/bin/bash
+
+# Set directory to location of this script
+# https://stackoverflow.com/a/3355423/1867984
+cd "$(dirname "$0")"
+
+echo 'PUBLISHING'
+
+./node_modules/.bin/gh-pages \
+  --silent \
+  --repo https://$GITHUB_TOKEN@github.com/OHIF/Viewers.git \
+  --message 'Autogenerated Message: [ci skip]' \
+	--dist docs/latest/_book
@@ -1,10 +0,0 @@
-# Specific to our deploy-preview
-# Our docs are published using CircleCI + GitBook
-# Confgure redirects using netlify.toml
-
-# PWA Demo
-/pwa/* /pwa/index.html 200
-# UI Demo
-/ui/* /ui/index.html 200
-# UI Demo
-/docs/* /docs/index.html 200
@@ -1,23 +0,0 @@
-<html>
-
-<head>
-  <title>OHIF Viewer: Deploy Preview</title>
-</head>
-
-<body>
-  <h1>Index of Previews</h1>
-
-  <ul>
-    <li>
-      <a href="/pwa">OHIF Viewer</a>
-    </li>
-    <li>
-      <a href="/docs">Documentation</a>
-    </li>
-    <li>
-      <a href="/ui">UI: Component Library</a>
-    </li>
-  </ul>
-</body>
-
-</html>
@@ -1 +0,0 @@
-16.14.0
@@ -1 +0,0 @@
-*.md
@@ -1,9 +0,0 @@
-{
-  "trailingComma": "es5",
-  "printWidth": 80,
-  "proseWrap": "always",
-  "tabWidth": 2,
-  "semi": true,
-  "singleQuote": true,
-  "arrowParens": "avoid"
-}
@@ -1,14 +0,0 @@
-#!/bin/bash
-# https://github.com/shelljs/shelljs
-# https://github.com/shelljs/shelljs#exclude-options
-PROJECT=$1
-
-if [ -z "$PROJECT" ]
-then
-  # Default
-  npx lerna run dev:viewer
-else
-  eval "npx lerna run dev:$PROJECT"
-fi
-
-read -p 'Press [Enter] key to continue...'
@@ -1,12 +1,8 @@
 {
  "recommendations": [
    "esbenp.prettier-vscode",
+    "sysoev.language-stylus",
    "dbaeumer.vscode-eslint",
-    "mikestead.dotenv",
-    "bungcip.better-toml",
-    "silvenon.mdx",
-    "gruntfuggly.todo-tree",
-    "wayou.vscode-todo-highlight",
-    "bradlc.vscode-tailwindcss"
+    "mikestead.dotenv"
  ]
 }
@@ -1,28 +0,0 @@
-{
-  // Use IntelliSense to learn about possible attributes.
-  // Hover to view descriptions of existing attributes.
-  // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
-  "version": "0.2.0",
-  "configurations": [
-    {
-      "type": "pwa-chrome",
-      "request": "launch",
-      "name": "Launch Chrome against localhost",
-      "url": "http://localhost:3000",
-      "webRoot": "${workspaceFolder}"
-    }
-    // {
-    //   "name": "Debug Jest Tests",
-    //   "type": "node",
-    //   "request": "launch",
-    //   "runtimeArgs": [
-    //     "--inspect-brk",
-    //     "${workspaceRoot}/node_modules/.bin/jest",
-    //     "--runInBand"
-    //   ],
-    //   "console": "integratedTerminal",
-    //   "internalConsoleOptions": "neverOpen",
-    //   "port": 9229
-    // }
-  ]
-}
@@ -1,8 +1,10 @@
 {
  "editor.rulers": [80, 120],
+
  // ===
  // Spacing
  // ===
+
  "editor.insertSpaces": true,
  "editor.tabSize": 2,
  "editor.trimAutoWhitespace": true,
@@ -10,27 +12,19 @@
  "files.eol": "\n",
  "files.insertFinalNewline": true,
  "files.trimFinalNewlines": true,
+
  // ===
  // Event Triggers
  // ===
+
  "editor.formatOnSave": true,
  "eslint.autoFixOnSave": true,
  "eslint.run": "onSave",
  "eslint.validate": [
-    {
-      "language": "javascript",
-      "autoFix": true
-    },
-    {
-      "language": "javascriptreact",
-      "autoFix": true
-    }
+    { "language": "javascript", "autoFix": true },
+    { "language": "javascriptreact", "autoFix": true }
  ],
-  "jest.autoRun": "off",
-  "prettier.disableLanguages": ["html"],
+  "prettier.disableLanguages": [],
  "prettier.endOfLine": "lf",
-  "workbench.colorCustomizations": {},
-  "editor.codeActionsOnSave": {
-    "source.fixAll.eslint": true
-  }
+  "workbench.colorCustomizations": {}
 }
@@ -1,22 +0,0 @@
-const path = require('path');
-
-function excludeNodeModulesExcept(modules) {
-  var pathSep = path.sep;
-  if (pathSep == '\\')
-    // must be quoted for use in a regexp:
-    pathSep = '\\\\';
-  var moduleRegExps = modules.map(function(modName) {
-    return new RegExp('node_modules' + pathSep + modName);
-  });
-
-  return function(modulePath) {
-    if (/node_modules/.test(modulePath)) {
-      for (var i = 0; i < moduleRegExps.length; i++)
-        if (moduleRegExps[i].test(modulePath)) return false;
-      return true;
-    }
-    return false;
-  };
-}
-
-module.exports = excludeNodeModulesExcept;
@@ -1,31 +0,0 @@
-const autoprefixer = require('autoprefixer');
-const path = require('path');
-const tailwindcss = require('tailwindcss');
-const tailwindConfigPath = path.resolve(
-  '../../platform/app/tailwind.config.js'
-);
-const MiniCssExtractPlugin = require('mini-css-extract-plugin');
-const devMode = process.env.NODE_ENV !== 'production';
-
-const cssToJavaScript = {
-  test: /\.css$/,
-  use: [
-    //'style-loader',
-    devMode ? 'style-loader' : MiniCssExtractPlugin.loader,
-    { loader: 'css-loader', options: { importLoaders: 1 } },
-    {
-      loader: 'postcss-loader',
-      options: {
-        postcssOptions: {
-          verbose: true,
-          plugins: [
-            [tailwindcss(tailwindConfigPath)],
-            [autoprefixer('last 2 version', 'ie >= 11')],
-          ],
-        },
-      },
-    },
-  ],
-};
-
-module.exports = cssToJavaScript;
@@ -1,10 +0,0 @@
-/**
- * This is exclusively used by `vtk.js` to bundle glsl files.
- */
-const loadShaders = {
-  test: /\.glsl$/i,
-  include: /vtk\.js[\/\\]Sources/,
-  loader: 'shader-loader',
-};
-
-module.exports = loadShaders;
@@ -1,17 +0,0 @@
-/**
- * This allows us to include web workers in our bundle, and VTK.js
- * web workers in our bundle. While this increases bundle size, it
- * cuts down on the number of includes we need for `script tag` usage.
- */
-const loadWebWorkers = {
-  test: /\.worker\.js$/,
-  include: /vtk\.js[\/\\]Sources/,
-  use: [
-    {
-      loader: 'worker-loader',
-      options: { inline: true, fallback: false },
-    },
-  ],
-};
-
-module.exports = loadWebWorkers;
@@ -1,41 +0,0 @@
-const excludeNodeModulesExcept = require('./../helpers/excludeNodeModulesExcept.js');
-
-function transpileJavaScript(mode) {
-  const exclude =
-    mode === 'production'
-      ? excludeNodeModulesExcept([
-          // 'dicomweb-client',
-          // https://github.com/react-dnd/react-dnd/blob/master/babel.config.js
-          'react-dnd',
-          // https://github.com/dcmjs-org/dcmjs/blob/master/.babelrc
-          // https://github.com/react-dnd/react-dnd/issues/1342
-          // 'dcmjs', // contains: loglevelnext
-          // https://github.com/shellscape/loglevelnext#browser-support
-          // 'loglevelnext',
-          // https://github.com/dcmjs-org/dicom-microscopy-viewer/issues/35
-          // 'dicom-microscopy-viewer',
-          // https://github.com/openlayers/openlayers#supported-browsers
-          // 'ol', --> Should be fine
-        ])
-      : excludeNodeModulesExcept([]);
-
-  return {
-    // Include mjs, ts, tsx, js, and jsx files.
-    test: /\.(mjs|ts|js)x?$/,
-    // These are packages that are not transpiled to our lowest supported
-    // JS version (currently ES5). Most of these leverage ES6+ features,
-    // that we need to transpile to a different syntax.
-    exclude: [/(codecs)/, /(dicomicc)/, exclude],
-    loader: 'babel-loader',
-    options: {
-      // Find babel.config.js in monorepo root
-      // https://babeljs.io/docs/en/options#rootmode
-      rootMode: 'upward',
-      envName: mode,
-      cacheCompression: false,
-      cacheDirectory: true,
-    },
-  };
-}
-
-module.exports = transpileJavaScript;
@@ -1,173 +0,0 @@
-// ~~ ENV
-const dotenv = require('dotenv');
-//
-const path = require('path');
-const fs = require('fs');
-
-const webpack = require('webpack');
-
-// ~~ PLUGINS
-const BundleAnalyzerPlugin = require('webpack-bundle-analyzer')
-  .BundleAnalyzerPlugin;
-const TerserJSPlugin = require('terser-webpack-plugin');
-
-// ~~ PackageJSON
-// const vtkRules = require('vtk.js/Utilities/config/dependency.js').webpack.core
-//   .rules;
-// ~~ RULES
-const loadShadersRule = require('./rules/loadShaders.js');
-const loadWebWorkersRule = require('./rules/loadWebWorkers.js');
-const transpileJavaScriptRule = require('./rules/transpileJavaScript.js');
-const cssToJavaScript = require('./rules/cssToJavaScript.js');
-
-// ~~ ENV VARS
-const NODE_ENV = process.env.NODE_ENV;
-const QUICK_BUILD = process.env.QUICK_BUILD;
-const BUILD_NUM = process.env.CIRCLE_BUILD_NUM || '0';
-
-// read from ../version.txt
-const VERSION_NUMBER =
-  fs.readFileSync(path.join(__dirname, '../version.txt'), 'utf8') || '';
-
-const COMMIT_HASH =
-  fs.readFileSync(path.join(__dirname, '../commit.txt'), 'utf8') || '';
-
-//
-dotenv.config();
-
-module.exports = (env, argv, { SRC_DIR, ENTRY }) => {
-  if (!process.env.NODE_ENV) {
-    throw new Error('process.env.NODE_ENV not set');
-  }
-
-  const mode = NODE_ENV === 'production' ? 'production' : 'development';
-  const isProdBuild = NODE_ENV === 'production';
-  const isQuickBuild = QUICK_BUILD === 'true';
-
-  const config = {
-    mode: isProdBuild ? 'production' : 'development',
-    devtool: isProdBuild ? 'source-map' : 'cheap-module-source-map',
-    entry: ENTRY,
-    optimization: {
-      // splitChunks: {
-      //   // include all types of chunks
-      //   chunks: 'all',
-      // },
-      //runtimeChunk: 'single',
-      minimize: isProdBuild,
-      sideEffects: false,
-    },
-    output: {
-      // clean: true,
-      publicPath: '/',
-    },
-    context: SRC_DIR,
-    stats: {
-      colors: true,
-      hash: true,
-      timings: true,
-      assets: true,
-      chunks: false,
-      chunkModules: false,
-      modules: false,
-      children: false,
-      warnings: true,
-    },
-    cache: {
-      type: 'filesystem',
-    },
-    module: {
-      noParse: [/(codec)/, /(dicomicc)/],
-      rules: [
-        transpileJavaScriptRule(mode),
-        loadWebWorkersRule,
-        // loadShadersRule,
-        {
-          test: /\.m?js/,
-          resolve: {
-            fullySpecified: false,
-          },
-        },
-        cssToJavaScript,
-        {
-          test: /\.wasm/,
-          type: 'asset/resource',
-        },
-      ], //.concat(vtkRules),
-    },
-    resolve: {
-      mainFields: ['module', 'browser', 'main'],
-      alias: {
-        // Viewer project
-        '@': path.resolve(__dirname, '../platform/app/src'),
-        '@components': path.resolve(
-          __dirname,
-          '../platform/app/src/components'
-        ),
-        '@hooks': path.resolve(__dirname, '../platform/app/src/hooks'),
-        '@routes': path.resolve(__dirname, '../platform/app/src/routes'),
-        '@state': path.resolve(__dirname, '../platform/app/src/state'),
-        'dicom-microscopy-viewer':
-          'dicom-microscopy-viewer/dist/dynamic-import/dicomMicroscopyViewer.min.js',
-        '@cornerstonejs/dicom-image-loader':
-          '@cornerstonejs/dicom-image-loader/dist/dynamic-import/cornerstoneDICOMImageLoader.min.js',
-      },
-      // Which directories to search when resolving modules
-      modules: [
-        // Modules specific to this package
-        path.resolve(__dirname, '../node_modules'),
-        // Hoisted Yarn Workspace Modules
-        path.resolve(__dirname, '../../../node_modules'),
-        path.resolve(__dirname, '../platform/app/node_modules'),
-        path.resolve(__dirname, '../platform/ui/node_modules'),
-        SRC_DIR,
-      ],
-      // Attempt to resolve these extensions in order.
-      extensions: ['.js', '.jsx', '.json', '.ts', '.tsx', '*'],
-      // symlinked resources are resolved to their real path, not their symlinked location
-      symlinks: true,
-      fallback: { fs: false, path: false, zlib: false },
-    },
-    plugins: [
-      new webpack.DefinePlugin({
-        /* Application */
-        'process.env.NODE_ENV': JSON.stringify(process.env.NODE_ENV),
-        'process.env.DEBUG': JSON.stringify(process.env.DEBUG),
-        'process.env.APP_CONFIG': JSON.stringify(process.env.APP_CONFIG || ''),
-        'process.env.PUBLIC_URL': JSON.stringify(process.env.PUBLIC_URL || '/'),
-        'process.env.BUILD_NUM': JSON.stringify(BUILD_NUM),
-        'process.env.VERSION_NUMBER': JSON.stringify(VERSION_NUMBER),
-        'process.env.COMMIT_HASH': JSON.stringify(COMMIT_HASH),
-        /* i18n */
-        'process.env.USE_LOCIZE': JSON.stringify(process.env.USE_LOCIZE || ''),
-        'process.env.LOCIZE_PROJECTID': JSON.stringify(
-          process.env.LOCIZE_PROJECTID || ''
-        ),
-        'process.env.LOCIZE_API_KEY': JSON.stringify(
-          process.env.LOCIZE_API_KEY || ''
-        ),
-        'process.env.REACT_APP_I18N_DEBUG': JSON.stringify(
-          process.env.REACT_APP_I18N_DEBUG || ''
-        ),
-      }),
-      // Uncomment to generate bundle analyzer
-      // new BundleAnalyzerPlugin(),
-    ],
-  };
-
-  if (isProdBuild) {
-    config.optimization.minimizer = [
-      new TerserJSPlugin({
-        parallel: true,
-        terserOptions: {},
-      }),
-    ];
-  }
-
-  if (isQuickBuild) {
-    config.optimization.minimize = false;
-    config.devtool = false;
-  }
-
-  return config;
-};
@@ -0,0 +1,90 @@
+const path = require("path");
+const ExtractCssChunks = require("extract-css-chunks-webpack-plugin");
+
+const SRC_DIR = path.join(__dirname, "../src");
+const PUBLIC_DIR = path.join(__dirname, "../public");
+const DIST_DIR = path.join(__dirname, "../dist");
+
+module.exports = (env, argv, { SRC_DIR, DIST_DIR }) => {
+  return {
+    entry: {
+      app: `${SRC_DIR}/index.js`
+    },
+    context: SRC_DIR,
+    module: {
+      rules: [
+        {
+          test: /\.jsx?$/,
+          exclude: [/node_modules/, /packages\\extension/],
+          loader: "babel-loader",
+          options: {
+            // Find babel.config.js in monorepo root
+            // https://babeljs.io/docs/en/options#rootmode
+            rootMode: "upward",
+            presets: [
+              [
+                "@babel/preset-env",
+                {
+                  // Do not transform ES6 modules to another format.
+                  // Webpack will take care of that.
+                  modules: false
+                }
+              ]
+            ]
+          }
+        },
+        {
+          test: /\.css$/,
+          use: [
+            "style-loader",
+            ExtractCssChunks.loader,
+            { loader: "css-loader", options: { importLoaders: 1 } },
+            {
+              loader: "postcss-loader",
+              options: {
+                config: {
+                  path: "./postcss.config.js"
+                }
+              }
+            }
+          ]
+        },
+        /**
+         * This allows us to include web workers in our bundle, and VTK.js
+         * web workers in our bundle. While this increases bundle size, it
+         * cuts down on the number of includes we need for `script tag` usage.
+         */
+        {
+          test: /\.worker\.js$/,
+          include: /vtk\.js[\/\\]Sources/,
+          use: [
+            {
+              loader: "worker-loader",
+              options: { inline: true, fallback: false }
+            }
+          ]
+        },
+        /**
+         * This is exclusively used by `vtk.js` to bundle glsl files.
+         */
+        {
+          test: /\.glsl$/i,
+          include: /vtk\.js[\/\\]Sources/,
+          loader: "shader-loader"
+        }
+      ]
+    },
+    resolve: {
+      // Which directories to search when resolving modules
+      modules: [
+        path.resolve(__dirname, "../node_modules"),
+        path.resolve(__dirname, "../../../node_modules"),
+        SRC_DIR
+      ],
+      // Attempt to resolve these extensions in order.
+      extensions: [".js", ".jsx", ".json", "*"],
+      // symlinked resources are resolved to their real path, not their symlinked location
+      symlinks: true
+    }
+  };
+};
@@ -1,76 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, sex characteristics, gender identity and expression,
-level of experience, education, socio-economic status, nationality, personal
-appearance, race, religion, or sexual identity and orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment
-include:
-
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
-
-Examples of unacceptable behavior by participants include:
-
-* The use of sexualized language or imagery and unwelcome sexual attention or
- advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic
- address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
- professional setting
-
-## Our Responsibilities
-
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
-
-Project maintainers have the right and responsibility to remove, edit, or
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at danny.ri.brown+OHIFcoc@gmail.com. All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
-
-[homepage]: https://www.contributor-covenant.org
-
-For answers to common questions about this code of conduct, see
-https://www.contributor-covenant.org/faq
@@ -1 +0,0 @@
-See our contributing guidelines at [`https://docs.ohif.org`](https://docs.ohif.org/development/contributing.html)
@@ -1,149 +0,0 @@
-# OHIF public demo data sets
-
-The OHIF Viewer's public demo page, available at https://viewer.ohif.org/, uses publicly anonymized demo datasets.
-These datasets were mostly obtained from the [NIH NCI Imaging Data Commons](https://datacommons.cancer.gov/repository/imaging-data-commons)
-and [NIH NCI TCIA](https://www.cancerimagingarchive.net/). Before listing the datasets,
-we would like to extend a special thank you to all groups who have made their datasets publicly available.
-Without them, we would not have been able to create this demo page.
-
-Please find below the list of datasets used on the demo page, along with their respective citations.
-
-
-## Platforms
-### NIH NCI IDC
-
- Fedorov, A., Longabaugh, W.J., Pot, D., Clunie, D.A., Pieper, S., Aerts, H.J., Homeyer, A., Lewis, R., Akbarzadeh, A., Bontempi, D. and Clifford, W., 2021. NCI imaging data commons. Cancer research, 81(16), p.4188.
-
-### NIH NCI TCIA
-
- Clark, K., Vendt, B., Smith, K., Freymann, J., Kirby, J., Koppel, P., Moore, S., Phillips, S., Maffitt, D., Pringle, M., Tarbox, L., & Prior, F. (2013). The Cancer Imaging Archive (TCIA): Maintaining and Operating a Public Information Repository. Journal of Digital Imaging, 26(6), 1045–1057. https://doi.org/10.1007/s10278-013-9622-7
-
-
-
-
-## Datasets
-Below you can find the StudyInstanceUID of the studies that are used in the demo page along with their citations.
-
-### 1.3.6.1.4.1.14519.5.2.1.267424821384663813780850856506829388886
-
-Segmentation of Vestibular Schwannoma from Magnetic Resonance Imaging: An Open Annotated Dataset and Baseline Algorithm (Vestibular-Schwannoma-SEG)
-
- Shapey, J., Kujawa, A., Dorent, R., Wang, G., Bisdas, S., Dimitriadis, A., Grishchuck, D., Paddick, I., Kitchen, N., Bradford, R., Saeed, S., Ourselin, S., & Vercauteren, T. (2021). Segmentation of Vestibular Schwannoma from Magnetic Resonance Imaging: An Open Annotated Dataset and Baseline Algorithm [Data set]. The Cancer Imaging Archive. https://doi.org/10.7937/TCIA.9YTJ-5Q73
-
- Shapey, J., Kujawa, A., Dorent, R., Wang, G., Dimitriadis, A., Grishchuk, D., Paddick, I., Kitchen, N., Bradford, R., Saeed, S. R., Bisdas, S., Ourselin, S., & Vercauteren, T. (2021). Segmentation of vestibular schwannoma from MRI, an open annotated dataset and baseline algorithm. In Scientific Data (Vol. 8, Issue 1). Springer Science and Business Media LLC. https://doi.org/10.1038/s41597-021-01064-w
-
-
-### 1.3.6.1.4.1.14519.5.2.1.7009.2403.334240657131972136850343327463
-### 1.3.6.1.4.1.14519.5.2.1.7009.2403.871108593056125491804754960339
-
-
-ACRIN-NSCLC-FDG-PET (ACRIN 6668)
-
- Kinahan, P., Muzi, M., Bialecki, B., Herman, B., & Coombs, L. (2019). Data from the ACRIN 6668 Trial NSCLC-FDG-PET (Version 2) [Data set]. The Cancer Imaging Archive. https://doi.org/10.7937/tcia.2019.30ilqfcl
-
- Machtay, M., Duan, F., Siegel, B. A., Snyder, B. S., Gorelick, J. J., Reddin, J. S., Munden, R., Johnson, D. W., Wilf, L. H., DeNittis, A., Sherwin, N., Cho, K. H., Kim, S., Videtic, G., Neumann, D. R., Komaki, R., Macapinlac, H., Bradley, J. D., & Alavi, A. (2013). Prediction of Survival by [18F]Fluorodeoxyglucose Positron Emission Tomography in Patients With Locally Advanced Non–Small-Cell Lung Cancer Undergoing Definitive Chemoradiation Therapy: Results of the ACRIN 6668/RTOG 0235 Trial. In Journal of Clinical Oncology (Vol. 31, Issue 30, pp. 3823–3830). American Society of Clinical Oncology (ASCO). https://doi.org/10.1200/jco.2012.47.5947
-
-
-### 2.25.103659964951665749659160840573802789777
-
-The Cancer Genome Atlas Glioblastoma Multiforme Collection (TCGA-GBM)
-
- Scarpace, L., Mikkelsen, T., Cha, S., Rao, S., Tekchandani, S., Gutman, D., Saltz, J. H., Erickson, B. J., Pedano, N., Flanders, A. E., Barnholtz-Sloan, J., Ostrom, Q., Barboriak, D., & Pierce, L. J. (2016). The Cancer Genome Atlas Glioblastoma Multiforme Collection (TCGA-GBM) (Version 4) [Data set]. The Cancer Imaging Archive. https://doi.org/10.7937/K9/TCIA.2016.RNYFUYE9
-
-
-### 1.3.6.1.4.1.14519.5.2.1.256467663913010332776401703474716742458
-
-Abdominal or pelvic enhanced CT images within 10 days before surgery of 230 patients with stage II colorectal cancer (StageII-Colorectal-CT)
-
-
- Tong T., Li M. (2022) Abdominal or pelvic enhanced CT images within 10 days before surgery of 230 patients with stage II colorectal cancer (StageII-Colorectal-CT) [Dataset]. The Cancer Imaging Archive. DOI: https://doi.org/10.7937/p5k5-tg43
-
- Li, M., Gong, J., Bao, Y., Huang, D., Peng, J., & Tong, T. (2022). Special issue “The advance of solid tumor research in China”: Prognosis prediction for stage II colorectal cancer by fusing computed tomography radiomics and deep‐learning features of primary lesions and peripheral lymph nodes. In International Journal of Cancer. Wiley. https://doi.org/10.1002/ijc.34053
-
-
-### 1.3.6.1.4.1.14519.5.2.1.3023.4024.215308722288168917637555384485
-
-The Cancer Genome Atlas Sarcoma Collection (TCGA-SARC)
-
- Roche, C., Bonaccio, E., & Filippini, J. (2016). The Cancer Genome Atlas Sarcoma Collection (TCGA-SARC) (Version 3) [Data set]. The Cancer Imaging Archive. https://doi.org/10.7937/K9/TCIA.2016.CX6YLSUX
-
-
-
-### 1.3.6.1.4.1.14519.5.2.1.4792.2001.105216574054253895819671475627
-
-BREAST-DIAGNOSIS
-
-
- Bloch, B. Nicolas, Jain, Ashali, & Jaffe, C. Carl. (2015). BREAST-DIAGNOSIS [Data set]. The Cancer Imaging Archive. http://doi.org/10.7937/K9/TCIA.2015.SDNRQXXR
-
-
-
-
-### 1.3.6.1.4.1.14519.5.2.1.1706.8374.643249677828306008300337414785
-
-Multimodality annotated HCC cases with and without advanced imaging segmentation (HCC-TACE-Seg)
-
-
- Moawad, A. W., Fuentes, D., Morshid, A., Khalaf, A. M., Elmohr, M. M., Abusaif, A., Hazle, J. D., Kaseb, A. O., Hassan, M., Mahvash, A., Szklaruk, J., Qayyom, A., & Elsayes, K. (2021). Multimodality annotated HCC cases with and without advanced imaging segmentation [Data set]. The Cancer Imaging Archive. https://doi.org/10.7937/TCIA.5FNA-0924
-
- Morshid, A., Elsayes, K. M., Khalaf, A. M., Elmohr, M. M., Yu, J., Kaseb, A. O., Hassan, M., Mahvash, A., Wang, Z., Hazle, J. D., & Fuentes, D. (2019). A Machine Learning Model to Predict Hepatocellular Carcinoma Response to Transcatheter Arterial Chemoembolization. Radiology: Artificial Intelligence, 1(5), e180021. https://doi.org/10.1148/ryai.2019180021
-
-
-
-### 1.3.6.1.4.1.14519.5.2.1.1188.2803.137585363493444318569098508293
-
-Ultrasound data of a variety of liver masses (B-mode-and-CEUS-Liver)
-
- Eisenbrey, J., Lyshchik, A., & Wessner, C. (2021). Ultrasound data of a variety of liver masses [Data set]. The Cancer Imaging Archive.  DOI: https://doi.org/10.7937/TCIA.2021.v4z7-tc39
-
-
-
-### 1.3.6.1.4.1.32722.99.99.62087908186665265759322018723889952421
-
-NSCLC-Radiomics
-
- Aerts, H. J. W. L., Wee, L., Rios Velazquez, E., Leijenaar, R. T. H., Parmar, C., Grossmann, P., Carvalho, S., Bussink, J., Monshouwer, R., Haibe-Kains, B., Rietveld, D., Hoebers, F., Rietbergen, M. M., Leemans, C. R., Dekker, A., Quackenbush, J., Gillies, R. J., Lambin, P. (2019). Data From NSCLC-Radiomics (version 4) [Data set]. The Cancer Imaging Archive. https://doi.org/10.7937/K9/TCIA.2015.PF0M9REI
-
-
- Aerts, H. J. W. L., Velazquez, E. R., Leijenaar, R. T. H., Parmar, C., Grossmann, P., Carvalho, S., Bussink, J., Monshouwer, R., Haibe-Kains, B., Rietveld, D., Hoebers, F., Rietbergen, M. M., Leemans, C. R., Dekker, A., Quackenbush, J., Gillies, R. J., Lambin, P. (2014, June 3). Decoding tumour phenotype by noninvasive imaging using a quantitative radiomics approach. Nature Communications. Nature Publishing Group. https://doi.org/10.1038/ncomms5006  (link)
-
-
-### 1.3.6.1.4.1.14519.5.2.1.3671.4754.298665348758363466150039312520
-
-QIN-PROSTATE-Repeatability
-
- Fedorov, A; Schwier, M; Clunie, D; Herz, C; Pieper, S; Kikinis, R; Tempany, C; Fennessy, F. (2018). Data From QIN-PROSTATE-Repeatability. The Cancer Imaging Archive. DOI: 10.7937/K9/TCIA.2018.MR1CKGND
-
-
- Fedorov A, Vangel MG, Tempany CM, Fennessy FM. Multiparametric Magnetic Resonance Imaging of the Prostate: Repeatability of Volume and Apparent Diffusion Coefficient Quantification. Investigative Radiology. 52, 538–546 (2017). DOI: 10.1097/RLI.0000000000000382
-
- Fedorov, A., Schwier, M., Clunie, D., Herz, C., Pieper, S., Kikinis,R., Tempany, C. & Fennessy, F. An annotated test-retest collection of prostate multiparametric MRI. Scientific Data 5, 180281 (2018). DOI:
-
-### 2.25.141277760791347900862109212450152067508
-
-The Clinical Proteomic Tumor Analysis Consortium Clear Cell Renal Cell Carcinoma Collection (CPTAC-CCRCC)
-
- National Cancer Institute Clinical Proteomic Tumor Analysis Consortium (CPTAC). (2018). The Clinical Proteomic Tumor Analysis Consortium Clear Cell Renal Cell Carcinoma Collection (CPTAC-CCRCC) (Version 10) [Data set]. The Cancer Imaging Archive. https://doi.org/10.7937/K9/TCIA.2018.OBLAMN27
-
- The CPTAC program requests that publications using data from this program include the following statement: “Data used in this publication were generated by the National Cancer Institute Clinical Proteomic Tumor Analysis Consortium (CPTAC).”
-
-
-### 2.25.275741864483510678566144889372061815320
-
-National Lung Screening Trial
-
-  National Lung Screening Trial Research Team. (2013). Data from the National Lung Screening Trial (NLST) [Data set]. The Cancer Imaging Archive. https://doi.org/10.7937/TCIA.HMQ8-J677
-
- National Lung Screening Trial Research Team*; Aberle DR, Adams AM, Berg CD, Black WC, Clapp JD, Fagerstrom RM, Gareen IF, Gatsonis C, Marcus PM, Sicks JD (2011). Reduced Lung-Cancer Mortality with Low-Dose Computed Tomographic Screening. New England Journal of Medicine, 365(5), 395–409. https://doi.org/10.1056/nejmoa1102873
-
-
-### 1.3.6.1.4.1.14519.5.2.1.99.1071.26968527900428638961173806140069
-
-Stony Brook University COVID-19 Positive Cases (COVID-19-NY-SBU)
-
- Saltz, J., Saltz, M., Prasanna, P., Moffitt, R., Hajagos, J., Bremer, E., Balsamo, J., & Kurc, T. (2021). Stony Brook University COVID-19 Positive Cases [Data set]. The Cancer Imaging Archive. https://doi.org/10.7937/TCIA.BBAG-2923
-
-
-### 2.16.840.1.114362.1.11972228.22789312658.616067305.306.2
-
-https://data.kitware.com/
@@ -1,73 +0,0 @@
-# This dockerfile is used to publish the `ohif/app` image on dockerhub.
-#
-# It's a good example of how to build our static application and package it
-# with a web server capable of hosting it as static content.
-#
-# docker build
-# --------------
-# If you would like to use this dockerfile to build and tag an image, make sure
-# you set the context to the project's root directory:
-# https://docs.docker.com/engine/reference/commandline/build/
-#
-#
-# SUMMARY
-# --------------
-# This dockerfile has two stages:
-#
-# 1. Building the React application for production
-# 2. Setting up our Nginx (Alpine Linux) image w/ step one's output
-#
-
-
-# Stage 1: Build the application
-# docker build -t ohif/viewer:latest .
-FROM node:16.15.0-slim as json-copier
-
-RUN mkdir /usr/src/app
-WORKDIR /usr/src/app
-
-COPY ["package.json", "yarn.lock", "preinstall.js", "./"]
-COPY extensions /usr/src/app/extensions
-COPY modes /usr/src/app/modes
-COPY platform /usr/src/app/platform
-
-# Find and remove non-package.json files
-#RUN find extensions \! -name "package.json" -mindepth 2 -maxdepth 2 -print | xargs rm -rf
-#RUN find modes \! -name "package.json" -mindepth 2 -maxdepth 2 -print | xargs rm -rf
-#RUN find platform \! -name "package.json" -mindepth 2 -maxdepth 2 -print | xargs rm -rf
-
-# Copy Files
-FROM node:16.15.0-slim as builder
-RUN mkdir /usr/src/app
-WORKDIR /usr/src/app
-
-COPY --from=json-copier /usr/src/app .
-
-# Run the install before copying the rest of the files
-RUN yarn config set workspaces-experimental true
-RUN yarn install --frozen-lockfile --verbose
-
-COPY . .
-
-# To restore workspaces symlinks
-RUN yarn install --frozen-lockfile --verbose
-
-ENV PATH /usr/src/app/node_modules/.bin:$PATH
-ENV QUICK_BUILD true
-# ENV GENERATE_SOURCEMAP=false
-# ENV REACT_APP_CONFIG=config/default.js
-
-RUN yarn run build
-
-# Stage 3: Bundle the built application into a Docker container
-# which runs Nginx using Alpine Linux
-FROM nginxinc/nginx-unprivileged:1.23.1-alpine as final
-#RUN apk add --no-cache bash
-ENV PORT=80
-RUN rm /etc/nginx/conf.d/default.conf
-USER nginx
-COPY --chown=nginx:nginx .docker/Viewer-v3.x /usr/src
-RUN chmod 777 /usr/src/entrypoint.sh
-COPY --from=builder /usr/src/app/platform/app/dist /usr/share/nginx/html
-ENTRYPOINT ["/usr/src/entrypoint.sh"]
-CMD ["nginx", "-g", "daemon off;"]
@@ -1,139 +1,73 @@
-<!-- prettier-ignore-start -->
-<!-- markdownlint-disable -->
-<div align="center">
-  <h1>OHIF Medical Imaging Viewer</h1>
-  <p><strong>The OHIF Viewer</strong> is a zero-footprint medical image viewer
-provided by the <a href="https://ohif.org/">Open Health Imaging Foundation (OHIF)</a>. It is a configurable and extensible progressive web application with out-of-the-box support for image archives which support <a href="https://www.dicomstandard.org/dicomweb/">DICOMweb</a>.</p>
-</div>
+# OHIF Medical Imaging Platform

+[![lerna][lerna-image]][lerna-url]
+[![Netlify Status][netlify-image]][netlify-url]

-<div align="center">
-  <a href="https://docs.ohif.org/"><strong>Read The Docs</strong></a>
-</div>
-<div align="center">
-  <a href="https://viewer.ohif.org/">Live Demo</a> |
-  <a href="https://ui.ohif.org/">Component Library</a>
-</div>
-<div align="center">
-  📰 <a href="https://ohif.org/news/"><strong>Join OHIF Newsletter</strong></a> 📰
-</div>
+## The Problem

-
-<hr />
-
-[![NPM version][npm-version-image]][npm-url]
-[![MIT License][license-image]][license-url]
-[![This project is using Percy.io for visual regression testing.][percy-image]](percy-url)
-<!-- [![NPM downloads][npm-downloads-image]][npm-url] -->
-<!-- [![Pulls][docker-pulls-img]][docker-image-url] -->
-<!-- [![FOSSA Status](https://app.fossa.io/api/projects/git%2Bgithub.com%2FOHIF%2FViewers.svg?type=shield)](https://app.fossa.io/projects/git%2Bgithub.com%2FOHIF%2FViewers?ref=badge_shield) -->
-
-<!-- [![Netlify Status][netlify-image]][netlify-url] -->
-<!-- [![CircleCI][circleci-image]][circleci-url] -->
-<!-- [![codecov][codecov-image]][codecov-url] -->
-<!-- [![All Contributors](https://img.shields.io/badge/all_contributors-10-orange.svg?style=flat-square)](#contributors) -->
-<!-- prettier-ignore-end -->
-
-
-|     |  | |
-| :-: | :---  | :--- |
-| <img src="platform/docs/docs/assets/img/demo-measurements.jpg" alt="Measurement tracking" width="350"/> | Measurement Tracking | [Demo](https://viewer.ohif.org/viewer?StudyInstanceUIDs=1.3.6.1.4.1.25403.345050719074.3824.20170125095438.5) |
-| <img src="platform/docs/docs/assets/img/demo-segmentation.png" alt="Segmentations" width="350"/> | Labelmap Segmentations  | [Demo](https://viewer.ohif.org/viewer?StudyInstanceUIDs=1.3.12.2.1107.5.2.32.35162.30000015050317233592200000046) |
-| <img src="platform/docs/docs/assets/img/demo-ptct.png" alt="Hanging Protocols" width="350"/> | Fusion and Custom Hanging protocols  | [Demo](https://viewer.ohif.org/tmtv?StudyInstanceUIDs=1.3.6.1.4.1.14519.5.2.1.7009.2403.334240657131972136850343327463) |
-| <img src="platform/docs/docs/assets/img/demo-microscopy.png" alt="Microscopy" width="350"/> | Slide Microscopy  | [Demo](https://viewer.ohif.org/microscopy?StudyInstanceUIDs=2.25.275741864483510678566144889372061815320) |
-| <img src="platform/docs/docs/assets/img/demo-volumeRendering.png" alt="Volume Rendering" width="350"/> | Volume Rendering  | [Demo](https://viewer.ohif.org/viewer?StudyInstanceUIDs=1.3.6.1.4.1.25403.345050719074.3824.20170125095438.5&hangingprotocolId=mprAnd3DVolumeViewport) |
-
-
-
-## About
-
-The OHIF Medical Imaging Viewer is for viewing medical images. It can retrieve
-and load images from most sources and formats; render sets in 2D, 3D, and
-reconstructed representations; allows for the manipulation, annotation, and
-serialization of observations; supports internationalization, OpenID Connect,
-offline use, hotkeys, and many more features.
-
-Almost everything offers some degree of customization and configuration. If it
-doesn't support something you need, we accept pull requests and have an ever
-improving Extension System.
+...

 ## Why Choose Us

-### Community & Experience
+...

-The OHIF Viewer is a collaborative effort that has served as the basis for many
-active, production, and FDA Cleared medical imaging viewers. It benefits from
-our extensive community's collective experience, and from the sponsored
-contributions of individuals, research groups, and commercial organizations.
+## Quick Start

-### Built to Adapt
+...

-After more than 8-years of integrating with many companies and organizations,
-The OHIF Viewer has been rebuilt from the ground up to better address the
-varying workflow and configuration needs of its many users. All of the Viewer's
-core features are built using it's own extension system. The same extensibility
-that allows us to offer:
+## Commands

- 2D and 3D medical image viewing
- Multiplanar Reconstruction (MPR)
- Maximum Intensity Project (MIP)
- Whole slide microscopy viewing
- PDF and Dicom Structured Report rendering
- Segmentation rendering as labelmaps and contours
- User Access Control (UAC)
- Context specific toolbar and side panel content
- and many others
+### Global

-Can be leveraged by you to customize the viewer for your workflow, and to add
-any new functionality you may need (and wish to maintain privately without
-forking).
+| Commands        |     |                                                       |
+| --------------- | --- | ----------------------------------------------------- |
+| `build:package` |     | Builds commonjs bundles for all projects              |
+| `test:unit`     |     | Jest multi-project test runner; overall coverage      |
+| `test:unit:ci`  |     | Runs tests in parallel. Reports coverage per project. |

-### Support
-
- [Report a Bug 🐛](https://github.com/OHIF/Viewers/issues/new?assignees=&labels=Community%3A+Report+%3Abug%3A%2CAwaiting+Reproduction&projects=&template=bug-report.yml&title=%5BBug%5D+)
- [Request a Feature 🚀](https://github.com/OHIF/Viewers/issues/new?assignees=&labels=Community%3A+Request+%3Ahand%3A&projects=&template=feature-request.yml&title=%5BFeature+Request%5D+)
- [Ask a Question 🤗](community.ohif.org)
- [Slack Channel](https://join.slack.com/t/cornerstonejs/shared_invite/zt-1r8xb2zau-dOxlD6jit3TN0Uwf928w9Q)
-
-For commercial support, academic collaborations, and answers to common
-questions; please use [Get Support](https://ohif.org/get-support/) to contact
-us.
+### Local

+| Commands       |     |                                                   |
+| -------------- | --- | ------------------------------------------------- |
+| `test:unit`    |     | Runs tests while watching for changes             |
+| `test:unit:ci` |     | Runs tests, collects coverage, reports to codecov |

 ## Developing

-### Branches
-
-#### `master` branch - The latest dev (beta) release
-
- `master` - The latest dev release
-
-This is typically where the latest development happens. Code that is in the master branch has passed code reviews and automated tests, but it may not be deemed ready for production. This branch usually contains the most recent changes and features being worked on by the development team. It's often the starting point for creating feature branches (where new features are developed) and hotfix branches (for urgent fixes).
-
-Each package is tagged with beta version numbers, and published to npm such as `@ohif/ui@3.6.0-beta.1`
-
-### `release` branch - The latest stable release
-
-This branch represents the latest stable version of the project that is considered ready for production. The code in this branch should be fully tested and vetted for release. Once the code in the master branch reaches a state where it's stable and ready to be released to users,
-we do a comprehensive code review and QA testing. Once the code is approved,
-we merge it into the release branch and tag a new release.
-
-Each package is tagged with version numbers, and published to npm such as `@ohif/ui@3.5.0`
-
-Note: `master` is always ahead of `release` branch. We publish both docker builds for beta and stable releases.
-
-Here is a schematic representation of our development workflow:
-
-![Alt text](platform/docs/docs/assets/img/github-readme-branches.png)
-
-
+The OHIF Medical Image Viewing Platform is maintained as a
+[`monorepo`][monorepo]. This means that this repository, instead of containing a
+single project, contains many projects. If you explore our project structure,
+you'll see the following:

+```bash
+.
+├── extensions              #
+│   ├── _example            # Skeleton of example extension
+│   ├── cornerstone         # 2D images w/ Cornerstone.js
+│   ├── dicom-html          # Structured Reports as HTML in viewport
+│   ├── dicom-microscopy    # Whole slide microscopy viewing
+│   ├── dicom-pdf           # View DICOM wrapped PDFs in viewport
+│   └── vtk                 # MPR and Volume support w/ VTK.js
+│
+├── platform                #
+│   ├── core                # Business Logic
+│   ├── i18n                # Internationalization Support
+│   ├── ui                  # React component library
+│   └── viewer              # Connects platform and extension projects
+│
+├── ...                     # misc. shared configuration
+├── lerna.json              # MonoRepo (Lerna) settings
+├── package.json            # Shared devDependencies and commands
+└── README.md               # This file
+```

+Want to better understand why and how we've structured this repository? Read
+more about it in our [Architecture Documentation](#todo).

 ### Requirements

 - [Yarn 1.17.3+](https://yarnpkg.com/en/docs/install)
- [Node 16+](https://nodejs.org/en/)
+- [Node 8+](https://nodejs.org/en/)
 - Yarn Workspaces should be enabled on your machine:
  - `yarn config set workspaces-experimental true`

@@ -149,119 +83,51 @@ Here is a schematic representation of our development workflow:

 #### To Develop

-_From this repository's root directory:_
-
 ```bash
-# Enable Yarn Workspaces
-yarn config set workspaces-experimental true
+# Force install
+yarn install --force

-# Restore dependencies
-yarn install
+# Link
+# Redundent with yarn workspaces
+npx lerna bootstrap
 ```

-## Commands
-
-These commands are available from the root directory. Each project directory
-also supports a number of commands that can be found in their respective
-`README.md` and `project.json` files.
-
-| Yarn Commands                | Description                                                   |
-| ---------------------------- | ------------------------------------------------------------- |
-| **Develop**                  |                                                               |
-| `dev` or `start`             | Default development experience for Viewer                     |
-| `test:unit`                  | Jest multi-project test runner; overall coverage              |
-| **Deploy**                   |                                                               |
-| `build`\*                    | Builds production output for our PWA Viewer                   |  |
-
-\* - For more information on our different builds, check out our [Deploy
-Docs][deployment-docs]
-
-## Project
-
-The OHIF Medical Image Viewing Platform is maintained as a
-[`monorepo`][monorepo]. This means that this repository, instead of containing a
-single project, contains many projects. If you explore our project structure,
-you'll see the following:
-
 ```bash
-.
-├── extensions               #
-│   ├── _example             # Skeleton of example extension
-│   ├── default              # basic set of useful functionalities (datasources, panels, etc)
-│   ├── cornerstone       # image rendering and tools w/ Cornerstone3D
-│   ├── cornerstone-dicom-sr # DICOM Structured Report rendering and export
-│   ├── cornerstone-dicom-sr # DICOM Structured Report rendering and export
-│   ├── cornerstone-dicom-seg # DICOM Segmentation rendering and export
-│   ├── cornerstone-dicom-rt # DICOM RTSTRUCT rendering
-│   ├── cornerstone-microscopy # Whole Slide Microscopy rendering
-│   ├── dicom-pdf # PDF rendering
-│   ├── dicom-video # DICOM RESTful Services
-│   ├── measurement-tracking # Longitudinal measurement tracking
-│   ├── tmtv # Total Metabolic Tumor Volume (TMTV) calculation
-|
-
-│
-├── modes                    #
-│   ├── _example             # Skeleton of example mode
-│   ├── basic-dev-mode       # Basic development mode
-│   ├── longitudinal         # Longitudinal mode (measurement tracking)
-│   ├── tmtv       # Total Metabolic Tumor Volume (TMTV) calculation mode
-│   └── microscopy          # Whole Slide Microscopy mode
-│
-├── platform                 #
-│   ├── core                 # Business Logic
-│   ├── i18n                 # Internationalization Support
-│   ├── ui                   # React component library
-│   ├── docs                 # Documentation
-│   └── viewer               # Connects platform and extension projects
-│
-├── ...                      # misc. shared configuration
-├── lerna.json               # MonoRepo (Lerna) settings
-├── package.json             # Shared devDependencies and commands
-└── README.md                # This file
+# Link for local dev
+cd ./extensions/my-package
+npx lerna add @ohif/my-package --scope=@ohif/my-package-consumer
 ```

-## Acknowledgments
+```bash
+# Add shared dev dependency for workspace
+yarn add --dev -W package-name
+```

-To acknowledge the OHIF Viewer in an academic publication, please cite
+// module vs main vs jsnext:main vs browser
+https://babeljs.io/blog/2018/06/26/on-consuming-and-publishing-es2015+-packages

-> _Open Health Imaging Foundation Viewer: An Extensible Open-Source Framework
-> for Building Web-Based Imaging Applications to Support Cancer Research_
->
-> Erik Ziegler, Trinity Urban, Danny Brown, James Petts, Steve D. Pieper, Rob
-> Lewis, Chris Hafey, and Gordon J. Harris
->
-> _JCO Clinical Cancer Informatics_, no. 4 (2020), 336-345, DOI:
-> [10.1200/CCI.19.00131](https://www.doi.org/10.1200/CCI.19.00131)
->
-> Open-Access on Pubmed Central:
-> https://www.ncbi.nlm.nih.gov/pmc/articles/PMC7259879/
+Webpack: https://webpack.js.org/configuration/resolve/

-or, for v1, please cite:
+UMD builds go through

-> _LesionTracker: Extensible Open-Source Zero-Footprint Web Viewer for Cancer
-> Imaging Research and Clinical Trials_
->
-> Trinity Urban, Erik Ziegler, Rob Lewis, Chris Hafey, Cheryl Sadow, Annick D.
-> Van den Abbeele and Gordon J. Harris
->
-> _Cancer Research_, November 1 2017 (77) (21) e119-e122 DOI:
-> [10.1158/0008-5472.CAN-17-0334](https://www.doi.org/10.1158/0008-5472.CAN-17-0334)
+- index.umd.js
+- Extensions passed in via window config

-**Note:** If you use or find this repository helpful, please take the time to
-star this repository on Github. This is an easy way for us to assess adoption
-and it can help us obtain future funding for the project.
+PWA builds go through

-This work is supported primarily by the National Institutes of Health, National
-Cancer Institute, Informatics Technology for Cancer Research (ITCR) program,
-under a
-[grant to Dr. Gordon Harris at Massachusetts General Hospital (U24 CA199460)](https://projectreporter.nih.gov/project_info_description.cfm?aid=8971104).
+- index.js
+- Extensions specified in file or by window config

-This project is tested with BrowserStack. Thank you for supporting open source
+> The module property should point to a script that utilizes ES2015 module
+> syntax but no other syntax features that aren't yet supported by browsers or
+> node. This enables webpack to parse the module syntax itself, allowing for
+> lighter bundles via tree shaking if users are only consuming certain parts of
+> the library.

-## License
+## Notes

-MIT © [OHIF](https://github.com/OHIF)
+Lerna requires `GH_TOKEN` for GitHub authentication token
+`git remote update` 1st call, need to verify host key

 <!--
  Links
@@ -271,59 +137,12 @@ MIT © [OHIF](https://github.com/OHIF)
 <!-- Badges -->
 [lerna-image]: https://img.shields.io/badge/maintained%20with-lerna-cc00ff.svg
 [lerna-url]: https://lerna.js.org/
-[netlify-image]: https://api.netlify.com/api/v1/badges/32708787-c9b0-4634-b50f-7ca41952da77/deploy-status
-[netlify-url]: https://app.netlify.com/sites/ohif-dev/deploys
-[all-contributors-image]: https://img.shields.io/badge/all_contributors-0-orange.svg?style=flat-square
-[circleci-image]: https://circleci.com/gh/OHIF/Viewers.svg?style=svg
-[circleci-url]: https://circleci.com/gh/OHIF/Viewers
-[codecov-image]: https://codecov.io/gh/OHIF/Viewers/branch/master/graph/badge.svg
-[codecov-url]: https://codecov.io/gh/OHIF/Viewers/branch/master
-[prettier-image]: https://img.shields.io/badge/code_style-prettier-ff69b4.svg?style=flat-square
-[prettier-url]: https://github.com/prettier/prettier
-[semantic-image]: https://img.shields.io/badge/%20%20%F0%9F%93%A6%F0%9F%9A%80-semantic--release-e10079.svg
-[semantic-url]: https://github.com/semantic-release/semantic-release
-<!-- ROW -->
-[npm-url]: https://npmjs.org/package/@ohif/app
-[npm-downloads-image]: https://img.shields.io/npm/dm/@ohif/app.svg?style=flat-square
-[npm-version-image]: https://img.shields.io/npm/v/@ohif/app.svg?style=flat-square
-[docker-pulls-img]: https://img.shields.io/docker/pulls/ohif/viewer.svg?style=flat-square
-[docker-image-url]: https://hub.docker.com/r/ohif/app
-[license-image]: https://img.shields.io/badge/license-MIT-blue.svg?style=flat-square
-[license-url]: LICENSE
-[percy-image]: https://percy.io/static/images/percy-badge.svg
-[percy-url]: https://percy.io/Open-Health-Imaging-Foundation/OHIF-Viewer
+[netlify-image]: https://api.netlify.com/api/v1/badges/a5d369ab-18a6-41c3-bcde-83805205ac7f/deploy-status
+[netlify-url]: https://app.netlify.com/sites/ohif/deploys
 <!-- Links -->
 [monorepo]: https://en.wikipedia.org/wiki/Monorepo
 [how-to-fork]: https://help.github.com/en/articles/fork-a-repo
 [how-to-clone]: https://help.github.com/en/articles/fork-a-repo#step-2-create-a-local-clone-of-your-fork
-[ohif-architecture]: https://docs.ohif.org/architecture/index.html
-[ohif-extensions]: https://docs.ohif.org/architecture/index.html
-[deployment-docs]: https://docs.ohif.org/deployment/
-[react-url]: https://reactjs.org/
-[pwa-url]: https://developers.google.com/web/progressive-web-apps/
-[ohif-viewer-url]: https://www.npmjs.com/package/@ohif/app
-[configuration-url]: https://docs.ohif.org/configuring/
-[extensions-url]: https://docs.ohif.org/extensions/
-<!-- Platform -->
-[platform-core]: platform/core/README.md
-[core-npm]: https://www.npmjs.com/package/@ohif/core
-[platform-i18n]: platform/i18n/README.md
-[i18n-npm]: https://www.npmjs.com/package/@ohif/i18n
-[platform-ui]: platform/ui/README.md
-[ui-npm]: https://www.npmjs.com/package/@ohif/ui
-[platform-viewer]: platform/app/README.md
-[viewer-npm]: https://www.npmjs.com/package/@ohif/app
-<!-- Extensions -->
-[extension-cornerstone]: extensions/cornerstone/README.md
-[cornerstone-npm]: https://www.npmjs.com/package/@ohif/extension-cornerstone
-[extension-dicom-html]: extensions/dicom-html/README.md
-[html-npm]: https://www.npmjs.com/package/@ohif/extension-dicom-html
-[extension-dicom-microscopy]: extensions/dicom-microscopy/README.md
-[microscopy-npm]: https://www.npmjs.com/package/@ohif/extension-dicom-microscopy
-[extension-dicom-pdf]: extensions/dicom-pdf/README.md
-[pdf-npm]: https://www.npmjs.com/package/@ohif/extension-dicom-pdf
-[extension-vtk]: extensions/vtk/README.md
-[vtk-npm]: https://www.npmjs.com/package/@ohif/extension-vtk
-<!-- prettier-ignore-end -->

-[![FOSSA Status](https://app.fossa.io/api/projects/git%2Bgithub.com%2FOHIF%2FViewers.svg?type=large)](https://app.fossa.io/projects/git%2Bgithub.com%2FOHIF%2FViewers?ref=badge_large)
+
+<!-- prettier-ignore-end -->
@@ -1,72 +1,50 @@
-// https://babeljs.io/docs/en/options#babelrcroots
-const { extendDefaultPlugins } = require('svgo');
+const aliases = require("./aliases.config");
+const path = require("path");

 module.exports = {
-  babelrcRoots: ['./platform/*', './extensions/*', './modes/*'],
+  // https://babeljs.io/docs/en/options#babelrcroots
  presets: [
-    '@babel/preset-env',
-    '@babel/preset-react',
-    '@babel/preset-typescript',
-  ],
-  plugins: [
    [
-      'inline-react-svg',
+      "@babel/preset-env",
      {
-        svgo: {
-          plugins: extendDefaultPlugins([
-            {
-              name: 'removeViewBox',
-              active: false,
-            },
-          ]),
-        },
-      },
+        targets: {
+          ie: "11"
+        }
+      }
    ],
-    ['@babel/plugin-proposal-class-properties', { loose: true }],
-    '@babel/plugin-transform-typescript',
-    ['@babel/plugin-proposal-private-property-in-object', { loose: true }],
-    ['@babel/plugin-proposal-private-methods', { loose: true }],
+    "@babel/preset-react"
+  ],
+  babelrcRoots: ["./platform/*", "./extensions/*"],
+  plugins: [
+    "inline-react-svg",
+    "@babel/plugin-proposal-class-properties",
+    "@babel/plugin-proposal-object-rest-spread",
+    "@babel/plugin-syntax-dynamic-import",
+    "@babel/plugin-transform-regenerator",
+    "@babel/plugin-transform-runtime",
+    [
+      "module-resolver",
+      {
+        // https://github.com/tleunen/babel-plugin-module-resolver/issues/338
+        // There seem to be a bug with module-resolver with a mono-repo setup:
+        // It doesn't resolve paths correctly when using root/alias combo, so we
+        // use this function instead.
+        resolvePath(sourcePath, currentFile, opts) {
+          // This will return undefined if aliases has no key for the sourcePath,
+          // in which case module-resolver will fallback on its default behaviour.
+          return aliases[sourcePath];
+        }
+      }
+    ]
  ],
  env: {
-    test: {
-      presets: [
-        [
-          // TODO: https://babeljs.io/blog/2019/03/19/7.4.0#migration-from-core-js-2
-          '@babel/preset-env',
-          {
-            modules: 'commonjs',
-            debug: false,
-          },
-        ],
-        '@babel/preset-react',
-        '@babel/preset-typescript',
-      ],
-      plugins: [
-        '@babel/plugin-proposal-object-rest-spread',
-        '@babel/plugin-syntax-dynamic-import',
-        '@babel/plugin-transform-regenerator',
-        '@babel/plugin-transform-runtime',
-        '@babel/plugin-transform-typescript',
-      ],
+    debug: {
+      sourceMaps: "inline",
+      retainLines: true
    },
-    production: {
-      presets: [
-        // WebPack handles ES6 --> Target Syntax
-        ['@babel/preset-env', { modules: false }],
-        '@babel/preset-react',
-        '@babel/preset-typescript',
-      ],
-      ignore: ['**/*.test.jsx', '**/*.test.js', '__snapshots__', '__tests__'],
-    },
-    development: {
-      presets: [
-        // WebPack handles ES6 --> Target Syntax
-        ['@babel/preset-env', { modules: false }],
-        '@babel/preset-react',
-        '@babel/preset-typescript',
-      ],
-      plugins: ['react-hot-loader/babel'],
-      ignore: ['**/*.test.jsx', '**/*.test.js', '__snapshots__', '__tests__'],
-    },
-  },
+    build: {
+      ignore: ["**/*.test.jsx", "**/*.test.js", "__snapshots__", "__tests__"]
+    }
+  }
+  // ignore: ["node_modules"]
 };
@@ -1 +0,0 @@
-15ad8f29cdda5796ddeea92d0acabbe97681eec6
@@ -0,0 +1 @@
+_book/
@@ -0,0 +1 @@
+docs.ohif.org
@@ -0,0 +1,46 @@
+# How To: Documentation Step-by-Step
+
+We use [GitBook](https://www.gitbook.com/) to create our documentation. It primarily uses markdown, html, css, js, misc. plugins, and configuration to generate high quality, easy to read, and easy to maintain documentation.
+
+## Getting Started
+
+_Requirements:_
+
+Make sure you have the [`gitbook-cli`](https://www.npmjs.com/package/gitbook-cli) installed globally:
+
+> `npm install -g gitbook-cli`
+
+### Editing and Previewing Changes
+
+Currently, you can only edit and preview a single "book" at a time. We maintain one "book" per API major version. You can find each version's book at:
+
+_Past Versions:_
+
+- Template:
+  - `<project-root>/docs/v<versionNumber>`
+- Examples:
+  - `/docs/v1`
+  - `/docs/v2`
+
+_Latest Version:_
+
+The latest version will always be located in `/docs/latest`
+
+_Live Preview:_
+
+In your terminal / command prompt:
+
+```bash
+cd /docs/latest
+gitbook install
+gitbook serve
+```
+
+Which should generate output like:
+
+> starting server...
+> serving book on http://localhost:4000
+
+Navigating to the the provided URL will show a preview of what the generated book should look like. Any edits you make to the book's markdown files should automatically update in your browser.
+
+### Publishing
@@ -0,0 +1,54 @@
+<div class='row'>
+	<div class='column' style='text-align: right; padding: 0 20px'>
+		<strong>Looking for a Deploy Preview?</strong>
+		<a onclick="function redirect() { window.location.href='/demo/'; } redirect();">Deploy Preview for Viewer</a>
+	</div>
+	<div class='column' style='text-align: left; padding: 0 20px'>
+		<a href="https://www.netlify.com">
+		  <img src="https://www.netlify.com/img/global/badges/netlify-color-bg.svg"/>
+		</a>
+	</div>
+</div>
+
+> ATTENTION! You are looking at the docs for the `React` version of the OHIF
+> Viewer. If you're looking for the `Meteor` version's documentation (now
+> deprecated), select it's version from the dropdown box in the top left corner
+> of this page.
+
+# Introduction
+
+The [Open Health Imaging Foundation][ohif-org] (OHIF) Viewer is an open source,
+web-based, medical imaging viewer. It can be configured to connect to Image
+Archives that support [DicomWeb][dicom-web], and offers support for mapping to
+proprietary API formats. OHIF maintained extensions add support for viewing,
+annotating, and reporting on DICOM images in 2D (slices) and 3D (volumes).
+
+![OHIF Viewer Screenshot](../assets/img/viewer.png)
+
+<center><i>The <strong>OHIF Viewer</strong>: A general purpose DICOM Viewer (<a href="http://viewer.ohif.org/">Live Demo</a>)</center>
+
+The Open Health Imaging Foundation intends to provide a simple general purpose
+DICOM Viewer which can be easily extended for specific uses. If you find
+yourself unable to extend the viewer for your purposes, please reach out via our
+[GitHub issues][gh-issues]. We are actively seeking feedback on ways to improve
+our integration and extension points.
+
+## Where to Next?
+
+Check out these helpful links:
+
+- Ready to dive into some code? Check out our
+  [Getting Started Guide](./essentials/getting-started.md).
+- We're an active, vibrant community.
+  [Learn how you can be more involved.](./contributing.md)
+- Feeling lost? Read our [help page](./help.md).
+
+<!--
+  Links
+  -->
+
+<!-- prettier-ignore-start -->
+[ohif-org]: https://www.ohif.org
+[dicom-web]: https://en.wikipedia.org/wiki/DICOMweb
+[gh-issues]: https://github.com/OHIF/Viewers/issues
+<!-- prettier-ignore-end -->
@@ -0,0 +1,51 @@
+# OHIF Viewers
+
+- 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)
+  - [Translating](essentials/translating.md)
+  - [Troubleshooting](essentials/troubleshooting.md)
+- [Scope of Project](essentials/scope-of-project.md)
+
+---
+
+- [Advanced](advanced/index.md)
+- [Architecture](advanced/architecture.md)
+  - [Overview](advanced/architecture.md#overview)
+  - [Business Logic](advanced/architecture.md#business-logic)
+  - [Component Library](advanced/architecture.md#react-component-library)
+  - [Extensions](advanced/architecture.md#misc-extensions)
+  - [Diagram](advanced/architecture.md#diagram)
+  - [Common Questions](advanced/architecture.md#common-questions)
+- [Extensions](advanced/extensions.md)
+  - [Overview](advanced/extensions.md#overview)
+  - [Modules](advanced/extensions.md#modules)
+  - [Registering](advanced/extensions.md#registering-extensions)
+  - [OHIF Maintained](advanced/extensions.md#ohif-maintained-extensions)
+- [Custom Tools](advanced/custom-tools.md)
+
+---
+
+- [Deployment](deployment/index.md)
+  - [Embedded](deployment/index.md#embedded-viewer)
+  - [Stand-alone](deployment/index.md#stand-alone-viewer)
+  - [Data](deployment/index.md#data)
+- Recipes
+  - 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)
+    - [Google Cloud Healthcare](connecting-to-image-archives/google-cloud-healthcare.md)
+
+---
+
+- [Contributing](contributing.md)
+- [FAQ](frequently-asked-questions.md)
+- [Roadmap](roadmap.md)
+- [Help](help.md)
@@ -0,0 +1,62 @@
+<table>
+    <thead>
+        <tr>
+            <th>Extension</th>
+            <th>Description</th>
+            <th>Modules</th>
+        </tr>
+    </thead>
+    <tbody>
+        <!-- CORNERSTONE.js -->
+        <tr>
+            <td>
+                <a href="https://www.npmjs.com/package/ohif-cornerstone-extension">
+                    Cornerstone
+                </a>
+            </td>
+            <td>
+                A viewport powered by <code>cornerstone.js</code>. Adds support for 2D DICOM rendering and manipulation, as well as support for the tools features in <a href="https://tools.cornerstonejs.org/examples/"><code>cornerstone-tools</code></a>. Also adds "CINE Dialog" to the Toolbar.
+            </td>
+            <td>Viewport, Toolbar</td>
+        </tr>
+        <!-- VTK.js -->
+        <tr>
+            <td>
+                <a href="https://www.npmjs.com/package/ohif-vtk-extension">
+                    VTK.js
+                </a>
+            </td>
+            <td>
+                A viewport powered by <code>vtk.js</code>. Adds support for volume renderings and advanced features like MPR. Also adds "3D Rotate" to the Toolbar.
+            </td>
+            <td>Viewport, Toolbar</td>
+        </tr>
+        <tr>
+            <td>
+                <a href="">HTML</a>
+            </td>
+            <td>
+                Renders text and HTML content for <a href="https://github.com/OHIF/Viewers/blob/react/extensions/ohif-dicom-html-extension/src/OHIFDicomHtmlSopClassHandler.js#L7-L15">specific SopClassUIDs</a>.
+            </td>
+            <td>Viewport, SopClassHandler</td>
+        </tr>
+        <tr>
+            <td>
+                <a href="https://www.npmjs.com/package/ohif-dicom-pdf-extension">PDF</a>
+            </td>
+            <td>
+                Renders PDFs for a <a href="https://github.com/OHIF/Viewers/blob/react/extensions/ohif-dicom-pdf-extension/src/OHIFDicomPDFSopClassHandler.js#L8">specific SopClassUID</a>.
+            </td>
+            <td>Viewport, SopClassHandler</td>
+        </tr>
+        <tr>
+            <td>
+                <a href="https://www.npmjs.com/package/ohif-dicom-microscopy-extension">Microscopy</a>
+            </td>
+            <td>
+                Renders Microscopy images for a <a href="https://github.com/OHIF/Viewers/blob/react/extensions/ohif-dicom-microscopy-extension/src/DicomMicroscopySopClassHandler.js#L6">specific SopClassUID</a>.
+            </td>
+            <td>Viewport, SopClassHandler</td>
+        </tr>
+    </tbody>
+</table>
@@ -0,0 +1,109 @@
+# 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!
+
+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`][viewers-project] project contains the source code for the
+OHIF Medical Imaging Viewer. It is effectively a React [progressive web
+app][pwa] (PWA) that combines the business logic housed in
+[`OHIF/ohif-core`][core] and the components in our React Component library
+[`OHIF/react-viewerbase`][component-library]. It provides customization for
+common use cases through [configuration][configuration] and for adding
+functionality via [extensions][extensions].
+
+### 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:
+
+- Hotkeys
+- DICOM Web
+- Hanging Protocols
+- Managing a study's measurements
+- Managing a study's DICOM metadata
+- A flexible pattern for extensions
+- [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.
+
+### 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.
+
+[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).
+
+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.
+
+1. (optional) `extensions` can be registered with `ohif-core`'s extension
+   manager
+2. `ohif-core` provides bussiness logic and a way for `viewer` to access
+   registered extensions
+3. The `viewer` composes and provides data to components from our component
+   library (`react-viewerbase`)
+4. 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)
+
+<center><i>architecture diagram</i></center>
+
+## Common Questions
+
+> 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.
+
+<!--
+  Links
+  -->
+
+<!-- prettier-ignore-start -->
+[viewers-project]: https://github.com/OHIF/Viewers
+[pwa]: https://developers.google.com/web/progressive-web-apps/
+[core]: https://github.com/OHIF/ohif-core
+[component-library]: https://github.com/OHIF/react-viewerbase
+[configuration]: ../essentials/configuration.md
+[extensions]: ./extensions.m
+<!-- prettier-ignore-end -->
@@ -0,0 +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).
@@ -0,0 +1,230 @@
+# Extensions
+
+Extensions add new functionality to the viewer by registering one or more
+modules. They go one step further than configuration in that they allow us to
+inject custom React components, so long as they adhere to the module's
+interface. This can be something as simple as adding a new button to the
+toolbar, or as complex as a new viewport capable of rendering volumes in 3D.
+
+- [Overview](#overview)
+- [Modules](#modules)
+  - [Commands](#commands)
+  - [Hotkeys](#hotkeys)
+  - [Toolbar](#toolbar)
+  - [Panel](#panel)
+  - [Viewport](#viewport)
+  - [SOP Class Handler](#sopclasshandler)
+
+## Overview
+
+At a glance, an extension is a javascript object that has an `id` property, and
+one or more "module" methods. You can find an abbreviated extension below, or
+[view the source][example-ext-src] of our example extension.
+
+```js
+export default {
+    /**
+     * Only required property. Should be a unique value across all extensions.
+     */
+    id: 'example-extension',
+
+    /**
+     * Registers one or more named commands scoped to a context. Commands are
+     * the primary means for...
+     */
+    getCommandsModule() {
+        return {
+            defaultContext: 'VIEWER'
+            actions: { ... },
+            definitions: { ... }
+        }
+    },
+
+    /**
+     * Allows you to provide toolbar definitions that will be merged with any
+     * existing application toolbar configuration. Used to determine which
+     * buttons should be visible when, their order, what happens when they're
+     * clicked, etc.
+     */
+    getToolbarModule() {
+        return {
+            definitions: [ ... ],
+            defaultContext: 'ACTIVE_VIEWPORT::CORNERSTONE'
+        }
+    }
+
+    /**
+     * Not yet implemented
+     */
+    getPanelModule: () => null,
+
+    /**
+     * Registers a ReactComponent that should be used to render data in a
+     * Viewport. The first registered viewport is our "default viewport". If
+     * more than one viewport is registered, we use `SopClassHandlers` to
+     * determine which viewport should be used.
+    */
+    getViewportModule: () => reactViewportComponent,
+
+    /** Provides a whitelist of SOPClassUIDs the viewport is capable of rendering.
+     *  Can modify default behavior for methods like `getDisplaySetFromSeries` */
+    getSopClassHandler: () => {
+        id: 'some-other-unique-id',
+        sopClassUids: [ ... ],
+        getDisplaySetFromSeries: (series, study, dicomWebClient, authorizationHeaders) => { ... }
+    },
+}
+```
+
+### Modules
+
+There are a few different module types. Each module type allows us to extend the
+viewer in a different way, and provides a consistent API for us to do so. You
+can find a full list of the different types of modules
+[`in ohif-core`][module-types]. Information on each type of module, it's API,
+and how we determine when/where it should be used is included below.
+
+> NOTE: Modifying the extensions/modules registered to the OHIF Viewer currently
+> requires us to import and pass extensions to the ExtensionManager in
+> `src/App.js`, then rebuild the application. Long-term, we intend to make it
+> possible to accomplish this without a build step.
+
+#### Commands
+
+The Commands Module allows us to register one or more commands scoped to
+specific contexts. Commands can be run by [hotkeys][#], [toolbar buttons][#],
+and any registered custom react component (like a [viewport][#] or [panel][#]).
+Here is a simple example commands module:
+
+```js
+{
+    getCommandsModule() {
+        return {
+            actions: {
+                speak: ({ viewports, words }) => {
+                    console.log(viewports, words);
+                },
+            },
+            definitions: {
+                rotateViewportCW: {
+                    commandFn: actions.rotateViewport,
+                    storeContexts: ['viewports'],
+                    options: { rotation: 90 }
+                },
+                rotateViewportCCW: {
+                    commandFn: actions.rotateViewport,
+                    storeContexts: ['viewports'],
+                    options: { rotation: -90 },
+                    context: 'ACTIVE_VIEWER::CORNERSTONE'
+                },
+            },
+            defaultContext: 'VIEWER'
+        }
+    }
+}
+```
+
+#### Viewport
+
+An extension can register a Viewport Module by providing a `getViewportModule()`
+method that returns a React Component. The React component will receive the
+following props:
+
+```js
+children: PropTypes.arrayOf(PropTypes.element)
+studies: PropTypes.object,
+displaySet: PropTypes.object,
+viewportData: PropTypes.object, // { studies, displaySet }
+viewportIndex: PropTypes.number,
+children: PropTypes.node,
+customProps: PropTypes.object
+```
+
+Viewport components are managed by the `LayoutManager`. Which Viewport component
+is used depends on:
+
+- The Layout Configuration
+- Registered SopClassHandlers
+- The SopClassUID for visible/selected datasets
+
+![Cornerstone Viewport](../assets/img/extensions-viewport.png)
+
+<center><i>An example of three Viewports</i></center>
+
+For a complete example implementation,
+[check out the OHIFCornerstoneViewport](https://github.com/OHIF/Viewers/blob/react/extensions/ohif-cornerstone-extension/src/OHIFCornerstoneViewport.js).
+
+#### Toolbar
+
+An extension can register a Toolbar Module by providing a `getToolbarModule()`
+method that returns a React Component. The component does not receive any props.
+If you want to modify or react to state, you will need to connect to the redux
+store.
+
+![Toolbar Extension](../assets/img/extensions-toolbar.gif)
+
+<center><i>A toolbar extension example</i></center>
+
+Toolbar components are rendered in the `ToolbarRow` component.
+
+For a complete example implementation,
+[check out the OHIFCornerstoneViewport's Toolbar Module](https://github.com/OHIF/Viewers/blob/react/extensions/ohif-cornerstone-extension/src/ToolbarModule.js).
+
+#### SopClassHandler
+
+...
+
+#### Panel
+
+> The panel module is not yet in use.
+
+#### Hotkeys
+
+...
+
+### Registering Extensions
+
+Extensions are registered for the application at startup. The
+`ExtensionManager`, exposed by `ohif-core`, registers a list of extensions with
+our application's store. Each module provided by the extension becomes available
+via `state.plugins.availablePlugins`, and consists of three parts: id, type
+([PLUGIN_TYPE](https://github.com/OHIF/ohif-core/blob/43c08a29eff3fb646a0e83a03a236ddd84f4a6e8/src/plugins.js#L1-L6)),
+and the return value of the module method.
+
+In a future version, we will likely expose a way to provide the extensions you
+would like included at startup.
+
+_app.js_
+
+```js
+import { createStore, combineReducers } from 'redux';
+import OHIF from 'ohif-core';
+import OHIFCornerstoneExtension from 'ohif-cornerstone-extension';
+
+const combined = combineReducers(OHIF.redux.reducers);
+const store = createStore(combined);
+const extensions = [new OHIFCornerstoneExtension()];
+
+// Dispatches the `addPlugin` action to the store
+// Adding extension modules to `state.plugins.availablePlugins`
+ExtensionManager.registerExtensions(store, extensions);
+```
+
+## OHIF Maintained Extensions
+
+A small number of powerful extensions for popular use cases are maintained by
+OHIF. They're co-located in the
+[`OHIF/Viewers`](https://github.com/OHIF/Viewers/tree/react/) repository, in the
+top level [`extensions/`](https://github.com/OHIF/Viewers/tree/react/extensions)
+directory.
+
+{% include "./_maintained-extensions-table.md" %}
+
+<!--
+    Links
+-->
+
+<!-- prettier-ignore-start -->
+[example-ext-src]: https://github.com/OHIF/Viewers/blob/master/extensions/_ohif-example-extension/src/index.js)
+[module-types]: https://github.com/OHIF/ohif-core/blob/43c08a29eff3fb646a0e83a03a236ddd84f4a6e8/src/plugins.js#L1-L6
+<!-- prettier-ignore-end -->
@@ -0,0 +1,3 @@
+# Advanced
+
+Advanced topics go beyond basic configuration and deployment. Their goal is to provide insight into this project's architecture and guidance on leveraging extensions.
@@ -0,0 +1,23 @@
+# MonoRepos: A Crash Course
+
+- [Lerna][lerna]
+
+Solutions:
+
+## Semantic-Release
+
+- [Semantic-Release](https://github.com/semantic-release/semantic-release/issues/193#issuecomment-462063871)
+- [Multi-semantic-release](https://github.com/dhoulb/multi-semantic-release)
+- [semantic-release-monorepo](https://github.com/Updater/semantic-release-monorepo)
+
+# Netlify
+
+- https://community.netlify.com/t/best-practices-for-deploying-sites-from-monorepos/818
+
+<!--
+  Links
+  -->
+
+<!-- prettier-ignore-start -->
+[lerna]: https://github.com/lerna/lerna
+<!-- prettier-ignore-end -->
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!-- Generator: Adobe Illustrator 18.0.0, SVG Export Plug-In . SVG Version: 6.00 Build 0)  -->
+<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
+<svg version="1.1" id="Layer_1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" viewBox="0 0 260.4 82.9" enable-background="new 0 0 260.4 82.9" xml:space="preserve">
+<g>
+	<path fill="#525DF9" d="M31.7,8.9c9.6,0,16.5,4.9,19,13.4l0.1,0.4h9.6l-0.1-0.6C57.6,8.5,46.7,0,31.8,0C13.7,0,0,14.1,0,32.9   s13.7,32.9,31.8,32.9c14.9,0,25.8-8.5,28.6-22.1l0.1-0.6h-9.6l-0.1,0.4c-2.5,8.5-9.5,13.4-19,13.4c-13.1,0-21.9-9.6-21.9-24   C9.8,18.6,18.6,8.9,31.7,8.9z"/>
+	<path fill="#525DF9" d="M110.1,58c-2.3,0-3.5-1.4-3.5-4.2V32.7c0-8.8-7.2-14.7-17.9-14.7c-7.5,0-16.7,3.9-18.3,14.9l-0.1,0.6h8.4   l0.1-0.4c1.4-5.7,5.8-6.9,9.3-6.9c6,0,9.5,2.7,9.5,7.4v2.6l-13.6,1.4c-7.6,0.8-15.7,5-15.7,14.6c0,8.1,6,13.5,14.8,13.5   c6.5,0,11.8-3.4,15-6.8c1.3,4.2,4.5,6.5,9.1,6.5c1.7,0,3.2-0.3,5.2-0.9l0.3-0.1v-7l-0.6,0.2C111.5,57.9,110.9,58,110.1,58z    M97.7,43.5v7.3c-4.6,4.6-8.9,6.7-13.5,6.7c-2,0-6.8-0.6-6.8-5.7c0-3.8,2.8-6.3,7.4-6.9L97.7,43.5z"/>
+	<path fill="#525DF9" d="M146.5,18c-6.5,0-12,3.1-15.2,6.1v-5.2h-8.9v46h8.9V34.3c2.2-3.2,6.7-8.3,13-8.3c5.6,0,8.7,3.1,8.7,8.8   v30.1h8.9V33.3C161.9,23.7,156.1,18,146.5,18z"/>
+	<path fill="#525DF9" d="M195.8,18c-6.5,0-12,3.1-15.2,6.1v-5.2h-8.9v46h8.9V34.3c2.2-3.2,6.7-8.3,13-8.3c5.6,0,8.7,3.1,8.7,8.8   v30.1h8.9V33.3C211.2,23.7,205.4,18,195.8,18z"/>
+	<polygon fill="#525DF9" points="251.3,18.9 238.6,51.8 237.8,47.9 225.6,18.9 216.2,18.9 234.3,62.4 226,82.9 235,82.9 260.4,18.9     "/>
+</g>
+</svg>
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!-- Generator: Adobe Illustrator 18.0.0, SVG Export Plug-In . SVG Version: 6.00 Build 0)  -->
+<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
+<svg version="1.1" id="Layer_1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px"
+	 viewBox="0 0 445.9 638" enable-background="new 0 0 445.9 638" xml:space="preserve">
+<g>
+	<g>
+		<path fill="#5F5DF9" d="M224.5,638C101.1,638,0,537.8,0,414.7V223.3C0,100.2,101.1,0,224.5,0c109.6,0,202.8,78.3,220.9,186.1
+			c2.9,17.4-8.6,33.8-26,36.8c-17.4,2.9-33.7-8.8-36.7-26.2c-13-77-78.6-132.9-157-132.9c-88.2,0-159.3,71.6-159.3,159.5v191.4
+			c0,88,71.1,159.5,159.3,159.5c78.3,0,144.2-55.9,157.1-132.9c2.9-17.4,19.3-29.1,36.6-26.2c17.4,2.9,28.6,19.4,25.7,36.7
+			C427.2,559.7,334,638,224.5,638z"/>
+	</g>
+	<g opacity="0.5">
+		<path fill="#5F5DF9" d="M153.6,347.7c-17.6,0-30.7-14.3-30.7-31.9v-92.3c0-56.8,45.8-103,102.8-103c38.9,0,73.9,21.6,91.7,56.4
+			c8,15.7,1.7,34.9-14,42.9c-15.7,8-35,1.8-43-13.9c-6.8-13.4-21-21.7-35.8-21.7c-21.8,0-40.2,17.6-40.2,39.2v92.3
+			C184.3,333.4,171.2,347.7,153.6,347.7z"/>
+	</g>
+</g>
+</svg>
@@ -0,0 +1,50 @@
+{
+  "title": "OHIF",
+  "description": "Documentation for the OHIF framework",
+  "gitbook": ">3.0.0",
+  "plugins": [
+    "edit-link",
+    "theme-cornerstone",
+    "-fontsettings",
+    "github",
+    "ga",
+    "sitemap",
+    "anchors",
+    "versions"
+  ],
+  "pluginsConfig": {
+    "edit-link": {
+      "base": "https://github.com/OHIF/Viewers/edit/master/docs",
+      "label": "Edit This Page"
+    },
+    "github": {
+      "url": "https://github.com/OHIF/Viewers"
+    },
+    "ga": {
+      "token": "UA-110573590-2"
+    },
+    "sitemap": {
+      "hostname": "https://docs.ohif.org"
+    },
+    "versions": {
+      "gitbookConfigURL": "https://raw.githubusercontent.com/OHIF/Viewers/master/docs/book.json",
+      "options": [
+        {
+          "value": "https://docs.ohif.org/history/v1/",
+          "text": "Version 1.0.0 (Meteor)"
+        },
+        {
+          "value": "https://docs.ohif.org/",
+          "text": "Version 2.0.0",
+          "selected": true
+        }
+      ]
+    }
+  },
+  "links": {
+    "sharing": {
+      "facebook": false,
+      "twitter": false
+    }
+  }
+}
@@ -0,0 +1,124 @@
+# Google Cloud Healthcare
+
+> ATTENTION: The original documentation for this integration lives in the legacy
+> `version 1` Meteor documentation. You can
+> [find it here](/history/v1/connecting-to-image-archives/google-cloud-healthcare.html).
+> These docs will mirror the Meteor documentation until our `React`
+> implementation has been updated to work with Google Cloud Healthcare.
+
+> The [Google Cloud Healthcare API](https://cloud.google.com/healthcare/) is a
+> powerful option for storing medical imaging data in the cloud.
+
+An alternative to deploying your own PACS is to use a software-as-a-service
+provider such as Google Cloud. The Cloud Healthcare API promises to be a
+scalable, secure, cost effective image storage solution for those willing to
+store their data in the cloud. It offers an
+[almost-entirely complete DICOMWeb API](https://cloud.google.com/healthcare/docs/dicom)
+which requires tokens generated via the
+[OAuth 2.0 Sign In flow](https://developers.google.com/identity/sign-in/web/sign-in).
+Images can even be transcoded on the fly if this is desired. The Cloud
+Healthcare API is a very attractive option because it allows us to avoid
+deploying the Meteor server entirely. We can just deploy OHIF as a client-only
+static site application.
+
+## Setup a Google Cloud Healthcare Project
+
+- Create a Google Cloud account
+- Create a project in Google Cloud
+- Enable the [Cloud Healthcare API](https://cloud.google.com/healthcare/) for
+  your project.
+  - (Optional): Create a Dataset and Data Store for storing your DICOM data
+- Enable the
+  [Cloud Resource Manager API](https://cloud.google.com/resource-manager/) for
+  your project.
+  - _Note:_ If you are having trouble finding the APIs, use the search box at
+    the top of the Cloud console.
+- Go to APIs & Services > Credentials to create an OAuth Consent screen and fill
+  in your application details.
+  - Under Scopes for Google APIs, click "manually paste scopes".
+  - Add the following scopes:
+    - `https://www.googleapis.com/auth/cloudplatformprojects.readonly`
+    - `https://www.googleapis.com/auth/cloud-healthcare`
+- Go to APIs & Services > Credentials to create a new set of credentials:
+
+  - Choose the "Web Application" type
+  - Set up an
+    [OAuth 2.0 Client ID](https://support.google.com/cloud/answer/6158849?hl=en)
+  - Add your domain (e.g. `http://localhost:3000`) to Authorized JavaScript
+    origins.
+  - Add your domain, plus `_oauth/google` (e.g.
+    `http://localhost:3000/_oauth/google`) to Authorized Redirect URIs.
+  - Save your Client ID for later.
+
+- (Optional): Enable Public Datasets that are being hosted by Google:
+  https://cloud.google.com/healthcare/docs/resources/public-datasets/
+
+## Run the viewer with your OAuth Client ID
+
+1. Open the `config/oidc-googleCloud.json` file and change `YOURCLIENTID` to
+   your Client ID value.
+1. Run the OHIF Viewer using the oidc-googleCloud.json configuration file
+
+```bash
+cd OHIFViewer
+METEOR_PACKAGE_DIRS="../Packages" meteor npm install
+METEOR_PACKAGE_DIRS="../Packages" meteor --settings ../config/oidc-googleCloud.json
+```
+
+## Running via Docker
+
+OHIF is also providing a Docker container which can connect to Google Cloud
+Healthcare with a Client ID which is provided at runtime. This is a very simple
+method to get up and running. Internally, the container is running
+[Nginx](https://nginx.org/) to serve the
+[Standalone Viewer](../standalone-viewer/usage.md).
+
+1. Install Docker (https://www.docker.com/)
+1. Run the Docker container, providing a Client ID as an environment variable.
+   Client IDs look like `xyz.apps.googleusercontent.com`.
+
+```bash
+docker run --env CLIENT_ID=$CLIENT_ID --publish 3000:80 ohif/viewer-google-cloud:latest
+```
+
+## Building the ohif/viewer-google-cloud Docker Image
+
+The
+[ohif/viewer-google-cloud](https://cloud.docker.com/u/ohif/repository/docker/ohif/viewer-google-cloud)
+Docker image is built as follows. The Dockerfile and nginx.conf are in the
+`/dockersupport/viewer-google-cloud` folder.
+
+1. [Install Meteor](https://www.meteor.com/install)
+1. Clone the repository
+
+```bash
+git clone https://github.com/OHIF/Viewers.git
+cd Viewers
+```
+
+1. Install meteor-build-client-fixed2 so you can build the Standalone Viewer
+
+```bash
+npm install -g meteor-build-client-fixed2
+```
+
+1. Build the Standalone client-only OHIF Viewer
+
+```bash
+cd OHIFViewer/
+METEOR_PACKAGE_DIRS="../Packages" meteor npm install
+METEOR_PACKAGE_DIRS="../Packages" meteor-build-client-fixed2 ../dockersupport/viewer-google-cloud/build -s ../config/oidc.json
+```
+
+1. Build the Docker image
+
+```bash
+cd ../dockersupport/viewer-google-cloud
+docker build -t ohif/viewer-google-cloud .
+```
+
+1. Run the Docker image using an OAuth Client ID
+
+```bash
+docker run --env CLIENT_ID={$someID}.apps.googleusercontent.com --publish 3000:80 ohif/viewer-google-cloud
+```
@@ -0,0 +1,103 @@
+# Contributing
+
+## I would like to contribute code - how do I do this?
+
+Fork the repository, make your change and submit a pull request.
+
+- The OHIF Viewer consists of code from three different repositories. Make sure
+  your change is modifying the appropriate one:
+  - `ohif-core`: Business Logic
+  - `react-viewerbase`: Reusable React Component Library
+  - `Viewers`: The glue, PWA, and primary extension point
+- At a minimum, you may want to read the following documentation:
+  - [Essentials: Getting Started](./essentials/getting-started.md)
+  - [Advanced: Architecture](./advanced/architecture.md)
+
+### When changes impact multiple repositories
+
+This is a particularly tricky scenario. We don't want to publish code in one
+repository, just so we can test and complete the other half of its requirements
+in another. Thankfully, there are a couple of ways you can test unpublished
+dependent changes locally before publishing:
+
+- [Use `yarn link`](https://yarnpkg.com/en/docs/cli/link)
+
+For example if you are working on `ohif-core` and would like to use your local
+version to debug a problem in `Viewers`, simply run yarn link inside of the
+`ohif-core` project.
+
+- If you're experiencing issues with `yarn link`,
+  [try `yalc`](https://github.com/whitecolor/yalc)
+
+Yalc provides an improved workflow as we add more and more dependent packages
+that are "in-progress". This comes into play as we begin working on extensions
+and their dependencies.
+
+```js
+// Install yalc for the first time
+yarn global add yalc
+
+// EXAMPLE: using an in-development version of ohif-core w/ Viewers locally
+// 1. Navigate to ohif-core's project root
+yarn install
+yalc publish
+
+// 2. Run the following after each change to ohif-core
+yarn build
+yalc push .
+
+// 3. Use the local package in our Viewers project. Navigate to the Viewers
+//    Project root.
+yarn install
+yalc add ohif-core
+yarn run dev
+```
+
+## Any guidance on submitting changes?
+
+While we do appreciate code contributions, triaging and integrating contributed
+code changes can be very time consuming. Please consider the following tips when
+working on your pull requests:
+
+- Functionality is appropriate for the repository. Consider creating a GitHub
+  issue to discuss your suggested changes.
+- The scope of the pull request is not too large. Please consider separate pull
+  requests for each feature as big pull requests are very time consuming to
+  understand.
+
+We will provide feedback on your pull requests as soon as possible. Following
+the tips above will help ensure your changes are reviewed.
+
+## Testing contribution pull requests
+
+OHIF uses [netlify](netlify.com) so that pull requests are autogenerated and
+available for testing.
+
+For example, [this url][example-url] allows you to test [pull request 237, the
+request that created this FAQ entry,][pr-237] using data pulled from Amazon S3.
+
+Replacing the number 237 in the link below with your pull request number should
+let you test it as well and you can use this link for discussions on github
+without requiring reviewers to download and build your branch.
+
+```bash
+https://deploy-preview-237--ohif.netlify.com/viewer/?url=https://s3.eu-central-1.amazonaws.com/ohif-viewer/sampleDICOM.json
+```
+
+If you have made a documentation change, a link like this will let you preview
+the gitbook generated by the pull request:
+
+```bash
+https://deploy-preview-237--ohif.netlify.com/contributing.html
+```
+
+<!--
+  Links
+  -->
+
+<!-- prettier-ignore-start -->
+
+[example-url]: https://deploy-preview-237--ohif.netlify.com/viewer/?url=https://s3.eu-central-1.amazonaws.com/ohif-viewer/sampleDICOM.json
+[pr-237]: https://github.com/OHIF/Viewers/pull/237
+
+<!-- prettier-ignore-end -->
@@ -0,0 +1,4 @@
+<div style="text-align: center;">
+  <img src="/assets/img/embedded-viewer-diagram.png" alt="Embedded Viewer Diagram" style="margin: 0 auto;" />
+  <div><i>embedded viewer diagram</i></div>
+</div>
@@ -0,0 +1,4 @@
+<div style="text-align: center;">
+  <img src="/assets/img/nginx-image-archive.png" alt="request flow example" style="margin: 0 auto;" />
+  <div><i>simplified request flow diagram</i></div>
+</div>
@@ -0,0 +1,4 @@
+<div style="text-align: center;">
+  <img src="/assets/img/user-access-control-request-flow.png" alt="request flow example" style="margin: 0 auto;" />
+  <div><i>simplified request flow diagram</i></div>
+</div>
@@ -0,0 +1,210 @@
+# Deployment
+
+The OHIF Viewer can be embedded in other web applications via it's [packaged
+script source][ohif-viewer-npm], or served up as a stand-alone PWA ([progressive
+web application][pwa-url]) by building and hosting a collection of static
+assets. In either case, you will need to configure your instance of the Viewer
+so that it can connect to your data source (the database or PACS that provides
+the data your Viewer will display).
+
+## Overview
+
+Our goal is to make deployment as simple and painless as possible; however,
+there is an inherent amount of complexity in customizing, optimizing, and
+deploying web applications. If you find yourself a little lost, please don't
+hesitate to [reach out for help](/help.md)
+
+## Deployment Scenarios
+
+### Embedded Viewer
+
+The quickest and easiest way to get the OHIF Viewer up and running is to embed
+it into an existing web application. It allows us to forego a "build step", and
+add a powerful medical imaging viewer to an existing web page using only a few
+include tags.
+
+- Read more about it here: [Embedded Viewer](./recipes/embedded-viewer.md)
+- And check out our [live demo on CodeSandbox][code-sandbox]
+
+{% include "./_embedded-viewer-diagram.md" %}
+
+### Stand-alone Viewer
+
+Deploying the OHIF Viewer as a stand-alone web application provides many
+benefits, but comes at the cost of time and complexity. Some benefits include:
+
+_Today:_
+
+- Leverage [extensions](/advanced/extensions.md) to drop-in powerful new
+  features
+- Add routes and customize the viewer's workflow
+- Finer control over styling and whitelabeling
+
+_In the future:_
+
+- The ability to package the viewer for [App Store distribution][app-store]
+- Leverage `service-workers` for offline support and speed benefits from caching
+
+#### Hosted Static Assets
+
+At the end of the day, a production OHIF Viewer instance is a collection of
+HTML, CSS, JS, Font Files, and Images. We "build" those files from our
+`source code` with configuration specific to our project. We then make those
+files publicly accessible by hosting them on a Web Server.
+
+If you have not deployed a web application before, this may be a good time to
+[reach out for help](/help.md), as these steps assume prior web development and
+deployment experience.
+
+##### Part 1 - Build Production Assets
+
+"Building", or creating, the files you will need is the same regardless of the
+web host you choose. You can find detailed instructions on how to configure and
+build the OHIF Viewer in our
+["Build for Production" guide](./recipes/build-for-production.md).
+
+##### Part 2 - Host Your App
+
+There are a lot of [benefits to hosting static assets][host-static-assets] over
+dynamic content. You can find instructions on how to host your build's output
+via one of these guides:
+
+_Drag-n-drop_
+
+- [Netlify: Drop](/deployment/recipes/static-assets.md#netlify-drop)
+
+_Easy_
+
+- [Surge.sh](/deployment/recipes/static-assets.md#surgesh)
+- [GitHub Pages](/deployment/recipes/static-assets.md#github-pages)
+
+_Advanced_
+
+- [AWS S3 + Cloudfront](/deployment/recipes/static-assets.md#aws-s3--cloudfront)
+- [GCP + Cloudflare](/deployment/recipes/static-assets.md#gcp--cloudflare)
+- [Azure](/deployment/recipes/static-assets.md#azure)
+
+## Data
+
+The OHIF Viewer is able to connect to any data source that implements the [DICOM
+Web Standard][dicom-web-standard]. [DICOM Web][dicom-web] refers to RESTful
+DICOM Services -- a recently standardized set of guidelines for exchanging
+medical images and imaging metadata over the internet. Not all archives fully
+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?
+
+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.
+
+#### 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 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?
+
+> This is possible to do with the OHIF Viewer, but not as straightforward. Look
+> out for documentation on this subject in the near future.
+
+...
+
+### Securing Your Data
+
+> 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).
+
+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
+
+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.
+Please feel free to suggest or contribute your own recipes.
+
+- 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
+  -->
+
+<!-- prettier-ignore-start -->
+
+[ohif-viewer-npm]: https://www.npmjs.com/package/ohif-viewer
+[pwa-url]: https://developers.google.com/web/progressive-web-apps/
+[static-assets-url]: https://www.maxcdn.com/one/visual-glossary/static-content/
+[app-store]: https://medium.freecodecamp.org/i-built-a-pwa-and-published-it-in-3-app-stores-heres-what-i-learned-7cb3f56daf9b
+[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
+[code-flows]: https://medium.com/@darutk/diagrams-of-all-the-openid-connect-flows-6968e3990660
+[code-sandbox]: https://codesandbox.io/s/ohif-viewer-script-tag-usage-b3st9
+<!-- prettier-ignore-end -->
@@ -0,0 +1,183 @@
+# Build for Production
+
+> If you've already followed the
+> ["Getting Started" Guide](/essentials/getting-started.md), you can skip ahead
+> to [Configuration](#configuration)
+
+## Overview
+
+### Build Machine Requirements
+
+- [Node.js & NPM](https://nodejs.org/en/download/)
+- [Yarn](https://yarnpkg.com/lang/en/docs/install/)
+- [Git](https://www.atlassian.com/git/tutorials/install-git)
+
+### Getting the Code
+
+_With Git:_
+
+```bash
+# Clone the remote repository to your local machine
+git clone https://github.com/OHIF/Viewers.git
+
+# Make sure the local code reflects the `react` version of the OHIF Viewer
+git checkout react
+```
+
+More on: _[`git clone`](https://git-scm.com/docs/git-clone),
+[`git checkout`](https://git-scm.com/docs/git-checkout)_
+
+_From .zip:_
+
+[OHIF/Viewers: react.zip](https://github.com/OHIF/Viewers/archive/react.zip)
+
+### Restore Dependencies & Build
+
+Open your terminal, and navigate to the directory containing the source files.
+Next run these commands:
+
+```js
+// Restore dependencies
+yarn install
+
+// Build source code for production
+yarn run build:web
+```
+
+If everything worked as expected, you should have a new `build/` directory in
+the project's folder. It should roughly resemble the following:
+
+```bash
+build
+├── config/
+├── static/
+├── index.html
+├── manifest.json
+├── service-worker.js
+└── ...
+```
+
+By default, the build output will connect to OHIF's publicly accessible PACS. If
+this is your first time setting up the OHIF Viewer, it is recommended that you
+test with these default settings. After testing, you can find instructions on
+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
+
+#### 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.
+
+## Next Steps
+
+### Deploying Build Output
+
+_Drag-n-drop_
+
+- [Netlify: Drop](/deployment/recipes/static-assets.md#netlify-drop)
+
+_Easy_
+
+- [Surge.sh](/deployment/recipes/static-assets.md#surgesh)
+- [GitHub Pages](/deployment/recipes/static-assets.md#github-pages)
+
+_Advanced_
+
+- [AWS S3 + Cloudfront](/deployment/recipes/static-assets.md#aws-s3--cloudfront)
+- [GCP + Cloudflare](/deployment/recipes/static-assets.md#gcp--cloudflare)
+- [Azure](/deployment/recipes/static-assets.md#azure)
+
+### Testing Build Output Locally
+
+A quick way to test your build output locally is to spin up a small webserver.
+You can do this by running the following commands in the `build/` output
+directory:
+
+```js
+// Install http-server as a globally available package
+yarn global add http-server
+
+// Serve the files in our current directory
+// Accessible at: `http://localhost:8080`
+http-server
+```
+
+### Automating Builds and Deployments
+
+If you found setting up your environmnent and running all of these steps to be a
+bit tedious, then you are in good company. Thankfully, there are a large number
+of tools available to assist with automating tasks like building and deploying
+web application. For a starting point, check out this repository's own use of:
+
+- [CircleCI][circleci]: [config.yaml][circleci-config]
+- [Netlify][netlify]: [netlify.toml][netlify.toml] |
+  [generateStaticSite.sh][generatestaticsite.sh]
+- [Semantic-Release][semantic-release]: [.releaserc][releaserc]
+
+## Troubleshooting
+
+> Issues and resolutions for common GitHub issues will be summarized here
+
+...
+
+<!-- prettier-ignore-start -->
+[circleci]: https://circleci.com/gh/OHIF/Viewers
+[circleci-config]: https://github.com/OHIF/Viewers/blob/react/.circleci/config.yml
+[netlify]: https://app.netlify.com/sites/ohif/deploys
+[netlify.toml]: https://github.com/OHIF/Viewers/blob/react/netlify.toml
+[generateStaticSite.sh]: https://github.com/OHIF/Viewers/blob/react/generateStaticSite.sh
+[semantic-release]: https://semantic-release.gitbook.io/semantic-release/
+[releaserc]: https://github.com/OHIF/Viewers/blob/react/.releaserc
+<!-- prettier-ignore-end -->
@@ -0,0 +1,106 @@
+# Embedded Viewer
+
+The quickest and easiest way to get the OHIF Viewer up and running is to embed
+it into an existing web application. It allows us to forego a "build step", and
+add a powerful medical imaging viewer to an existing web page using only a few
+include tags. Here's how it works:
+
+{% include "./../_embedded-viewer-diagram.md" %}
+
+1. Create a new web page or template that includes the following external
+   dependencies:
+
+<ul>
+  <li>
+    <a href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.min.css">
+      <code>bootstrap@3.3.7</code>
+    </a>
+  </li>
+  <li>
+    <a href="https://fonts.googleapis.com/css?family=Roboto:100,300,400,500,700|Sanchez&display=swap">
+      <code>Google Fonts, Sanchez & Roboto</code>
+    </a>
+  </li>
+  <li>
+    <a href="https://unpkg.com/react@16/umd/react.production.min.js">
+      <code>react@16.8.6</code>
+    </a>
+  </li>
+  <li>
+    <a href="https://unpkg.com/react-dom@16/umd/react-dom.production.min.js">
+      <code>react-dom@16.8.6</code>
+    </a>
+  </li>
+  <li>
+    <a href="https://unpkg.com/ohif-viewer/dist/index.umd.js">
+      <code>ohif-viewer@latest</code>
+    </a>
+  </li>
+</ul>
+
+<ol start="2">
+  <li>The <a href="">WADO Image Loader Codecs and Web Worker source code</a>
+  should be accessible from your server's root</li>
+  <li>Create a JS Object to hold the OHIF Viewer's configuration. Here are some
+   example values that would allow the viewer to hit our public PACS:</li>
+</ol>
+
+```js
+// Set before importing `ohif-viewer`
+window.config = {
+  // default: '/'
+  routerBasename: '/',
+  // default: ''
+  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,
+        },
+      },
+    ],
+  },
+};
+```
+
+<ol start="5"><li>
+  Render the viewer in the web page's target <code>div</code>
+</li></ol>
+
+```js
+// Made available by the `ohif-viewer` script included in step 1
+var Viewer = window.OHIFStandaloneViewer.App;
+var app = React.createElement(Viewer, window.config, null);
+
+ReactDOM.render(app, document.getElementById('ohif-viewer-target'));
+```
+
+#### Tips & Tricks
+
+> I'm having trouble getting this to work. Where can I go for help?
+
+First, check out this fully functional [CodeSandbox][code-sandbox] example. If
+you're still having trouble, feel free to search or GitHub issues. Can't find
+anything related your problem? Create a new one.
+
+> When I include bootstrap, other styles on my page no longer work correctly.
+> What can I do?
+
+When we include `bootsrap` (and the other dependencies), they are added
+globally. This has the potential of causing conflicts with other scripts and
+styles on the page. To prevent this, `embed` the viewer in a new/empty web page.
+Have that working? Good. Now `embed` that new page using an
+[`<iframe>` element](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/iframe).
+
+This should produce the expected result while also protecting your page from any
+globally defined styles/scripts.
+
+[code-sandbox]: https://codesandbox.io/s/ohif-viewer-script-tag-usage-b3st9
Author	SHA1	Message	Date
dannyrb	7ba2916cf5	chore(release): publish %s [skip ci] - @ohif/extension-cornerstone@0.0.39-alpha.0 - @ohif/extension-dicom-html@0.0.4-alpha.0 - @ohif/extension-dicom-microscopy@0.0.9-alpha.0 - @ohif/extension-dicom-pdf@0.0.8-alpha.0 - @ohif/extension-vtk@0.1.4-alpha.0 - @ohif/core@0.11.1-alpha.0 - @ohif/i18n@0.2.3-alpha.0 - @ohif/ui@0.2.18-alpha.0 - @ohif/viewer@0.0.22-alpha.0	2019-08-05 14:45:09 -04:00
dannyrb	4736ad5620	Catch more updates	2019-08-05 14:44:45 -04:00
dannyrb	44f562e24c	Adding note	2019-08-05 14:44:20 -04:00
dannyrb	8683e1e8ff	Changing to scoped package names	2019-08-05 14:29:14 -04:00
dannyrb	f86eb5e8f2	Fix typo	2019-08-05 14:00:20 -04:00
dannyrb	64fd724455	Set default threshold	2019-08-05 13:52:02 -04:00
dannyrb	b2dfb6e0f7	Fix path; split PR and Merge unit tests into separate jobs	2019-08-05 13:04:27 -04:00
dannyrb	7c043b46b4	Try running with aliased folder	2019-08-05 12:54:23 -04:00
dannyrb	62932b3e80	Also upload `core`	2019-08-05 12:49:35 -04:00
dannyrb	7a7b2774e6	Try to see the contents of our cat'd file	2019-08-05 12:41:42 -04:00
dannyrb	1556b3bbf8	Fix filename	2019-08-05 12:37:01 -04:00
dannyrb	199db68674	Use home alias	2019-08-05 12:35:13 -04:00
dannyrb	d74b6fb826	long paths	2019-08-05 12:30:27 -04:00
dannyrb	aeac900496	Combine lines to reduce path	2019-08-05 12:26:29 -04:00
dannyrb	835fec7f32	Escape string literal	2019-08-05 12:23:10 -04:00
dannyrb	4c202ed064	tryfix syntax	2019-08-05 12:21:39 -04:00
dannyrb	e751e8fab8	Escape anchors	2019-08-05 12:12:27 -04:00
dannyrb	ae795ea97d	Combine files before upload	2019-08-05 12:08:18 -04:00
dannyrb	d90c70cab5	Fix dir	2019-08-05 11:52:35 -04:00
dannyrb	1a8fd13896	Remove individual codecov calls	2019-08-05 11:52:09 -04:00
dannyrb	0026801b62	Use full string paths	2019-08-05 11:43:03 -04:00
dannyrb	395315ea4c	Upload core and viewer	2019-08-05 11:39:10 -04:00
dannyrb	4664f673d6	Bump circleci version	2019-08-05 11:32:38 -04:00
dannyrb	a8c4534b33	Try using codecov orb	2019-08-05 11:07:14 -04:00
dannyrb	e4a3510c86	Simplify	2019-08-02 13:33:21 -04:00
dannyrb	d28f332312	Try fixing paths	2019-08-02 13:04:03 -04:00
dannyrb	37f60ba0af	Generate example for codecov issue	2019-07-19 14:54:34 -04:00
dannyrb	d64cdc429e	Shift back to calling codecov from root	2019-07-18 15:05:52 -04:00
dannyrb	e06e8304d3	Remove clear flag	2019-07-18 14:26:47 -04:00
dannyrb	0e862c69db	Fix typo	2019-07-18 13:57:14 -04:00
dannyrb	fbdb61bcb2	Use recommended flags from issue comments for codecov	2019-07-18 13:52:27 -04:00
dannyrb	3acea218fb	Trigger codecov after everything has finished running; these may not support flags	2019-07-18 13:40:31 -04:00
dannyrb	a521ce31ce	Generate separate reports	2019-07-18 13:07:29 -04:00
dannyrb	67e2fd39a3	Add projects to split by flags	2019-07-18 12:53:24 -04:00
dannyrb	253620650b	Try once relying on codecov yaml to split w/ flags	2019-07-18 12:43:03 -04:00
dannyrb	31357ea9b5	Run and report individually and in parallel	2019-07-18 10:26:33 -04:00
dannyrb	b8baae7c25	Get all platform unit tests to run	2019-07-17 14:57:50 -04:00
dannyrb	5544c57c37	Use cpx so our copying finishes?	2019-07-16 14:58:40 -04:00
dannyrb	6b523cb50d	Add codecov flags	2019-07-16 14:51:04 -04:00
dannyrb	579c2b41d1	Set path and enable workspaces	2019-07-16 14:27:22 -04:00
dannyrb	9449ae4314	Try alternative jest transform	2019-07-16 14:23:41 -04:00
dannyrb	4386b5c960	Run version command instead of calling node directly	2019-07-16 14:14:34 -04:00
dannyrb	fe3ee3010f	Try alternative jest-canvas-mock location and version file syntax	2019-07-16 14:06:02 -04:00
dannyrb	ee5530183e	Lower version to match circleci image	2019-07-16 13:43:55 -04:00
dannyrb	413214786d	Change copy syntax; try running tests on viewers from root for circleci	2019-07-16 13:31:52 -04:00
dannyrb	0b62b720c5	Attempt to fix ticks/escapes	2019-07-16 13:24:46 -04:00
dannyrb	c3fead1ca9	We need to pull cornerstone-wado-image-loader files from hoisted node_modules	2019-07-16 13:11:16 -04:00
dannyrb	bc8d505a0a	We may have figured it out johnny, boy	2019-07-16 12:57:37 -04:00
dannyrb	ab4067144f	and again	2019-07-16 12:50:33 -04:00
dannyrb	575d11ac5b	Annd let's try again	2019-07-16 12:42:40 -04:00
dannyrb	aa53d3258c	Try bash -l instead of exec bash	2019-07-16 12:19:51 -04:00
dannyrb	dc672bf38d	Try swapping bash with a new shell	2019-07-16 12:11:21 -04:00
dannyrb	65a855d99b	try again to set bin path	2019-07-16 11:12:19 -04:00
dannyrb	99c1d0220d	Follow deploy log output advice	2019-07-16 10:43:01 -04:00
dannyrb	dab0b5e0e3	More agressive with modifying PATH	2019-07-16 10:35:06 -04:00
dannyrb	ea3f7d5657	Export node_modules path	2019-07-16 10:01:33 -04:00
dannyrb	3c812792bb	Try to use global gitbook-cli	2019-07-16 09:55:34 -04:00
dannyrb	ff21408440	push workspace enabled to initial command; remove second yarn install; use npx to call gitbook cli commands	2019-07-16 09:42:43 -04:00
dannyrb	fd720bd4d7	Attempt to fix deploy preview build	2019-07-16 09:32:14 -04:00
dannyrb	2279e555a3	First attempt at a netlify deploy preview	2019-07-16 09:24:24 -04:00
dannyrb	91ee615aee	Shift links to bottom of doc	2019-07-15 15:56:07 -04:00
dannyrb	f8d9bbef8a	Rename example extension folder	2019-07-15 15:51:36 -04:00
dannyrb	4fcf544abe	Begin providing basic readme info	2019-07-15 15:51:24 -04:00
dannyrb	2ba0e95fe8	Specify additional lerna config props	2019-07-15 15:51:10 -04:00
dannyrb	91564bfa06	Shift docs to root	2019-07-15 15:50:47 -04:00
dannyrb	83e627e5c9	Fix ESM symlink build for Viewers	2019-07-15 13:03:29 -04:00
dannyrb	2fbbb4a8e2	Push changes up to switch PCs	2019-07-11 13:12:37 -04:00
dannyrb	c05058a0f5	Better entrypoint for extensions	2019-07-09 12:56:08 -04:00
dannyrb	2429294dda	Provide WebPack build options for microscopy, vtk, and ui	2019-07-09 12:39:15 -04:00
dannyrb	2234869b11	Add Webpack Stylus loader	2019-07-09 12:38:12 -04:00
dannyrb	96686850cb	Target for UMD bundle	2019-07-09 12:37:58 -04:00
dannyrb	35dc82e120	Resolve viewer's modules	2019-07-09 12:37:02 -04:00
dannyrb	f5d6674b62	Make it possible to pass in extensions as App props	2019-07-08 10:18:03 -04:00
dannyrb	f3009c7a45	Consolidate how/where we specify file/module type entrypoints	2019-07-08 09:38:16 -04:00
dannyrb	e8969fba11	Split packages into platform and extensions	2019-07-08 00:41:25 -04:00
dannyrb	f175d4b96b	Commit changes before a long weekend	2019-07-05 22:58:25 -04:00
dannyrb	e250ac0c50	Begin updating dependent libraries to use sync'd webpack builds w/ watches	2019-07-05 13:28:49 -04:00
dannyrb	3e1e456cc2	Move @babel dependencies up to workspace root	2019-07-04 20:35:30 -04:00
dannyrb	e58ba39a60	more shifting	2019-07-04 16:19:28 -04:00
dannyrb	b73ea99971	init	2019-07-04 16:12:43 -04:00
				`@@ -1 +0,0 @@`
				`custom: https://giving.massgeneral.org/ohif`
				`@@ -1 +0,0 @@`
				See our contributing guidelines at [`https://docs.ohif.org`](https://docs.ohif.org/development/contributing.html)