docs: update getting started w/ webpack CLI (#1237)

Author: davideast

GETTING_STARTED.md

@@ -1,127 +1,48 @@
-This guide will take you through building your first project with Angular Material 2.  We'll be using 
-the Angular CLI, but you can also accomplish this with other build tools like Webpack or Gulp.
+Get started with Angular Material 2 using the Angular CLI.
 
-### Globally install the CLI
+## Install the CLI
 
  ```bash
- npm install -g angular-cli
+ npm install -g angular-cli@webpack
  ```
 
-### Create a new project
+## Create a new project
 
  ```bash
  ng new my-project
  ```
- 
-This will create a starter repo under the name you specified with the files and folders 
-you'd need for any Angular 2 app: a root component, a main.ts to bootstrap your root component, an 
-index.html, etc.  It also sets up build rules to transpile your Typescript into Javascript and sets 
-some initial config for the SystemJS module loader.  
- 
-### Install Angular Material 2 components 
 
-Now that your project has been created, you can install any Angular Material 2 components you'd like 
-to use through npm. You can see our [list of published packages here](https://www.npmjs.com/~angular2-material).
+The new command creates a project with a build system for your Angular app.
+
+## Install Angular Material 2 components 
+
+Angular Material 2 components are set up in separate modules. This allows you to only pull into your app what you need, reducing the size of your app. Components are installed individually. You can see our [list of published packages here](https://www.npmjs.com/~angular2-material).
 
 Note that only packages published under the `@latest` npm tag are officially released.
 
 ```bash
 npm install --save @angular2-material/core @angular2-material/button @angular2-material/card
 ```
-(the core module is required as a peer dependency of other components)
-
-### Add components to vendor bundle
-
-Next, you'll need to build the `@angular2-material` folder out of `node_modules` and into 
-`dist/vendor`, so that it's served with the rest of the vendor files. You can easily configure this by 
-editing the `angular-cli-build.js` file in the root of your project.  Simply add a glob for all 
-@angular2-material files to the end of the existing `vendorNpmFiles` array.
-
-**angular-cli-build.js**
-```js
-module.exports = function(defaults) {
-  return new Angular2App(defaults, {
-    vendorNpmFiles: [
-      'systemjs/dist/system-polyfills.js',
-      'systemjs/dist/system.src.js',
-      'zone.js/dist/**/*.+(js|js.map)',
-      'es6-shim/es6-shim.js',
-      'reflect-metadata/**/*.+(js|js.map)',
-      'rxjs/**/*.+(js|js.map)',
-      '@angular/**/*.+(js|js.map)',
-      '@angular2-material/**/*'
-    ]
-  });
-};
-```
-
-You can see an example `angular-cli-build.js` file [here](https://github.com/kara/puppy-love/blob/master/angular-cli-build.js).
-
-### Configure SystemJS
-
-First, you need to let SystemJS know where to look when you import `@angular2-material`. You can do 
-this by adding the path to the Material folder to the `maps` object. 
-
-**src/system-config.ts**
-```ts
-const map: any = {
-  '@angular2-material': 'vendor/@angular2-material'
-};
-```
-
-This says something like "when you look for an @angular2-material import, look inside the vendor 
-folder" (the base folder will already be `dist`).
-
-Next, you need to let SystemJS know how to process the new modules.  Specifically, you need to point 
-to the main files of each of the packages. You can also set the format to `cjs` and the 
-defaultExtension to `js`, but it's not required.
-
-**src/system-config.ts**
-```ts
-const packages:any = {};
-
-// put the names of any of your Material components here
-const materialPkgs:string[] = [
-  'core',
-  'button',
-  'card',
-];
-
-materialPkgs.forEach((pkg) => {
-  packages[`@angular2-material/${pkg}`] = {main: `${pkg}.js`};
-});
-```
-
-You can see an example `system-config.ts` [here](https://github.com/kara/puppy-love-io/blob/master/src/system-config.ts).
 
-### Import and use the components
+> The core module is required as a peer dependency of other components
 
-Now you should be able to import the components normally wherever you'd like to use them.
+## Add components to your app module
+Now you should be able to import the components normally wherever you'd like to use them. Import the components in your application module:
 
-**src/app/my-project.component.ts**
+**src/app/app.module.ts**
 ```ts
-import { MdCardModule } from '@angular2-material/card';
 import { MdButtonModule } from '@angular2-material/button';
-```
-
-Import the components in your application module:
-
-**my-app-module.ts**
-```ts
+import { MdCardModule } from '@angular2-material/card';
+// other imports 
 @NgModule({
   imports: [MdButtonModule, MdCardModule],
   ...
 })
 ```
 
-### Sample Angular Material 2 projects
-
+### Sample Angular Material 2 project
 - [Material 2 Sample App](https://github.com/jelbourn/material2-app)
 
-(the following are slightly out of date now)
-- [Puppy Love (ng-conf 2016)](https://github.com/kara/puppy-love) - see live demo [here](https://youtu.be/rRiV_b3WsoY?t=4m20s) 
-- [Puppy Love Mobile (Google IO 2016)](https://github.com/kara/puppy-love-io)
-
 
 ### Additional setup for `md-menu` and `md-tooltip`:
 For alpha.7, you need to include the overlay styles in your app via a `link` element. This will
@@ -132,7 +53,6 @@ look something like
 
 In future releases, all of the core styles will be combined into a single distributed css file.
 
-
 ### Additional setup for `md-slide-toggle` and `md-slider`:
 The slide-toggle and slider components have a dependency on [HammerJS](http://hammerjs.github.io/).
 1) Add HammerJS to your application via [npm](https://www.npmjs.com/package/hammerjs), a CDN