Merge branch 'master' into img-inline-doc

Author: hansl

docs/documentation/build.md

@@ -89,6 +89,20 @@ If a resource is less than 10kb it will also be inlined.
 
 You'll see these resources be outputted and fingerprinted at the root of `dist/`.
 
+### Service Worker
+
+There is experimental service worker support for production builds available in the CLI.
+To enable it, run the following commands:
+```
+npm install @angular/service-worker --save
+ng set apps.0.serviceWorker=true
+```
+
+On `--prod` builds a service worker manifest will be created and loaded automatically.
+Remember to disable the service worker while developing to avoid stale code.
+
+Note: service worker support is experimental and subject to change.
+
 ## Options
 <details>
   <summary>aot</summary>

docs/documentation/stories.md

@@ -25,3 +25,4 @@
  - [Code Coverage](stories/code-coverage)
  - [Application Environments](stories/application-environments)
  - [Autoprefixer Configuration](stories/autoprefixer)
+ - [Deploy to GitHub Pages](stories/githug-pages)

docs/documentation/stories/github-pages.md

@@ -0,0 +1,21 @@
+# Deploy to GitHub Pages
+
+A simple way to deploy your Angular app is to use
+[GitHub Pages](https://help.github.com/articles/what-is-github-pages/).
+
+The first step is to [create a GitHub account](https://github.com/join), and then
+[create a repository](https://help.github.com/articles/create-a-repo/) for your project.
+Make a note of the user name and project name in GitHub.
+
+Then all you need to do is run `ng build --prod --output-path docs --base-href PROJECT_NAME`, where
+`PROJECT_NAME` is the name of your project in GitHub.
+Make a copy of `dist/index.html` and name it `dist/404.html`.
+
+Commit your changes and push. On the GitHub project page, configure it to
+[publish from the docs folder](https://help.github.com/articles/configuring-a-publishing-source-for-github-pages/#publishing-your-github-pages-site-from-a-docs-folder-on-your-master-branch).
+
+And that's all you need to do! Now you can see your page at
+`https://USER_NAME.github.io/PROJECT_NAME/`.
+
+You can also use [angular-cli-ghpages](https://github.com/angular-buch/angular-cli-ghpages), a full
+featured package that does this all this for you and has extra functionality.

docs/documentation/stories/global-scripts.md

@@ -21,3 +21,23 @@ You can also rename the output and lazy load it by using the object format:
   { "input": "pre-rename-script.js", "output": "renamed-script" },
 ],
 ```
+
+## Using global libraries inside your app
+
+Once you import a library via the scripts array, you should **not** import it via a import statement
+in your TypeScript code (e.g. `import * as $ from 'jquery';`).
+If you do that, you'll end up with two different copies of the library: one imported as a
+global library, and one imported as a module.
+
+This is especially bad for libraries with plugins, like JQuery, because each copy will have
+different plugins.
+
+Instead, download typings for your library (`npm install @types/jquery`) which will give you
+access to the global variables exposed by that library.
+
+If the global library you need to use does not have global typings, you can also declare them
+manually in `src/typings.d.ts` as `any`:
+
+```
+declare var libraryName: any;
+```