Fix broken links (gatsbyjs#1205)

CONTRIBUTING.md

@@ -32,7 +32,7 @@ The usual contributing steps are:
 * For each of your Gatsby test sites, run the `gatsby-dev` command there to copy
   the built files from your cloned copy of Gatsby. It'll watch for your changes
   to Gatsby packages and copy them into the site. For more detailed
-  instructions see the [gatsby-dev-cli README](/packages/gatsby-dev-cli/)
+  instructions see the [gatsby-dev-cli README](/docs/packages/gatsby-dev-cli/)
 * Add tests and code for your changes.
 * Once you're done, make sure all tests still pass: `npm test`
 * Commit and push to your fork.

docs/blog/gatsby-first-beta-release.md

@@ -68,36 +68,36 @@ It'd be impossible to write open source code without the generous support
 of these infrastructure providers.
 
 * [Netlify](https://www.netlify.com/) *Awesome static site continuous delivery & hosting*
-* [Travis CI](travis-ci.org) *Test runner in the cloud*
+* [Travis CI](https://travis-ci.org) *Test runner in the cloud*
 * [Appveyor](https://www.appveyor.com/) *Windows test runner in the cloud*
 
 ## Changelog since 1.0.0-alpha.20
 
 ### Added
-* Allow for gatsby-remark-smartypants options [#1166](https://github.com/gatsbyjs/pull/1166) @mitchejj
-* New design (for gatsbyjs.org) + new home page [#1170](https://github.com/gatsbyjs/pull/1170) @kyleamathews
-* Add ability to locally define plugins [#1126](https://github.com/gatsbyjs/pull/1126) @0x80
-* Add rough draft for docs for creating source plugins [#1159](https://github.com/gatsbyjs/pull/1159) @kyleamathews
-* Optimizations around prefetching page resources [#1133](https://github.com/gatsbyjs/pull/1133) @kyleamathews
-* Redux example site [#1081](https://github.com/gatsbyjs/pull/1081) @scottyeck
-* Sitemap Generator Plugin [#1115](https://github.com/gatsbyjs/pull/1115) @nicholaswyoung
+* Allow for gatsby-remark-smartypants options [#1166](https://github.com/gatsbyjs/gatsby/pull/1166) @mitchejj
+* New design (for gatsbyjs.org) + new home page [#1170](https://github.com/gatsbyjs/gatsby/pull/1170) @kyleamathews
+* Add ability to locally define plugins [#1126](https://github.com/gatsbyjs/gatsby/pull/1126) @0x80
+* Add rough draft for docs for creating source plugins [#1159](https://github.com/gatsbyjs/gatsby/pull/1159) @kyleamathews
+* Optimizations around prefetching page resources [#1133](https://github.com/gatsbyjs/gatsby/pull/1133) @kyleamathews
+* Redux example site [#1081](https://github.com/gatsbyjs/gatsby/pull/1081) @scottyeck
+* Sitemap Generator Plugin [#1115](https://github.com/gatsbyjs/gatsby/pull/1115) @nicholaswyoung
 * Add documentation to gatsby-remark-prism @kyleamathews
 
 ### Changed
-* Move all filter operators for connections under a top-level "filter" field [#1177](https://github.com/gatsbyjs/pull/1177) @kyleamathews
-* Change `linkPrefix` to `pathPrefix` and add an example site [#1155](https://github.com/gatsbyjs/pull/1155) @kyleamathews
-* Make the plugin options for remark plugins the second argument (like everywhere else) [#1167](https://github.com/gatsbyjs/pull/1167) @kyleamathews
+* Move all filter operators for connections under a top-level "filter" field [#1177](https://github.com/gatsbyjs/gatsby/pull/1177) @kyleamathews
+* Change `linkPrefix` to `pathPrefix` and add an example site [#1155](https://github.com/gatsbyjs/gatsby/pull/1155) @kyleamathews
+* Make the plugin options for remark plugins the second argument (like everywhere else) [#1167](https://github.com/gatsbyjs/gatsby/pull/1167) @kyleamathews
 * Start using next instead of canary in example sites for package versions @kyleamathews
 
 ### Fixed
-* Fix graphql compiler on typescript [#949](https://github.com/gatsbyjs/pull/949) @fabien0102
-* Replace react.createClass with ES6 classes in examples html.js, add PropTypes [#1169](https://github.com/gatsbyjs/pull/1169) @abachuk
-* Fix windows build pull [#1158](https://github.com/gatsbyjs/pull/1158) @kyleamathews
+* Fix graphql compiler on typescript [#949](https://github.com/gatsbyjs/gatsby/pull/949) @fabien0102
+* Replace react.createClass with ES6 classes in examples html.js, add PropTypes [#1169](https://github.com/gatsbyjs/gatsby/pull/1169) @abachuk
+* Fix windows build pull [#1158](https://github.com/gatsbyjs/gatsby/pull/1158) @kyleamathews
 * Use custom delimiter when flattening example values for enum fields so easy to convert back @kyleamathews
-* gatsby-remark-responsive-images: use span instead of div [#1151](https://github.com/gatsbyjs/pull/1151) @rstacruz
+* gatsby-remark-responsive-images: use span instead of div [#1151](https://github.com/gatsbyjs/gatsby/pull/1151) @rstacruz
 * Add check that we can actually find a linked image file node @kyleamathews
-* Ignore SVGs in gatsby-remark-responsive-image [#1157](https://github.com/gatsbyjs/pull/1157) @fk
-* Replace using levelup for caching with lowdb to avoid native dependency [#1142](https://github.com/gatsbyjs/pull/1142) @kyleamathews
-* Fix Appveyor bug regarding build all examples on release [#1118](https://github.com/gatsbyjs/pull/1118) @jbolda
+* Ignore SVGs in gatsby-remark-responsive-image [#1157](https://github.com/gatsbyjs/gatsby/pull/1157) @fk
+* Replace using levelup for caching with lowdb to avoid native dependency [#1142](https://github.com/gatsbyjs/gatsby/pull/1142) @kyleamathews
+* Fix Appveyor bug regarding build all examples on release [#1118](https://github.com/gatsbyjs/gatsby/pull/1118) @jbolda
 
 

docs/docs/plugins.md

@@ -93,7 +93,6 @@ you can place the files in a `src` subfolder and build them to the plugin folder
 * [gatsby-remark-responsive-iframe](/docs/packages/gatsby-remark-responsive-iframe/)
 * [gatsby-remark-responsive-image](/docs/packages/gatsby-remark-responsive-image/)
 * [gatsby-remark-smartypants](/docs/packages/gatsby-remark-smartypants/)
-* [gatsby-sharp](/docs/packages/gatsby-sharp/)
 * [gatsby-source-contentful](/docs/packages/gatsby-source-contentful/)
 * [gatsby-source-drupal](/docs/packages/gatsby-source-drupal/)
 * [gatsby-source-filesystem](/docs/packages/gatsby-source-filesystem/)

docs/tutorial/part-one.md

@@ -11,7 +11,7 @@ Sit down, buckle up, and let's get going!
 
 ## Check Environment
 
-Let's check first that you have everything setup to start working with Gatsby. You will need a recent version of [Node.js](nodejs.org) installed.
+Let's check first that you have everything setup to start working with Gatsby. You will need a recent version of [Node.js](https://nodejs.org) installed.
 
 Open a terminal window and type `node --version` then `npm --version`.
 

packages/gatsby/src/utils/api-node-docs.js

@@ -65,7 +65,7 @@ exports.createPages = true
  * `createPagesStatefully` will not.
  *
  * An example of a plugin that uses this extension point is the internal plugin
- * [component-page-creator](https://github.com/gatsbyjs/gatsby/tree/document-refactor-apis/packages/gatsby/src/bootstrap/internal-plugins/component-page-creator)
+ * [component-page-creator](https://github.com/gatsbyjs/gatsby/tree/1.0/packages/gatsby/src/internal-plugins/component-page-creator)
  * which monitors the `src/pages` directory for the adding and removal of JS
  * pages. As its source of truth, files in the pages directory, is not known by
  * Gatsby, it needs to keep its own state about its world to know when to