Fix docs: reintroduce index pages, fix all references

Author: spawnia

docs/class-reference.md

@@ -422,7 +422,7 @@ const INPUT_FIELD_DEFINITION = "INPUT_FIELD_DEFINITION";
 # GraphQL\Type\SchemaConfig
 Schema configuration class.
 Could be passed directly to schema constructor. List of options accepted by **create** method is
-[described in docs](type-definitions/schema-definition.md#configuration-options).
+described in the [schema definition docs](schema-definition.md#configuration-options).
 
 Usage example:
 
@@ -565,7 +565,7 @@ function getTypeLoader()
 function setTypeLoader(callable $typeLoader)
 ```
 # GraphQL\Type\Schema
-Schema Definition (see [related docs](type-definitions/schema-definition.md))
+Schema Definition (see [schema definition docs](schema-definition.md))
 
 A Schema is created by supplying the root types of each type of operation:
 query, mutation (optional) and subscription (optional). A schema definition is
@@ -763,7 +763,7 @@ function assertValid()
 function validate()
 ```
 # GraphQL\Language\Parser
-Parses string containing GraphQL query or [type definition](type-definitions/schema-definition-language.md) to Abstract Syntax Tree.
+Parses string containing GraphQL query language or [schema definition language](schema-definition-language.md) to Abstract Syntax Tree.
 
 Those magic functions allow partial parsing:
 

docs/complementary-tools.md

@@ -1,6 +1,6 @@
 # Integrations
 
-* [Standard Server](executing-queries.md/#using-server) – Out of the box integration with any PSR-7 compatible framework (like [Slim](http://slimframework.com) or [Zend Expressive](http://zendframework.github.io/zend-expressive/)).
+* [Standard Server](executing-queries.md#using-server) – Out of the box integration with any PSR-7 compatible framework (like [Slim](http://slimframework.com) or [Zend Expressive](http://zendframework.github.io/zend-expressive/)).
 * [Relay Library for graphql-php](https://github.com/ivome/graphql-relay-php) – Helps construct Relay related schema definitions.
 * [Lighthouse](https://github.com/nuwave/lighthouse) – Laravel based, uses Schema Definition Language
 * [Laravel GraphQL](https://github.com/rebing/graphql-laravel) - Laravel wrapper for Facebook's GraphQL

docs/data-fetching.md

@@ -4,7 +4,7 @@ plain files or in-memory data structures.
 
 In order to convert the GraphQL query to PHP array, **graphql-php** traverses query fields (using depth-first algorithm) and 
 runs special **resolve** function on each field. This **resolve** function is provided by you as a part of 
-[field definition](type-definitions/object-types.md#field-configuration-options) or [query execution call](executing-queries.md#overview).
+[field definition](type-definitions/object-types.md#field-configuration-options) or [query execution call](executing-queries.md).
 
 Result returned by **resolve** function is directly included in the response (for scalars and enums)
 or passed down to nested fields (for objects).

docs/executing-queries.md

@@ -37,7 +37,7 @@ Description of **executeQuery** method arguments:
 
 Argument     | Type     | Notes
 ------------ | -------- | -----
-schema       | [`GraphQL\Type\Schema`](#) | **Required.** Instance of your application [Schema](schema-definition.md)
+schema       | [`GraphQL\Type\Schema`](class-reference.md#graphqltypeschema) | **Required.** Instance of your application [Schema](schema-definition.md)
 queryString  | `string` or `GraphQL\Language\AST\DocumentNode` | **Required.** Actual GraphQL query string to be parsed, validated and executed. If you parse query elsewhere before executing - pass corresponding AST document here to avoid new parsing.
 rootValue  | `mixed` | Any value that represents a root of your data graph. It is passed as the 1st argument to field resolvers of [Query type](schema-definition.md#query-and-mutation-types). Can be omitted or set to null if actual root values are fetched by Query type itself.
 context  | `mixed` | Any value that holds information shared between all field resolvers. Most often they use it to pass currently logged in user, locale details, etc.<br><br>It will be available as the 3rd argument in all field resolvers. (see section on [Field Definitions](type-definitions/object-types.md#field-configuration-options) for reference) **graphql-php** never modifies this value and passes it *as is* to all underlying resolvers.
@@ -95,7 +95,7 @@ PSR-7 is useful when you want to integrate the server into existing framework:
 
 Argument     | Type     | Notes
 ------------ | -------- | -----
-schema       | [`Schema`](class-reference.md#graphqltypeschema) | **Required.** Instance of your application [Schema](type-definitions/schema/)
+schema       | [`Schema`](class-reference.md#graphqltypeschema) | **Required.** Instance of your application [Schema](schema-definition.md)
 rootValue  | `mixed` | Any value that represents a root of your data graph. It is passed as the 1st argument to field resolvers of [Query type](schema-definition.md#query-and-mutation-types). Can be omitted or set to null if actual root values are fetched by Query type itself.
 context  | `mixed` | Any value that holds information shared between all field resolvers. Most often they use it to pass currently logged in user, locale details, etc.<br><br>It will be available as the 3rd argument in all field resolvers. (see section on [Field Definitions](type-definitions/object-types.md#field-configuration-options) for reference) **graphql-php** never modifies this value and passes it *as is* to all underlying resolvers.
 fieldResolver | `callable` | A resolver function to use when one is not provided by the schema. If not provided, the [default field resolver is used](data-fetching.md#default-field-resolver).
@@ -105,7 +105,7 @@ debugFlag | `int` | Debug flags. See [docs on error debugging](error-handling.md
 persistentQueryLoader | `callable` | A function which is called to fetch actual query when server encounters **queryId** in request vs **query**.<br><br> The server does not implement persistence part (which you will have to build on your own), but it allows you to execute queries which were persisted previously.<br><br> Expected function signature:<br> **function ($queryId, [OperationParams](class-reference.md#graphqlserveroperationparams) $params)** <br><br>Function is expected to return query **string** or parsed **DocumentNode** <br><br> [Read more about persisted queries](https://dev-blog.apollodata.com/persisted-graphql-queries-with-apollo-client-119fd7e6bba5).
 errorFormatter | `callable` | Custom error formatter. See [error handling docs](error-handling.md#custom-error-handling-and-formatting).
 errorsHandler | `callable` | Custom errors handler. See [error handling docs](error-handling.md#custom-error-handling-and-formatting).
-promiseAdapter | [`PromiseAdapter`](class-reference.md#graphqlexecutorpromisepromiseadapter) | Required for [Async PHP](data-fetching/#async-php) only.
+promiseAdapter | [`PromiseAdapter`](class-reference.md#graphqlexecutorpromisepromiseadapter) | Required for [Async PHP](data-fetching.md#async-php) only.
 
 **Server config instance**
 

docs/getting-started.md

@@ -62,7 +62,7 @@ $queryType = new ObjectType([
 
 ```
 
-(Note: type definition can be expressed in [different styles](type-definitions/introduction.md#definition-styles))
+(Note: type definition can be expressed in [different styles](type-definitions/index.md#definition-styles))
 
 The interesting piece here is **resolve** option of field definition. It is responsible for returning 
 a value of our field. Values of **scalar** fields will be directly included in response while values of 

docs/about.md renamed to docs/index.md

@@ -28,8 +28,8 @@ are used. Instead, it provides tools for creating rich API for your existing app
 
 Library features include:
 
- - Primitives to express your app as a [Type System](type-definitions/introduction.md)
- - Validation and introspection of this Type System (for compatibility with tools like [GraphiQL](complementary-tools.md#tools))
+ - Primitives to express your app as a [Type System](type-definitions/index.md)
+ - Validation and introspection of this Type System (for compatibility with [tools like GraphiQL](complementary-tools.md#general-graphql-tools))
  - Parsing, validating and [executing GraphQL queries](executing-queries.md) against this Type System
  - Rich [error reporting](error-handling.md), including query validation and execution errors
  - Optional tools for [parsing schema definition language](schema-definition-language.md)

docs/type-definitions/enums.md

@@ -30,7 +30,7 @@ $episodeEnum = new EnumType([
 ```
 
 This example uses an **inline** style for Enum Type definition, but you can also use
-[inheritance or schema definition language](introduction.md#definition-styles).
+[inheritance or schema definition language](index.md#definition-styles).
 
 # Configuration options
 Enum Type constructor accepts an array with following options:

docs/type-definitions/introduction.md renamed to docs/type-definitions/index.md

@@ -33,7 +33,7 @@ $character = new InterfaceType([
 ]);
 ```
 This example uses **inline** style for Interface definition, but you can also use  
-[inheritance or schema definition language](introduction.md#definition-styles).
+[inheritance or schema definition language](index.md#definition-styles).
 
 # Configuration options
 The constructor of InterfaceType accepts an array. Below is a full list of allowed options:

docs/type-definitions/interfaces.md

@@ -5,7 +5,7 @@ Conceptually Object Type is a collection of Fields. Each field, in turn,
 has its own type which allows building complex hierarchies.
 
 In **graphql-php** object type is an instance of `GraphQL\Type\Definition\ObjectType` 
-(or one of it subclasses) which accepts configuration array in constructor:
+(or one of its subclasses) which accepts a configuration array in its constructor:
 
 ```php
 <?php
@@ -57,36 +57,32 @@ $blogStory = new ObjectType([
 ]);
 ```
 This example uses **inline** style for Object Type definitions, but you can also use  
-[inheritance or schema definition language](introduction.md#definition-styles).
+[inheritance or schema definition language](index.md#definition-styles).
 
 # Configuration options
-Object type constructor expects configuration array. Below is a full list of available options:
 
 Option       | Type     | Notes
 ------------ | -------- | -----
 name         | `string` | **Required.** Unique name of this object type within Schema
-fields       | `array` or `callable` | **Required**. An array describing object fields or callable returning such an array. See [Fields](#field-definitions) section below for expected structure of each array entry. See also the section on [Circular types](#recurring-and-circular-types) for an explanation of when to use callable for this option.
+fields       | `array` or `callable` | **Required**. An array describing object fields or callable returning such an array. See [field configuration options](#field-configuration-options) section below for expected structure of each array entry. See also the section on [Circular types](#recurring-and-circular-types) for an explanation of when to use callable for this option.
 description  | `string` | Plain-text description of this type for clients (e.g. used by [GraphiQL](https://github.com/graphql/graphiql) for auto-generated documentation)
 interfaces   | `array` or `callable` | List of interfaces implemented by this type or callable returning such a list. See [Interface Types](interfaces.md) for details. See also the section on [Circular types](#recurring-and-circular-types) for an explanation of when to use callable for this option.
 isTypeOf     | `callable` | **function($value, $context, [ResolveInfo](../class-reference.md#graphqltypedefinitionresolveinfo) $info)**<br> Expected to return **true** if **$value** qualifies for this type (see section about [Abstract Type Resolution](interfaces.md#interface-role-in-data-fetching) for explanation).
 resolveField | `callable` | **function($value, $args, $context, [ResolveInfo](../class-reference.md#graphqltypedefinitionresolveinfo) $info)**<br> Given the **$value** of this type, it is expected to return value for a field defined in **$info->fieldName**. A good place to define a type-specific strategy for field resolution. See section on [Data Fetching](../data-fetching.md) for details.
 
-# Field configuration options
-Below is a full list of available field configuration options:
+## Field configuration options
 
 Option | Type | Notes
 ------ | ---- | -----
 name | `string` | **Required.** Name of the field. When not set - inferred from **fields** array key (read about [shorthand field definition](#shorthand-field-definitions) below)
 type | `Type` | **Required.** An instance of internal or custom type. Note: type must be represented by a single instance within one schema (see also [lazy loading of types](../schema-definition.md#lazy-loading-of-types))
-args | `array` | An array of possible type arguments. Each entry is expected to be an array with keys: **name**, **type**, **description**, **defaultValue**. See [Field Arguments](#field-arguments) section below.
+args | `array` | An array describing any number of possible field arguments, each element being an array. See [field argument configuration options](#field-argument-configuration-options).
 resolve | `callable` | **function($objectValue, $args, $context, [ResolveInfo](../class-reference.md#graphqltypedefinitionresolveinfo) $info)**<br> Given the **$objectValue** of this type, it is expected to return actual value of the current field. See section on [Data Fetching](../data-fetching.md) for details
 complexity | `callable` | **function($childrenComplexity, $args)**<br> Used to restrict query complexity. The feature is disabled by default, read about [Security](../security.md#query-complexity-analysis) to use it.
 description | `string` | Plain-text description of this field for clients (e.g. used by [GraphiQL](https://github.com/graphql/graphiql) for auto-generated documentation)
 deprecationReason | `string` | Text describing why this field is deprecated. When not empty - field will not be returned by introspection queries (unless forced)
 
-# Field arguments
-Every field on a GraphQL object type can have zero or more arguments, defined in **args** option of field definition.
-Each argument is an array with following options:
+## Field argument configuration options
 
 Option | Type | Notes
 ------ | ---- | -----
@@ -149,7 +145,9 @@ $userType = new ObjectType([
 ]);
 ```
 
-Same example for [inheritance style of type definitions](introduction.md#type-definition-styles) using [TypeRegistry](introduction.md#type-registry):
+Same example for [inheritance style of type definitions](index.md#definition-styles)
+using a type registry (see [lazy loading of types](../schema-definition.md#lazy-loading-of-types)):
+
 ```php
 <?php
 namespace MyApp;