Moved GridField docs to reference

docs/en/changelogs/3.0.0.md

@@ -61,7 +61,7 @@ which points to the framework directory, and in the templates you can use `$Modu
 
 ### GridField: Replacement for TableListField and ComplexTableField [gridfield]###
 
-We have a new component for managing lists of objects: The `[GridField](/topics/grid-field)`.
+We have a new component for managing lists of objects: The `[GridField](/reference/grid-field)`.
 It's a substantial rewrite of the features previously captured by `TableListField`,
 `ComplexTableField`, `HasManyComplexTableField` and `ManyManyComplexTableField`.
 
@@ -97,7 +97,7 @@ Upgrade example: Relationship editing
 	// after
 	$field = new GridField('MyRelation', null, $myRecord->MyRelation(), GridFieldConfig_RelationEditor::create());
 
-More information is available in the [GridField documentation](/topics/grid-field).
+More information is available in the [GridField documentation](/reference/grid-field).
 
 ### Object static functions replaced with new Config class {#new-config}
 Static functions for getting a static variable on the `Object` class have been deprecated,

docs/en/changelogs/alpha/3.0.0-alpha2.md

@@ -34,7 +34,7 @@ For more information see documentation at [/topics/datamodel](../../topics/datam
 GridField has changed since 3.0.0-alpha1 to be more flexible. Any previous implementation are broken
 and need to be changed according to the new API.
 
-For implementation details see documentation at [/topics/grid-field](../../topics/grid-field).
+For implementation details see documentation at [/reference/grid-field](../../reference/grid-field).
 
 ## Upgrading ##
 

docs/en/reference/complextablefield.md

@@ -3,7 +3,7 @@
 ## Introduction
 
 <div class="warning" markdown="1">
-	This field is deprecated in favour of the new [GridField](/topics/grid-field) API.
+	This field is deprecated in favour of the new [GridField](/reference/grid-field) API.
 </div>
 
 Shows a group of DataObjects as a (readonly) tabular list (similiar to `[api:TableListField]`.)

docs/en/reference/form-field-types.md

@@ -59,7 +59,7 @@ doesn't necessarily have any visible styling.
  * `[api:TableField]`: In-place editing of tabular data.
  * `[api:TreeDropdownField]`: Dropdown-like field that allows you to select an item from a hierarchical AJAX-expandable tree.
  * `[api:TreeMultiselectField]`: Represents many-many joins using a tree selector shown in a dropdown-like element
- * `[api:GridField](/topics/grid-field)`: Displays a `[api:SS_List]` in a tabular format. Versatile base class which can be configured to allow editing, sorting, etc.
+ * `[api:GridField](/reference/grid-field)`: Displays a `[api:SS_List]` in a tabular format. Versatile base class which can be configured to allow editing, sorting, etc.
  * `[api:ListboxField]`: Multi-line listbox field, through `<select multiple>`.
 
 

docs/en/reference/index.md

@@ -5,6 +5,7 @@ Reference articles complement our auto-generated [API docs](http://api.silverstr
 * [Advanced templates](advanced-templates): Advanced SilverStripe template syntax
 * [BBCode](bbcode): Extensible shortcode syntax
 * [ComplexTableField](complextablefield): Manage records and their relations inside the CMS
+* [GridField](grid-field): The GridField is a flexible form field for creating tables of data.
 * [Database Structure](database-structure): Conventions and best practices for database tables and fields
 * [DataObject](dataobject): Base class for database records
 * [DataExtension](dataextension): A "mixin" system allowing to extend core classes

docs/en/reference/modeladmin.md

@@ -9,7 +9,7 @@ It uses the framework's knowledge about the model to provide sensible defaults,
 allowing you to get started in a couple of lines of code,
 while still providing a solid base for customization.
 
-The interface is mainly powered by the `[GridField](/topics/grid-field)` class,
+The interface is mainly powered by the `[GridField](/reference/grid-field)` class,
 which can also be used in other CMS areas (e.g. to manage a relation on a `SiteTree`
 record in the standard CMS interface).
 
@@ -69,7 +69,7 @@ for the search form, override `[api:DataObject->getCustomSearchContext()]` on yo
 
 ## Result Columns
 
-The results are shown in a tabular listing, powered by the `[GridField](/topics/grid-field)`,
+The results are shown in a tabular listing, powered by the `[GridField](/reference/grid-field)`,
 more specifically the `[api:GridFieldDataColumns]` component.
 It looks for a `[api:DataObject::$summary_fields]` static on your model class,
 where you can add or remove columns, or change their title.
@@ -136,7 +136,7 @@ Has-one relationships are simply implemented as a `[api:DropdownField]` by defau
 Consider replacing it with a more powerful interface in case you have many records
 (through customizing `[api:DataObject->getCMSFields]`).
 
-Has-many and many-many relationships are usually handled via the `[GridField](/topics/grid-field)` class,
+Has-many and many-many relationships are usually handled via the `[GridField](/reference/grid-field)` class,
 more specifically the `[api:GridFieldAddExistingAutocompleter]` and `[api:GridFieldRelationDelete]` components.
 They provide a list/detail interface within a single record edited in your ModelAdmin.
 
@@ -217,7 +217,7 @@ For an introduction how to customize the CMS templates, see our [CMS Architectur
 
 ## Related
 
-* [/topics/grid-field](GridField): The UI component powering ModelAdmin
+* [/reference/grid-field](GridField): The UI component powering ModelAdmin
 * [/tutorials/5-dataobject-relationship-management](Tutorial 5: Dataobject Relationship Management)
 *  `[api:SearchContext]`
 * [genericviews Module](http://silverstripe.org/generic-views-module)

docs/en/reference/tablelistfield.md

@@ -3,7 +3,7 @@
 ## Introduction
 
 <div class="warning" markdown="1">
-	This field is deprecated in favour of the new [GridField](/topics/grid-field) API.
+	This field is deprecated in favour of the new [GridField](/reference/grid-field) API.
 </div>
 
 Form field that embeds a list of `[api:DataObject]`s into a form, such as a member list or a file list.

docs/en/topics/index.md

@@ -18,7 +18,6 @@ It is where most documentation should live, and is the natural "second step" aft
  * [Files and Images](files): File and Image management in the database and how to manipulate images
  * [Form Validation](form-validation): Built-in validation on form fields, and how to extend it
  * [Forms](forms): Create your own form, add fields and create your own form template using the existing `Form` class
- * [GridField](grid-field): The GridField is a flexible form field for creating tables of data.
  * [Internationalization (i18n)](i18n): Displaying templates and PHP code in different languages using i18n
  * [Javascript](javascript): Best practices for developing with JavaScript in SilverStripe
  * [Module Development](module-development): Creating a module (also known as "extension" or "plugin") to contain reusable functionality

docs/en/tutorials/5-dataobject-relationship-management.md

@@ -114,7 +114,7 @@ But what about creating `Student` records?
 
 Since students are related to a single project, we will
 allow editing them right the on the CMS interface in the `Project` page type.
-We do this through a powerful field called `[GridField](/topics/grid-field)`.
+We do this through a powerful field called `[GridField](/reference/grid-field)`.
 All customization to fields for a page type are managed through a method called
 `getCMSFields()`, so let's add it there: