Restructure docs files.

Author: ghengeveld

docs/_summary.md

@@ -4,14 +4,14 @@
 
 ## Getting started
 
-- [Installation](installation.md)
-- [Upgrading](upgrading.md)
-- [Usage](usage.md)
-- [DevTools](devtools.md)
+- [Installation](getting-started/installation.md)
+- [Upgrading](getting-started/upgrading.md)
+- [Usage](getting-started/usage.md)
+- [DevTools](getting-started/devtools.md)
 
 ## API
 
-- [Interfaces](interfaces.md)
-- [Configuration options](options.md)
-- [State properties](state.md)
-- [Helper components](helpers.md)
+- [Interfaces](api/interfaces.md)
+- [Configuration options](api/options.md)
+- [State properties](api/state.md)
+- [Helper components](api/helpers.md)

docs/helpers.md renamed to docs/api/helpers.md

@@ -1,6 +1,7 @@
 # DevTools
 
-React Async comes with a separate DevTools package which helps you Debug and develop your asynchronous application states. You can install it from npm:
+React Async comes with a separate DevTools package which helps you Debug and develop your asynchronous application
+states. You can install it from npm:
 
 ```text
 npm install --save react-async-devtools

docs/interfaces.md renamed to docs/api/interfaces.md

@@ -12,4 +12,5 @@ Or if you're using Yarn:
 yarn add react-async
 ```
 
-> This package requires `react` as a peer dependency. Please make sure to install that as well. If you want to use the `useAsync` hook, you'll need `[email protected]` or later.
+> This package requires `react` as a peer dependency. Please make sure to install that as well. If you want to use the
+> `useAsync` hook, you'll need `[email protected]` or later.

docs/options.md renamed to docs/api/options.md

@@ -1,17 +1,32 @@
 # Introduction
 
-React Async is a utility belt for declarative promise resolution and data fetching. It makes it easy to handle asynchronous UI states, without assumptions about the shape of your data or the type of request. React Async consists of a React component and several hooks. You can use it with `fetch`, Axios or other data fetching libraries, even GraphQL.
+React Async is a utility belt for declarative promise resolution and data fetching. It makes it easy to handle
+asynchronous UI states, without assumptions about the shape of your data or the type of request. React Async consists of
+a React component and several hooks. You can use it with `fetch`, Axios or other data fetching libraries, even GraphQL.
 
 ## Rationale
 
-React Async is different in that it tries to resolve data as close as possible to where it will be used, while using declarative syntax, using just JSX and native promises. This is in contrast to systems like Redux where you would configure any data fetching or updates on a higher \(application global\) level, using a special construct \(actions/reducers\).
+React Async is different in that it tries to resolve data as close as possible to where it will be used, while using
+declarative syntax, using just JSX and native promises. This is in contrast to systems like Redux where you would
+configure any data fetching or updates on a higher (application global) level, using a special construct
+(actions/reducers).
 
-React Async works well even in larger applications with multiple or nested data dependencies. It encourages loading data on-demand and in parallel at component level instead of in bulk at the route/page level. It's entirely decoupled from your routes, so it works well in complex applications that have a dynamic routing model or don't use routes at all.
+React Async works well even in larger applications with multiple or nested data dependencies. It encourages loading data
+on-demand and in parallel at component level instead of in bulk at the route/page level. It's entirely decoupled from
+your routes, so it works well in complex applications that have a dynamic routing model or don't use routes at all.
 
 React Async is promise-based, so you can resolve anything you want, not just `fetch` requests.
 
 ## Concurrent React and Suspense
 
-The React team is currently working on a large rewrite called [Concurrent React](https://github.com/sw-yx/fresh-concurrent-react/blob/master/Intro.md#introduction-what-is-concurrent-react), previously known as "Async React". Part of this rewrite is Suspense, which is a generic way for components to suspend rendering while they load data from a cache. It can render a fallback UI while loading data, much like `<Async.Pending>`.
+The React team is currently working on a large rewrite called [Concurrent React], previously known as "Async React".
+Part of this rewrite is Suspense, which is a generic way for components to suspend rendering while they load data from a
+cache. It can render a fallback UI while loading data, much like `<Async.Pending>`.
 
-React Async has no direct relation to Concurrent React. They are conceptually close, but not the same. React Async is meant to make dealing with asynchronous business logic easier. Concurrent React will make those features have less impact on performance and usability. When Suspense lands, React Async will make full use of Suspense features. In fact, you can already **start using React Async right now**, and in a later update, you'll **get Suspense features for free**. In fact, React Async already has experimental support for Suspense, by passing the `suspense` option.
+React Async has no direct relation to Concurrent React. They are conceptually close, but not the same. React Async is
+meant to make dealing with asynchronous business logic easier. Concurrent React will make those features have less
+impact on performance and usability. When Suspense lands, React Async will make full use of Suspense features. In fact,
+you can already **start using React Async right now**, and in a later update, you'll **get Suspense features for free**.
+In fact, React Async already has experimental support for Suspense, by passing the `suspense` option.
+
+[concurrent react]: https://github.com/sw-yx/fresh-concurrent-react/blob/master/Intro.md#introduction-what-is-concurrent-react