[fix] Updating all how-to/** links to guides/**

Author: skipjack

content/concepts/entry-points.md

@@ -73,7 +73,7 @@ const config = {
 
 **What does this do?** At face value this tells webpack to create dependency graphs starting at both `app.js` and `vendors.js`. These graphs are completely separate and independent of each other (there will be a webpack bootstrap in each bundle). This is commonly seen with single page applications which have only one entry point (excluding vendors).
 
-**Why?** This setup allows you to leverage `CommonsChunkPlugin` and extract any vendor references from your app bundle into your vendor bundle, replacing them with `__webpack_require__()` calls. If there is no vendor code in your application bundle, then you can achieve a common pattern in webpack known as [long-term vendor-caching](/how-to/cache).
+**Why?** This setup allows you to leverage `CommonsChunkPlugin` and extract any vendor references from your app bundle into your vendor bundle, replacing them with `__webpack_require__()` calls. If there is no vendor code in your application bundle, then you can achieve a common pattern in webpack known as [long-term vendor-caching](/guides/caching).
 
 ?> Consider removing this scenario in favor of the DllPlugin, which provides a better vendor-splitting.
 

content/configuration/dev-server.md

@@ -8,7 +8,7 @@ contributors:
   - charlespwd
 ---
 
-webpack-dev-server can be used to quickly develop an application. See the ["How to Develop?"](/how-to/develop) to get started.
+webpack-dev-server can be used to quickly develop an application. See the ["How to Develop?"](/guides/development) to get started.
 
 This page describes the options that effect the behavior of webpack-dev-server (short: dev-server).
 

content/configuration/externals.md

@@ -98,4 +98,4 @@ This syntax is used to describe all the possible ways that an external library c
 
 ?> TODO - I think its overkill to list externals as regex.
 
-For more information on how to use this configuration, please refer to the article on [how to author a library](/how-to/author-libraries).
+For more information on how to use this configuration, please refer to the article on [how to author a library](/guides/author-libraries).

content/configuration/index.md

@@ -37,7 +37,7 @@ T> Notice that throughout the configuration we use Node's built-in [path module]
 
     <details><summary>[filename](/configuration/output#output-filename): "bundle.js", // string</summary>
     [filename](/configuration/output#output-filename): "[name].js", // for multiple entry points
-    [filename](/configuration/output#output-filename): "[chunkhash].js", // for [long term caching](/how-to/cache)
+    [filename](/configuration/output#output-filename): "[chunkhash].js", // for [long term caching](/guides/caching)
     </details>
     // the filename template for entry chunks
 
@@ -67,7 +67,7 @@ T> Notice that throughout the configuration we use Node's built-in [path module]
     // include useful path info about modules, exports, requests, etc. into the generated code
 
     [chunkFilename](/configuration/output#output-chunkfilename): "[id].js",
-    [chunkFilename](/configuration/output#output-chunkfilename): "[chunkhash].js", // for [long term caching](/how-to/cache)
+    [chunkFilename](/configuration/output#output-chunkfilename): "[chunkhash].js", // for [long term caching](/guides/caching)
     // the filename template for additional chunks
 
     [jsonpFunction](/configuration/output#output-jsonpfunction): "myWebpackJsonp", // string
@@ -142,7 +142,7 @@ T> Notice that throughout the configuration we use Node's built-in [path module]
         [loader](/configuration/module#rule-loader): "babel-loader",
         // the loader which should be applied, it'll be resolve relative to the context
         // -loader suffix is no longer optional in Webpack 2 for clarity reasons
-        // see [webpack 1 upgrade guide](/how-to/upgrade-from-webpack-1)
+        // see [webpack 1 upgrade guide](/guides/migrating)
 
         [options](/configuration/module#rule-options-rule-query): {
           presets: ["es2015"]

content/configuration/output.md

@@ -132,7 +132,7 @@ Using hashes based on each chunks' content:
 filename: "[chunkhash].bundle.js"
 ```
 
-Make sure the read the [Caching guide](/how-to/cache) for details. There are more steps involved than just setting this option.
+Make sure the read the [Caching guide](/guides/caching) for details. There are more steps involved than just setting this option.
 
 The default value is `"[name].js"`.
 
@@ -199,7 +199,7 @@ If using the [`output.library`](#output-library) option, the library name is aut
 
 `string`
 
-Read the [library guide](/how-to/author-libraries) for details.
+Read the [library guide](/guides/author-libraries) for details.
 
 Use `library`, and `libraryTarget` below, when writing a JavaScript library that should export values, which can be used by other code depending on it. Pass a string with the name of the library:
 
@@ -216,7 +216,7 @@ Note that `output.libraryTarget` defaults to `var`. This means if only `output.l
 
 `string`
 
-Read the [library guide](/how-to/author-libraries) for details.
+Read the [library guide](/guides/author-libraries) for details.
 
 Configure how the library will be exposed. Any one of the following options can be used: (the examples assume `library: "MyLibrary"`)
 
@@ -244,7 +244,7 @@ The output directory as an **absolute** path.
 path: path.resolve(__dirname, 'dist/assets')
 ```
 
-Note that `[hash]` in this parameter will be replaced with an hash of the compilation. See the [Caching guide](/how-to/cache) for details.
+Note that `[hash]` in this parameter will be replaced with an hash of the compilation. See the [Caching guide](/guides/caching) for details.
 
 
 ## `output.pathinfo`
@@ -302,7 +302,7 @@ background-image: url(/assets/spinner.gif);
 
 The webpack-dev-server also takes a hint from `publicPath`, using it to determine where to serve the output files from.
 
-Note that `[hash]` in this parameter will be replaced with an hash of the compilation. See the [Caching guide](/how-to/cache) for details.
+Note that `[hash]` in this parameter will be replaced with an hash of the compilation. See the [Caching guide](/guides/caching) for details.
 
 Examples:
 

content/guides/author-libraries.md

@@ -178,7 +178,7 @@ If `library` property is set and `libraryTarget` is set to be `var` by default,
 
 ### Final Steps
 
-[Tweak your production build using webpack](/how-to/generate-production-build).
+[Tweak your production build using webpack](/guides/production-build).
 
 Add the path to your generated bundle as the package's main file in `package.json`
 

content/guides/code-splitting.md

@@ -17,7 +17,7 @@ There are mainly two kind of code-splits that need to be accomplished with `webp
 ### Code splitting with `require.ensure()`
 
 `require.ensure()` is the CommonJS way of including assets asynchronously. By adding `require.ensure([<fileurl>])`, we can define a split point in the code. webpack can then create a separate bundle of all the code inside this split point.
-Learn [how to split your code using `require.ensure()`](/how-to/code-splitting/splitting-require)
+Learn [how to split code](/guides/code-splitting-require) using `require.ensure()`.
 
 ?> Document `System.import()`
 
@@ -26,10 +26,10 @@ Learn [how to split your code using `require.ensure()`](/how-to/code-splitting/s
 ### CSS splitting
 
 An application owner would want to split all the css into a separate bundle. This enhances cacheability of the resource bundle and also allows the browser to parallely load the bundle which makes for a solid performance improvement.
-Learn [how to split your css using Extract-Text-Webpack-Plugin](/how-to/code-splitting/splitting-css)
+Learn [how to split css](/guides/code-splitting-css) using the ExtractTextWebpackPlugin.
 
 ### Vendor code splitting
 
 A typical application uses third party libraries for framework/functionality needs. Particular versions of these libraries are used and code here does not change often. However, the application code changes frequently. Bundling application code with third party code would be inefficient. This is because the browser can cache asset files based on the cache header. To take advantage of this, we want to keep the hash of the vendor files constant regardless of application code changes. We can do this only when we separate the bundles for vendor and application code.
 
-Learn [how to split your vendor code using CommonsChunkPlugin](/how-to/code-splitting/splitting-vendor)
+Learn [how to split vendor/library](/guides/code-splitting-libraries) code using the CommonsChunkPlugin.

content/guides/development.md

@@ -86,7 +86,7 @@ The command above should automatically open your browser on `http://localhost:80
 
 Make a change in one of your files and hit save. You should see that the console is recompiling. After that's done, the page should be refreshed. If nothing happens in the console, you may need to fiddle with [`watchOptions`](/configuration/dev-server#devserver-watchoptions-).
 
-Now you have live reloading working, you can take it even a step further: Hot Module Replacement. This is an interface that makes it possible to swap modules **without a page refresh**. Find out how to [configure HMR](/how-to/hot-module-reload).
+Now you have live reloading working, you can take it even a step further: Hot Module Replacement. This is an interface that makes it possible to swap modules **without a page refresh**. Find out how to [configure HMR](/guides/hmr).
 
 By default **inline mode** is used. This mode injects the client - needed for live reloading and showing build errors - in your bundle. With inline mode you will get build errors and warnings in your DevTools console.