Merge pull request #776 from simon04/get-started-guides

List get-started content under guides

antwar.config.js

@@ -38,16 +38,13 @@ module.exports = {
       }
     ),
 
-    'get-started': section(
-      'Get-Started',
-      function() {
-        return require.context(
-          'json-loader!yaml-frontmatter-loader!./content/get-started',
-          false,
-          /^\.\/.*\.md$/
-        )
+    'get-started': {
+      redirects: {
+        '': '/guides/get-started',
+        'install-webpack': '/guides/installation',
+        'why-webpack': '/guides/why-webpack',
       }
-    ),
+    },
 
     concepts: section(
       'Concepts',

components/footer/footer.jsx

@@ -10,10 +10,10 @@ export default (props) => {
     <footer className="footer">
       <Container className="footer__inner">
         <section className="footer__left">
-          <Link className="footer__link" to="/get-started">Get Started</Link>
+          <Link className="footer__link" to="/guides/get-started">Get Started</Link>
           <Link className="footer__link" to="/organization">Organization</Link>
           <Link className="footer__link" to="/contribute">Contribute</Link>
-          <Link className="footer__link" to="/get-started/why-webpack#comparison">Comparison</Link>
+          <Link className="footer__link" to="/guides/why-webpack#comparison">Comparison</Link>
         </section>
 
         <section className="footer__middle">

components/sidebar/sidebar.jsx

@@ -62,11 +62,6 @@ export default class Sidebar extends Component {
             currentPage= { currentPage }
           />
 
-          { isGuides ? (
-            <SidebarItem
-              url={ `/get-started` }
-              title="Get Started" />
-          ) : null }
           {
             pages.map(({ url, title, anchors }, i) =>
               <SidebarItem

content/concepts/entry-points.md

@@ -6,7 +6,7 @@ contributors:
   - chrisVillanueva
 ---
 
-Like we mentioned in the [introduction](/get-started/#using-webpack-with-a-config), there are multiple ways to define the `entry` property in your webpack configuration. We will show you the ways you **can** configure the `entry` property, in addition to explaining why it may be useful to you.
+Like we mentioned in the [introduction](/guides/get-started/#using-webpack-with-a-config), there are multiple ways to define the `entry` property in your webpack configuration. We will show you the ways you **can** configure the `entry` property, in addition to explaining why it may be useful to you.
 
 ## Single Entry (Shorthand) Syntax
 

content/get-started/index.md → content/guides/get-started.md

@@ -1,6 +1,6 @@
 ---
 title: Getting Started
-sort: 3
+sort: 0
 contributors:
   - bebraw
   - varunjayaraman
@@ -11,7 +11,7 @@ contributors:
 ---
 
 webpack is a tool to build JavaScript modules in your application. To start using `webpack` from its [cli](/api/cli) or [api](/api/node), follow the [Installation instructions](/guides/installation).
-webpack simplifies your workflow by quickly constructing a dependency graph of your application and bundling them in the right order. webpack can be configured to customise optimisations to your code, to split vendor/css/js code for production, run a development server that hot-reloads your code without page refresh and many such cool features. Learn more about [why you should use webpack](/get-started/why-webpack).
+webpack simplifies your workflow by quickly constructing a dependency graph of your application and bundling them in the right order. webpack can be configured to customise optimisations to your code, to split vendor/css/js code for production, run a development server that hot-reloads your code without page refresh and many such cool features. Learn more about [why you should use webpack](/guides/why-webpack).
 
 ## Creating a bundle
 

content/index.md

@@ -65,4 +65,4 @@ Then run `webpack` on the command-line to create `bundle.js`.
 </div>
 
 ## It's that simple.
-## [Get Started](/get-started)
+## [Get Started](/guides/get-started)