For step 1, point users to the "build for production" guide

This commit is contained in:
dannyrb 2019-04-29 23:11:04 -04:00
parent 6e058ef312
commit 70a9b9ca06

View File

@ -48,10 +48,10 @@ _In the future:_
#### Hosted Static Assets #### Hosted Static Assets
At the end of the day, the OHIF Viewer is a collection of HTML, CSS, JS, Font At the end of the day, a production OHIF Viewer instance is a collection of
Files, and Images. We "build" those files from our `source code` with HTML, CSS, JS, Font Files, and Images. We "build" those files from our
configuration specific to our project. We then make those files publicly `source code` with configuration specific to our project. We then make those
accessible by hosting them on a Web Server. 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 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 [reach out for help](/help.md), as these steps assume prior web development and
@ -59,8 +59,10 @@ deployment experience.
##### Part 1 - Build Production Assets ##### Part 1 - Build Production Assets
"Building", or creating, the files you will need to host is the same regardless "Building", or creating, the files you will need is the same regardless of the
of the host you choose. [] web host you choose. You can find detailed instructions on how to configure and
build the OHIF Viewer in our
["Build for Production" guide](./build-for-production.md).
##### Part 2 - Host Your App ##### Part 2 - Host Your App