fix docs links after renaming the reference section

jackmcdade · jackmcdade · commit 66c68871ef85 · 2016-03-30T16:56:45.000-04:00
diff --git a/README.md b/README.md
@@ -1,6 +1,6 @@
 # Statamic 2 Documentation
 
 This repo holds the content for the Statamic v2 docs site.
-[http://docs.talonsbeard.com](http://docs.talonsbeard.com)
+[http://docs.statamic.com](http://docs.statamic.com)
 
 Any commits made to this repo's `master` branch will be reflected on the site.
diff --git a/content/collections/fieldtypes/assets.md b/content/collections/fieldtypes/assets.md
@@ -32,7 +32,7 @@ bacon_images:
 
 ## Templating {#templating}
 
-Use the [Assets tag](/docs/tags/assets) to loop through the IDs and fetch the available data.
+Use the [Assets tag](/reference/tags/assets) to loop through the IDs and fetch the available data.
 
 ```
 {{ assets:bacon_images }}
diff --git a/content/collections/fieldtypes/collection.md b/content/collections/fieldtypes/collection.md
@@ -16,7 +16,7 @@ id: 0e7eb069-dc0c-4dfd-9230-67ca5d215395
 ---
 ## Data Structure {#data-structure}
 
-The Collections fieldtype is a [Relate fieldtype](/docs/fieldtypes/relate), which means the Entries will be saved as IDs.
+The Collections fieldtype is a [Relate fieldtype](/reference/fieldtypes/relate), which means the Entries will be saved as IDs.
 
 ``` .language-yaml
 shows:
@@ -26,7 +26,7 @@ shows:
 
 ## Templating
 
-Use the [Relate tag](/docs/tags/relate) to loop through the IDs and fetch the content data.
+Use the [Relate tag](/reference/tags/relate) to loop through the IDs and fetch the content data.
 
 ```
 <ul>
diff --git a/content/collections/fieldtypes/date.md b/content/collections/fieldtypes/date.md
@@ -1,6 +1,6 @@
 title: Date
 description: A datepicker that includes an optional timepicker.
 overview: >
-  Select a date and optional time. Data is stored as a timestamp and can be formatted with any of the date [modifiers](/docs/modifiers) or used in Tag conditions to filter results.
+  Select a date and optional time. Data is stored as a timestamp and can be formatted with any of the date [modifiers](/reference/modifiers) or used in Tag conditions to filter results.
 image: a462b8e7-86c1-49ce-9d96-0941dc922dd2
 id: 7dfba904-8a74-40e1-b507-51cd2b5f6123
diff --git a/content/collections/fieldtypes/grid.md b/content/collections/fieldtypes/grid.md
@@ -28,7 +28,7 @@ options:
     name: mode
     type: string *table*
     description: >
-      The Grid is displayed as a table by default. If you have a large number of columns it can get pretty crowded. Choose `stacked` mode to group rows similar to [Replicator](/docs/fieldtypes/replicator). When [Sneak Peek]() is enabled, Grids automatically toggle into stacked mode.
+      The Grid is displayed as a table by default. If you have a large number of columns it can get pretty crowded. Choose `stacked` mode to group rows similar to [Replicator](/reference/fieldtypes/replicator). When [Sneak Peek]() is enabled, Grids automatically toggle into stacked mode.
   -
     name: add_row
     type: string
diff --git a/content/collections/fieldtypes/relate.md b/content/collections/fieldtypes/relate.md
@@ -9,10 +9,10 @@ id: 9dd58c40-6e33-49c8-83fa-61a69f6371be
 
 You can relate any of the base [Content Types](/guides/content-types), each of which with its own specific fieldtype. They all extend this core Relate fieldtype.
 
-- [Taxonomy](/docs/fieldtypes/taxonomy) - for Taxonomy Terms
-- [Collection](/docs/fieldtypes/collection) - for Entries
-- [Users](/docs/fieldtypes/users) - for Users
-- [Assets](/docs/fieldtypes/assets) - for Assets (it doesn't extend this Relate fieldtype)
+- [Taxonomy](/reference/fieldtypes/taxonomy) - for Taxonomy Terms
+- [Collection](/reference/fieldtypes/collection) - for Entries
+- [Users](/reference/fieldtypes/users) - for Users
+- [Assets](/reference/fieldtypes/assets) - for Assets (it doesn't extend this Relate fieldtype)
 
 ## Data Structure {#data-structure}
 
@@ -26,7 +26,7 @@ wildlife:
 
 ### Templating {#templating}
 
-Use the [Relate tag](/docs/tags/relate) to loop through the IDs and fetch the content data.
+Use the [Relate tag](/reference/tags/relate) to loop through the IDs and fetch the content data.
 
 ```
 <ul>
diff --git a/content/collections/fieldtypes/suggest.md b/content/collections/fieldtypes/suggest.md
@@ -32,4 +32,4 @@ The values come from either a predefined array of `options`, or from a third-par
 The suggestions in this field will normally come from the `options` array, which is a predefined list of values.
 
 It is possible for an addon to provide suggestions to power this field. For example, an addon might create a suggest mode
-that fetches tweets from a Twitter user's account. [Learn how to make a Suggest Mode](/docs/recipes/suggest-modes).
+that fetches tweets from a Twitter user's account. [Learn how to make a Suggest Mode](/reference/recipes/suggest-modes).
diff --git a/content/collections/fieldtypes/table.md b/content/collections/fieldtypes/table.md
@@ -33,7 +33,7 @@ This data format makes it trivial when it comes time to render it templates.
 
 ## Templating
 
-This fieldtype comes with a handy [`table`](/docs/modifiers/table) modifier, which will turn your data into a simple HTML `<table>`.
+This fieldtype comes with a handy [`table`](/reference/modifiers/table) modifier, which will turn your data into a simple HTML `<table>`.
 
 ```
 {{ my_table | table }}
diff --git a/content/collections/fieldtypes/tags.md b/content/collections/fieldtypes/tags.md
@@ -19,4 +19,4 @@ Your tags will get saved as a simple YAML list, like this:
 ```
 
 Note: This fieldtype uses "Tags" in general terms. If you're looking for a way to tag/taxonomize your content, you
-may be interested in checking out [taxonomies](/guides/taxonomies) and the [Taxonomy fieldtype](/docs/fieldtypes/taxonomy).
+may be interested in checking out [taxonomies](/guides/taxonomies) and the [Taxonomy fieldtype](/reference/fieldtypes/taxonomy).
diff --git a/content/collections/fieldtypes/taxonomy.md b/content/collections/fieldtypes/taxonomy.md
@@ -15,7 +15,7 @@ id: 31adcc00-4fbb-4fe9-9b48-401061273096
 ---
 ## Data Structure
 
-The Taxonomy fieldtype is a [Relate fieldtype](/docs/fieldtypes/relate), which means the taxonomies will be saved as IDs.
+The Taxonomy fieldtype is a [Relate fieldtype](/reference/fieldtypes/relate), which means the taxonomies will be saved as IDs.
 
 ``` .language-yaml
 wildlife:
@@ -25,7 +25,7 @@ wildlife:
 
 ## Templating
 
-Use the [Relate tag](/docs/tags/relate) to loop through the IDs and fetch the content data.
+Use the [Relate tag](/reference/tags/relate) to loop through the IDs and fetch the content data.
 
 ```
 <ul>
diff --git a/content/collections/fieldtypes/users.md b/content/collections/fieldtypes/users.md
@@ -8,7 +8,7 @@ id: 0f8102b9-c948-4264-8cb8-cbfbd0415a04
 ---
 ## Data Structure {#data-structure}
 
-The Users fieldtype is a [Relate fieldtype](/docs/fieldtypes/relate), which means the users will be saved as IDs.
+The Users fieldtype is a [Relate fieldtype](/reference/fieldtypes/relate), which means the users will be saved as IDs.
 
 ``` .language-yaml
 jedis:
@@ -18,7 +18,7 @@ jedis:
 
 ## Templating {#templating}
 
-Use the [Relate tag](/docs/tags/relate) to loop through the IDs and fetch the user data.
+Use the [Relate tag](/reference/tags/relate) to loop through the IDs and fetch the user data.
 
 ```
 <ul>
diff --git a/content/collections/fieldtypes/yaml.md b/content/collections/fieldtypes/yaml.md
@@ -13,4 +13,4 @@ options:
       field.
 id: 25155800-8fd7-46c7-aad0-5daaf07543da
 ---
-This field is essentially a [Textarea fieldtype](/docs/fieldtypes/textarea) that gets saved as YAML instead of a string.
+This field is essentially a [Textarea fieldtype](/reference/fieldtypes/textarea) that gets saved as YAML instead of a string.
diff --git a/content/collections/modifiers/format.md b/content/collections/modifiers/format.md
@@ -18,5 +18,5 @@ event_date: April 15 2016
 2016-04-15
 ```
 
-[carbon]: http://carbon.nesbot.com/docs/
+[carbon]: http://carbon.nesbot.com/reference/
 [datetime]: http://php.net/manual/en/function.date.php
diff --git a/content/collections/modifiers/format_localized.md b/content/collections/modifiers/format_localized.md
@@ -21,5 +21,5 @@ Vendredi 15 avril 2016
 ```
 
 
-[carbon]: http://carbon.nesbot.com/docs/
+[carbon]: http://carbon.nesbot.com/reference/
 [strftime]: http://php.net/strftime
diff --git a/content/collections/modifiers/table.md b/content/collections/modifiers/table.md
@@ -6,7 +6,7 @@ types:
   - utility
 id: 4d8e0392-af96-4b46-a73a-d3a47b57ccbe
 ---
-Takes an array generated by the [Table Fieldtype](/docs/fieldtypes/table), and converts into a basic HTML `<table>`.
+Takes an array generated by the [Table Fieldtype](/reference/fieldtypes/table), and converts into a basic HTML `<table>`.
 
 ``` .language-yaml
 my_table:
diff --git a/content/collections/recipes/blade.md b/content/collections/recipes/blade.md
@@ -7,7 +7,7 @@ id: efa34b0d-b4c3-43fc-bb91-a6d331dc6026
 ---
 ## The Blade Templating Language
 
-You can find out how to use Blade, the templating language over on the [Laravel docs](https://laravel.com/docs/blade).  
+You can find out how to use Blade, the templating language over on the [Laravel docs](https://laravel.com/reference/blade).  
 Here we'll be explaining how to use it in the context of Statamic.
 
 ## Using in a theme
@@ -75,7 +75,7 @@ Your Blade template would have access to the variables in this file:
 
 ## Modifiers
 
-You can use [Modifiers](/docs/modifiers) in your Blade templates, but they will use a different syntax than
+You can use [Modifiers](/reference/modifiers) in your Blade templates, but they will use a different syntax than
 what you're used to with Antlers.
 
 First, wrap your variable in a `modify()` method, then feel free to chain modifiers as you wish. The value
diff --git a/content/collections/recipes/filesystems.md b/content/collections/recipes/filesystems.md
@@ -88,7 +88,7 @@ To relocate a filesystem, simply change the `root` variable to one of the follow
 
   - A path relative to the main filesystem root. (eg. `site/content`)
   - An absolute path. (eg. `/var/www/example.com/content`)
-  - An absolute path with an [interpolated environment variable](/docs/recipes/settings). (eg. `"{env‌:BASE_PATH}/content"`)
+  - An absolute path with an [interpolated environment variable](/reference/recipes/settings). (eg. `"{env‌:BASE_PATH}/content"`)
 
 \* Asset containers can be modified in their respective `container.yaml` file or CP pages.
 
diff --git a/content/collections/recipes/redirects.md b/content/collections/recipes/redirects.md
@@ -58,4 +58,4 @@ to perform the redirect before Statamic even gets loaded.
 
 This is the preferred method for permanent redirects.
 
-[redirect_tag]: /docs/tags/redirect
+[redirect_tag]: /reference/tags/redirect
diff --git a/content/collections/recipes/secure-installation.md b/content/collections/recipes/secure-installation.md
@@ -95,4 +95,4 @@ You'll also want to update your asset container `path` and `url` values, which c
 4. Adjust [filesystem references][filesystems].
 5. Adjust the asset container's path in `container.yaml`.
 
-[filesystems]: /docs/recipes/filesystems
+[filesystems]: /reference/recipes/filesystems
diff --git a/content/collections/recipes/suggest-modes.md b/content/collections/recipes/suggest-modes.md
@@ -5,7 +5,7 @@ overview: >
   somewhere on the internet, or your local grocer.
 id: dd9212d0-978c-4b86-a51f-745464ff0721
 ---
-The "[Relate](/docs/fieldtypes/relate)" fields – "[Users](/docs/fieldtypes/users)", "[Taxonomy](/docs/fieldtypes/taxonomy)", "[Collection](/docs/fieldtypes/collection)" – all leverage the "[Suggest](/docs/fieldtypes/suggest)" field behind the scenes.
+The "[Relate](/reference/fieldtypes/relate)" fields – "[Users](/reference/fieldtypes/users)", "[Taxonomy](/reference/fieldtypes/taxonomy)", "[Collection](/reference/fieldtypes/collection)" – all leverage the "[Suggest](/reference/fieldtypes/suggest)" field behind the scenes.
 
 While the Relate fields might not look like a Suggest field, they follow the same basic principle: they retrieve "suggestions" through an AJAX call.
 
diff --git a/content/collections/tags/404.md b/content/collections/tags/404.md
@@ -23,4 +23,4 @@ In this example, we will trigger a 404 if there are no results in a collection.
 {{ /collection:blog }}
 ```
 
-[redirect_tag]: /docs/tags/redirect
+[redirect_tag]: /reference/tags/redirect
diff --git a/content/collections/tags/assets.md b/content/collections/tags/assets.md
@@ -2,7 +2,7 @@
 id: 5b748a3f-be0e-41c1-8877-73f6b7ee1d0a
 title: Assets
 overview: >
-    Used to retrieve Assets data from the [Asset Fieldtype](/docs/fieldtypes/assets). Your site's Assets are managed and stored independently of your pages and entries and have a joined relationship through their `id`. [Learn more about Assets](/guides/assets).
+    Used to retrieve Assets data from the [Asset Fieldtype](/reference/fieldtypes/assets). Your site's Assets are managed and stored independently of your pages and entries and have a joined relationship through their `id`. [Learn more about Assets](/guides/assets).
 description: Fetch image/file Assets from an Assets field.
 variables:
   -
diff --git a/content/collections/tags/collection-next.md b/content/collections/tags/collection-next.md
@@ -29,7 +29,7 @@ parameters:
   -
     name: collection params
     type: inheritance
-    description: 'All parameters available on the [collection tag](/docs/tags/collection) are also available here.'
+    description: 'All parameters available on the [collection tag](/reference/tags/collection) are also available here.'
 variables:
   -
     name: no_results
diff --git a/content/collections/tags/collection-previous.md b/content/collections/tags/collection-previous.md
@@ -3,7 +3,7 @@ title: Previous
 overview: Grab the previous entries relative to current entry in a Collection.
 id: 741cf972-c0bd-4e3c-81e2-8cc8bea60737
 ---
-This Tag functions the same way as the [`collection:next`](/docs/tags/collection-next) tag, but in the opposite direction.
+This Tag functions the same way as the [`collection:next`](/reference/tags/collection-next) tag, but in the opposite direction.
 
 ```
 {{ collection:previous in="blog" as="posts" limit="2" sort="date:asc" }}
diff --git a/content/collections/tags/collection.md b/content/collections/tags/collection.md
@@ -264,7 +264,7 @@ You can optionally put your entries loop in a scope, if you’d like to be more
 
 You don’t have to wrap your entries loop in the `else` of your `if no_results` conditional. If there are no posts, the loop will simply output nothing.
 
-You can [read more about scope and the cascade here](/docs/recipes/cascade).
+You can [read more about scope and the cascade here](/reference/recipes/cascade).
 
 ## Pagination {#pagination}
 
@@ -385,5 +385,5 @@ Here's the `auto_links` output, recreated using the other tags, for you maverick
 
 See, just a couple of keystrokes.
 
-[conditions]: /docs/conditions
+[conditions]: /reference/conditions
 [custom_filters]: /addons/filters
diff --git a/content/collections/tags/entries.md b/content/collections/tags/entries.md
@@ -37,4 +37,4 @@ For example:
 
 In this tag, Statamic will check the `/company/news` page for any mounted entry collections. If it has a mounted collection (with `mount: articles`, for example) the tag will get the entries in the `articles` collection.
 
-[collection]: /docs/tags/collection
+[collection]: /reference/tags/collection
diff --git a/content/collections/tags/form-submissions.md b/content/collections/tags/form-submissions.md
@@ -22,7 +22,7 @@ variables:
 
 ## Usage {#usage}
 
-This tag has the same functionality as the [collection](/docs/tags/collection) tag, with exception that the collection
+This tag has the same functionality as the [collection](/reference/tags/collection) tag, with exception that the collection
 is of form submissions rather than entries.
 
 ```
diff --git a/content/collections/tags/get_value.md b/content/collections/tags/get_value.md
@@ -23,7 +23,7 @@ id: b4d337c9-5012-48eb-8819-48b6d35571bc
 ## Usage {#usage}
 
 The first way to use this tag is to get an array value from another URL. This is essentially the single-tag version of
-wrapping some templating in a [get_content tag](/docs/tags/get_content).
+wrapping some templating in a [get_content tag](/reference/tags/get_content).
 
 ``` .language-yaml
 title: Drinks
diff --git a/content/collections/tags/nav.md b/content/collections/tags/nav.md
@@ -51,7 +51,7 @@ parameters:
     name: filter
     type: wizardry
     description: >
-      Filter the tree by using a special conditions syntax, the same as the [Collections tag](/docs/tags/collection). View the [available conditions](/docs/conditions).
+      Filter the tree by using a special conditions syntax, the same as the [Collections tag](/reference/tags/collection). View the [available conditions](/reference/conditions).
 variables:
   -
     name: is_published
@@ -158,7 +158,7 @@ has been removed in favor of the following workflow.
         display: Hide from navigation
    ```
 
-2. In your `nav` tag, use the [conditions syntax](/docs/conditions) to remove any hidden pages:
+2. In your `nav` tag, use the [conditions syntax](/reference/conditions) to remove any hidden pages:
 
    ```
    {{ nav from="/" is_hidden:isnt_set="true" }}
diff --git a/content/collections/tags/pages-next.md b/content/collections/tags/pages-next.md
@@ -30,7 +30,7 @@ parameters:
   -
     name: collection params
     type: inheritance
-    description: 'All parameters available on the [collection tag](/docs/tags/collection) are also available here.'
+    description: 'All parameters available on the [collection tag](/reference/tags/collection) are also available here.'
 variables:
   -
     name: no_results
@@ -60,4 +60,4 @@ This will show the next 2 pages sibling pages. It'll scope the loop into the `st
 {{ /pages:next }}
 ```
 
-Note: When using `as`, don't use `as="pages"` since it will assume you are trying to use the [Pages Tag](/docs/tags/pages).
+Note: When using `as`, don't use `as="pages"` since it will assume you are trying to use the [Pages Tag](/reference/tags/pages).
diff --git a/content/collections/tags/pages-previous.md b/content/collections/tags/pages-previous.md
@@ -3,7 +3,7 @@ title: Previous
 overview: Grab the previous Pages relative to your current Page.
 id: 1172608e-0e75-487a-8cd6-872746542550
 ---
-This Tag functions the same way as the [`pages:next`](/docs/tags/pages-next) tag, but in the opposite direction.
+This Tag functions the same way as the [`pages:next`](/reference/tags/pages-next) tag, but in the opposite direction.
 
 ```
 {{ pages:previous as="stories" limit="2" }}
diff --git a/content/collections/tags/pages.md b/content/collections/tags/pages.md
@@ -70,6 +70,6 @@ Notice only the immediate child pages are output. If we wanted to get the next l
 ```
 
 Notice that (by default) the pages are being sorted by the order key, then alphabetically. They are also displayed in a
-single list, as siblings. If you'd like to output the hierarchy, you should use the [Nav Tag](/docs/tags/nav).
+single list, as siblings. If you'd like to output the hierarchy, you should use the [Nav Tag](/reference/tags/nav).
 
-[collection]: /docs/tags/collection
+[collection]: /reference/tags/collection
diff --git a/content/collections/tags/relate.md b/content/collections/tags/relate.md
@@ -9,7 +9,7 @@ id: dd9513b4-4cbb-4481-bf72-eb076e053b04
 ---
 ## Parameters {#parameters}
 
-The parameters are inherited from the [collection](/docs/tags/collection) tag. Everything available there is available here.
+The parameters are inherited from the [collection](/reference/tags/collection) tag. Everything available there is available here.
 
 ## Example {#example}
 
diff --git a/content/collections/tags/taxonomy.md b/content/collections/tags/taxonomy.md
@@ -191,5 +191,5 @@ The filter will get the taxonomy collection instance, _not_ the content collecti
 
 
 
-[conditions]: /docs/conditions
+[conditions]: /reference/conditions
 [custom_filters]: /addons/filters
diff --git a/content/collections/tags/user-forgot_password_form.md b/content/collections/tags/user-forgot_password_form.md
@@ -80,4 +80,4 @@ This email is bundled with Statamic and will work for most people out of the box
 like to customize it, you can. [Find out how to write custom emails][custom-emails]. The template
 used is `user-reset` and should contain a `{{ reset_url }}` variable, which is the generated reset URL.
 
-[custom-emails]: /docs/recipes/emails#templates
+[custom-emails]: /reference/recipes/emails#templates
diff --git a/content/collections/tags/user-logout.md b/content/collections/tags/user-logout.md
@@ -22,4 +22,4 @@ id: 3604bfe9-89be-42af-8163-4b378279026a
 
 This will immediately log a user out and redirect to `/somewhere` if the condition is met.
 
-If you'd like to just output a link, use the [`user:logout_url`](/docs/tags/user-logout_url) tag.
+If you'd like to just output a link, use the [`user:logout_url`](/reference/tags/user-logout_url) tag.
diff --git a/content/collections/tags/user.md b/content/collections/tags/user.md
@@ -6,4 +6,4 @@ overview: >
 id: fcdfb1e0-5cf5-4669-9c00-3064e43cb630
 is_parent_tag: true
 ---
-The `user` tag on its own is an alias of the [`user:profile`](/docs/tags/user-profile) Tag.
+The `user` tag on its own is an alias of the [`user:profile`](/reference/tags/user-profile) Tag.
diff --git a/content/collections/tags/users.md b/content/collections/tags/users.md
@@ -32,4 +32,4 @@ Here we will loop over the users with gmail email addresses.
 </ul>
 ```
 
-[collection]: /docs/tags/collection
+[collection]: /reference/tags/collection
diff --git a/content/collections/variables/current_uri.md b/content/collections/variables/current_uri.md
@@ -10,5 +10,5 @@ The current URI (URL without domain).
 ```
 
 ``` .language-output
-/docs/variables
+/reference/variables
 ```
diff --git a/content/collections/variables/current_url.md b/content/collections/variables/current_url.md
@@ -10,5 +10,5 @@ The current URL.
 ```
 
 ``` .language-output
-http://learn.statamic.com/docs/variables
+http://learn.statamic.com/reference/variables
 ```
diff --git a/content/collections/variables/edit_url.md b/content/collections/variables/edit_url.md
@@ -5,7 +5,7 @@ types:
 ---
 Get the URL to edit a the current page or entry in the Control Panel, if there is one (for example, there is no `edit_url` for a template route).
 
-The user will need to login and have permissions, so it's probably best if used in conjunction with [permissions checks](/docs/tags/user-can).
+The user will need to login and have permissions, so it's probably best if used in conjunction with [permissions checks](/reference/tags/user-can).
 
 ```
 <a href="{{ edit_url }}">Edit this page</a>
diff --git a/content/pages/1.reference/1.tags/index.md b/content/pages/1.reference/1.tags/index.md
diff --git a/content/pages/2.addons/5.events/index.md b/content/pages/2.addons/5.events/index.md
diff --git a/content/pages/3.guides/1.getting-started/index.md b/content/pages/3.guides/1.getting-started/index.md
diff --git a/content/pages/3.guides/10.search/index.md b/content/pages/3.guides/10.search/index.md
diff --git a/content/pages/3.guides/11.permissions/index.md b/content/pages/3.guides/11.permissions/index.md
diff --git a/content/pages/3.guides/12.caching/index.md b/content/pages/3.guides/12.caching/index.md
diff --git a/content/pages/3.guides/13.debugging/index.md b/content/pages/3.guides/13.debugging/index.md
diff --git a/content/pages/3.guides/2.upgrading-from-v1/index.md b/content/pages/3.guides/2.upgrading-from-v1/index.md
diff --git a/content/pages/3.guides/3.content-types/index.md b/content/pages/3.guides/3.content-types/index.md
diff --git a/content/pages/3.guides/4.template-language/index.md b/content/pages/3.guides/4.template-language/index.md
diff --git a/content/pages/3.guides/4.theming/index.md b/content/pages/3.guides/4.theming/index.md
diff --git a/content/pages/3.guides/6.urls-and-routing/index.md b/content/pages/3.guides/6.urls-and-routing/index.md
diff --git a/content/pages/3.guides/7.assets/index.md b/content/pages/3.guides/7.assets/index.md
diff --git a/content/pages/3.guides/8.taxonomies/index.md b/content/pages/3.guides/8.taxonomies/index.md
diff --git a/content/pages/3.guides/9.forms/index.md b/content/pages/3.guides/9.forms/index.md
