chore(build): try to build demo and docs (#3434)

platform/docs/docs/development/architecture.md

@@ -50,7 +50,7 @@ you'll see the following:
 OHIF v3 is composed of the following components, described in detail in further
 sections:
 
-- `@ohif/viewer`: The core framework that controls extension registration, mode
+- `@ohif/app`: The core framework that controls extension registration, mode
   composition and routing.
 - `@ohif/core`: A library of useful and reusable medical imaging functionality
   for the web.
@@ -58,7 +58,7 @@ sections:
   with.
 - `Extensions`: A set of building blocks for building applications. The OHIF org
   maintains a few core libraries.
-- `Modes`: Configuration objects that tell @ohif/viewer how to compose
+- `Modes`: Configuration objects that tell @ohif/app how to compose
   extensions to build applications on different routes of the platform.
 
 ## Extensions
@@ -110,7 +110,7 @@ certain workflows.
 To summarize the difference between extensions and modes in `OHIF-v3` and
 extensions in `OHIF-v2`
 
-> - `Modes` are configuration objects that tell _@ohif/viewer_ how to compose
+> - `Modes` are configuration objects that tell _@ohif/app_ how to compose
 >   extensions to build applications on different routes of the platform.
 > - In v2 extensions are “plugins” that add functionality to a core viewer.
 > - In v3 extensions are building blocks that a mode uses to build an entire
@@ -120,7 +120,7 @@ extensions in `OHIF-v2`
 
 ## Platform
 
-### `@ohif/viewer`
+### `@ohif/app`
 
 This library is the core library which consumes modes and extensions and builds
 an application. Extensions can be passed in as app configuration and will be
@@ -195,7 +195,7 @@ new mode as well.
 <!-- prettier-ignore-start -->
 [monorepo]: https://github.com/OHIF/Viewers/issues/768
 [viewers-project]: https://github.com/OHIF/Viewers
-[viewer-npm]: https://www.npmjs.com/package/@ohif/viewer
+[viewer-npm]: https://www.npmjs.com/package/@ohif/app
 [pwa]: https://developers.google.com/web/progressive-web-apps/
 [configuration]: ../configuration/index.md
 [extensions]: ../platform/extensions/index.md

platform/docs/docs/development/getting-started.md

@@ -24,10 +24,6 @@ up-to-date with the upstream (original) repository. This is called a "Triangular
 Workflow" and is common for Open Source projects. The GitHub blog has a [good
 graphic that illustrates this setup][triangular-workflow].
 
-### `v3-stable` branch
-Currently the stable branch for OHIF-v3 is `v3-stable`. Once the v3-stable branch has
-feature parity with the master branch, `v3-stable` will be pushed to the master branch.
-You can read more about the roadmap timeline [here](https://ohif.org/roadmap).
 
 ### Private
 
@@ -57,9 +53,6 @@ Navigate to the root of the project's directory in your terminal and run the
 following commands:
 
 ```bash
-# Switch to the v3 branch
-git switch v3-stable
-
 # Restore dependencies
 yarn install
 
@@ -70,10 +63,10 @@ yarn run dev
 You should see the following output:
 
 ```bash
-@ohif/viewer: i ｢wds｣: Project is running at http://localhost:3000/
-@ohif/viewer: i ｢wds｣: webpack output is served from /
-@ohif/viewer: i ｢wds｣: Content not from webpack is served from D:\code\ohif\Viewers\platform\viewer
-@ohif/viewer: i ｢wds｣: 404s will fallback to /index.html
+@ohif/app: i ｢wds｣: Project is running at http://localhost:3000/
+@ohif/app: i ｢wds｣: webpack output is served from /
+@ohif/app: i ｢wds｣: Content not from webpack is served from D:\code\ohif\Viewers\platform\viewer
+@ohif/app: i ｢wds｣: 404s will fallback to /index.html
 
 # And a list of all generated files
 ```
@@ -111,6 +104,6 @@ yarn run build
 [add-remote-repo]: https://help.github.com/en/articles/fork-a-repo#step-3-configure-git-to-sync-your-fork-with-the-original-spoon-knife-repository
 [sync-changes]: https://help.github.com/en/articles/syncing-a-fork
 [triangular-workflow]: https://github.blog/2015-07-29-git-2-5-including-multiple-worktrees-and-triangular-workflows/#improved-support-for-triangular-workflows
-[ohif-viewers-repo]: https://github.com/OHIF/Viewers/tree/v3-stable
+[ohif-viewers-repo]: https://github.com/OHIF/Viewers/
 [ohif-viewers]: https://github.com/OHIF/Viewers
 <!-- prettier-ignore-end -->

platform/docs/docs/development/ohif-cli.md

@@ -286,7 +286,7 @@ To make all the above commands work, we have created a new file called `PluginCo
 information needed to run the commands. You **don't need to (and should not)**
 edit/update/modify this file as it is automatically generated by the CLI. You
 can take a look at what this file contains by going to
-`platform/viewer/PluginConfig.json` in your project's root directory. In short,
+`platform/app/PluginConfig.json` in your project's root directory. In short,
 this file tracks and stores all the extensions/modes and the their version that
 are currently being used by the viewer.
 
@@ -305,4 +305,4 @@ export NPM_TOKEN=<your readonly token>
 The ohif-cli will add the path to the external dependencies to the webpack config,
 so that you can install them in your project and use them in your custom
 extensions and modes. To achieve this ohif-cli will update the webpack.pwa.js
-file in the platform/viewer directory.
+file in the platform/app directory.