feat(www): Convert API pages to MDX

docs/docs/actions.mdx

@@ -0,0 +1,25 @@
+---
+title: "Actions"
+disableTableOfContents: true
+jsdoc: ["gatsby/src/redux/actions/public.js", "gatsby/src/redux/actions/restricted.js"]
+---
+
+import APIReference, {APIContents} from "../../www/src/components/api-reference"
+
+
+Gatsby uses [Redux](http://redux.js.org) internally to manage state. When you implement a Gatsby API, you are passed a collection of actions (equivalent to `boundActionCreators` in Redux) which you can use to manipulate state on your site.
+
+The object `actions` contains the functions and these can be individually extracted by using ES6 object destructuring.
+
+```javascript
+// For function createNodeField
+exports.onCreateNode = ({ node, getNode, actions }) => {
+  const { createNodeField } = actions
+}
+```
+
+## Functions
+<APIContents docs={props.mergedFuncs} />
+
+## Reference
+<APIReference docs={props.mergedFuncs} />

docs/docs/browser-apis.mdx

@@ -0,0 +1,17 @@
+---
+title: "Gatsby Browser APIs"
+disableTableOfContents: true
+jsdoc: ["gatsby/src/utils/api-browser-docs.js"]
+apicalls: "BrowserAPI"
+---
+
+import APIReference, {APIContents} from "../../www/src/components/api-reference"
+
+## Usage
+Implement any of these APIs by exporting them from a file named `gatsby-browser.js` in the root of your project.
+
+## APIs
+<APIContents docs={props.mergedFuncs} />
+
+## Reference
+<APIReference docs={props.mergedFuncs}  showTopLevelSignatures={true} />

docs/docs/node-api-helpers.mdx

@@ -0,0 +1,36 @@
+---
+title: "Node API Helpers"
+disableTableOfContents: true
+jsdoc: ["gatsby/src/utils/api-node-helpers-docs.js"]
+apicalls: "NodeAPIHelpers"
+---
+
+import APIReference, {APIContents} from "../../www/src/components/api-reference"
+
+The first argument passed to each of [Gatsby’s Node APIs](/docs/node-apis/) is an object containing a set of helpers. Helpers shared by all Gatsby’s Node APIs are documented in [Shared helpers](#shared-helpers) section.
+
+```javascript
+// in gatsby-node.js
+exports.createPages = gatsbyNodeHelpers => {
+  const { actions, reporter } = gatsbyNodeHelpers
+  // use helpers
+}
+```
+
+Common convention is to destructure helpers right in argument list:
+
+```javascript
+// in gatsby-node.js
+exports.createPages = ({ actions, reporter }) => {
+  // use helpers
+}
+```
+
+## Note
+Some APIs provide additional helpers. For example `createPages` provides `graphql` function. Check documentation of specific APIs in (Gatsby Node APIs)[/docs/node-apis/] for details.
+
+## Shared helpers
+<APIContents docs={props.mergedFuncs} />
+
+## Reference
+<APIReference docs={props.mergedFuncs} showTopLevelSignatures={true}/>

docs/docs/node-apis.mdx

@@ -0,0 +1,39 @@
+---
+title: "Gatsby Node APIs"
+disableTableOfContents: true
+jsdoc: ["gatsby/src/utils/api-node-docs.js"]
+apicalls: "NodeAPI"
+---
+
+import APIReference, {APIContents} from "../../www/src/components/api-reference"
+
+Gatsby gives plugins and site builders many APIs for controlling your site's data in the GraphQL data layer.
+
+## Async plugins
+If your plugin performs async operations (disk I/O, database access, calling remote APIs, etc.) you must either return a promise or use the callback passed to the 3rd argument. Gatsby needs to know when plugins are finished as some APIs, to work correctly, require previous APIs to be complete first. See [Debugging Async Lifecycles](/docs/debugging-async-lifecycles/) for more info.
+
+```javascript
+// Promise API
+exports.createPages = () => {
+  return new Promise((resolve, reject) => {
+    // do async work
+  })
+}
+
+// Callback API
+exports.createPages = (_, pluginOptions, cb) => {
+  // do Async work
+  cb()
+}
+```
+
+If your plugin does not do async work, you can just return directly.
+
+## Usage
+Implement any of these APIs by exporting them from a file named `gatsby-node.js` in the root of your project.
+
+## APIs
+<APIContents docs={props.mergedFuncs} />
+
+## Reference
+<APIReference docs={props.mergedFuncs} />

docs/docs/node-model.mdx

@@ -0,0 +1,35 @@
+---
+title: "Node Model"
+disableTableOfContents: true
+jsdoc: ["gatsby/src/schema/node-model.js"]
+apicalls: "NodeModel"
+---
+
+import APIReference, {APIContents} from "../../www/src/components/api-reference"
+
+Gatsby exposes its internal data store and query capabilities to GraphQL field resolvers on `context.nodeModel`.
+
+## Example Usage
+### gatsby-node.js
+```javascript
+createResolvers({
+  Query: {
+    mood: {
+      type: `String`,
+      resolve(source, args, context, info) {
+        const coffee = context.nodeModel.getAllNodes({ type: `Coffee` })
+        if (!coffee.length) {
+          return 😞
+        }
+        return 😊
+      },
+    },
+  },
+})
+```
+
+## Methods
+<APIContents docs={props.mergedFuncs} />
+
+## Reference
+<APIReference docs={props.mergedFuncs} />

docs/docs/ssr-apis.mdx

@@ -0,0 +1,17 @@
+---
+title: "Gatsby Server Rendering APIs"
+disableTableOfContents: true
+jsdoc: ["gatsby/cache-dir/api-ssr-docs.js"]
+apicalls: "SSRAPI"
+---
+
+import APIReference, {APIContents} from "../../www/src/components/api-reference"
+
+## Usage
+Implement any of these APIs by exporting them from a file named `gatsby-ssr.js` in the root of your project.
+
+## APIs
+<APIContents docs={props.mergedFuncs} />
+
+## Reference
+<APIReference docs={props.mergedFuncs} showTopLevelSignatures={true} />

packages/gatsby/src/redux/actions/public.js

@@ -544,8 +544,10 @@ actions.deleteNode = (options: any, plugin: Plugin, args: any) => {
   }
 }
 
+// Marked private here because it was supressed in documentation pages.
 /**
  * Batch delete nodes
+ * @private
  * @param {Array} nodes an array of node ids
  * @example
  * deleteNodes([`node1`, `node2`])
@@ -582,8 +584,11 @@ actions.deleteNodes = (nodes: any[], plugin: Plugin) => {
 let NODE_COUNTER = 0
 
 const typeOwners = {}
+
+// memberof notation is added so this code can be referenced instead of the wrapper.
 /**
  * Create a new node.
+ * @memberof actions
  * @param {Object} node a node object
  * @param {string} node.id The node's ID. Must be globally unique.
  * @param {string} node.parent The ID of the parent's node. If the node is