feat(segmentation mode): Add create, and export SEG with Brushes (#3632)

platform/docs/docs/deployment/build-for-production.md

@@ -116,6 +116,26 @@ In the video below notice that there is `platform/viewer` which has been renamed
     <iframe src="https://player.vimeo.com/video/551957266?badge=0&amp;autopause=0&amp;player_id=0&amp;app_id=58479"  frameBorder="0" allow="autoplay; fullscreen; picture-in-picture" allowFullScreen style= {{ position:"absolute",top:0,left:0,width:"100%",height:"100%"}} title="measurement-report"></iframe>
 </div>
 
+### Build for non-root path
+
+If you would like to access the viewer from a non-root path (e.g., `/my-awesome-viewer` instead of `/`),
+You can achieve so by using the `PUBLIC_URL` environment variable AND the `routerBasename` configuration option.
+
+1. use a config (e.g. config/myConfig.js) file that is using the `routerBasename` of your choice `/my-awesome-viewer` (note there is only one / - it is not /my-awesome-viewer/).
+2. build the viewer with `PUBLIC_URL=/my-awesome-viewer/ APP_CONFIG=config/myConfig.js yarn build` (note there are two / - it is not /my-awesome-viewer).
+
+
+:::tip
+The PUBLIC_URL tells the application where to find the static assets and the routerBasename will tell the application how to handle the routes
+:::
+
+:::tip
+Testing, you can use `npx http-server` to serve the files in the generated `dist` folder and access the viewer from `http://localhost:8080/my-awesome-viewer`. To achieve
+so, you should first rename the `dist` folder to `my-awesome-viewer` and then change the working directory
+to the `platform/app` folder and run `npx http-server ./`. Then on the browser, you can access the viewer from `http://localhost:8080/my-awesome-viewer`
+:::
+
+
 ### Automating Builds and Deployments
 
 If you found setting up your environment and running all of these steps to be a

platform/docs/docs/deployment/iframe.md

@@ -28,7 +28,7 @@ It is also required that the PUBLIC_URL environment variable is set to the same
 `<iframe src="./ohif" />` (which means there is a `ohif` folder containing the build in your main app), then you need to:
 
 1. use a config (e.g. config/myConfig.js) file that is using the `routerBasename` of `/ohif` (note the one / - it is not /ohif/).
-2. build the viewer with `PUBLIC_URL=./ohif/ APP_CONFIG=config/myConfig.js yarn build` (note the one / - it is not /ohif/).
+2. build the viewer with `PUBLIC_URL=/ohif/ APP_CONFIG=config/myConfig.js yarn build` (note the two / - it is not /ohif).
 
 :::tip
 Check to make sure the `app-config.js` in the build is reflecting the correct routerBasename.