Begin detailing steps to build for production (host static assets)

docs/latest/deployment/index.md

@@ -48,8 +48,23 @@ _In the future:_
 
 #### Hosted Static Assets
 
-_blocking:_ Generate files from `npm script` that we can host. IE. production
-ready build output
+At the end of the day, the OHIF Viewer 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 to host is the same regardless
+of the host you choose. []
+
+##### Part 2 - Host Your App
+
+There are a lot of [benefits to hosting static assets][host-static-assets]
 
 - AWS S3 + Cloudfront
 - GCP + Cloudflare
@@ -115,5 +130,6 @@ support it yet, but it is gaining wider adoption.
 [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/
 
 <!-- prettier-ignore-end -->