From b75a88352a685c4ba2dd3640aff6853cc1cdf216 Mon Sep 17 00:00:00 2001
From: Sean Madsen <sean@seanmadsen.com>
Date: Sat, 24 Jun 2017 19:56:37 -0600
Subject: [PATCH] Fix auto-detected broken links

---
 docs/documentation/style-guide.md | 2 +-
 docs/extensions/civix.md          | 6 +++---
 docs/extensions/index.md          | 2 +-
 docs/tools/buildkit.md            | 2 +-
 docs/tools/civibuild.md           | 2 +-
 docs/tools/index.md               | 8 ++++----
 6 files changed, 11 insertions(+), 11 deletions(-)

diff --git a/docs/documentation/style-guide.md b/docs/documentation/style-guide.md
index 150c02e4..f7e9d170 100644
--- a/docs/documentation/style-guide.md
+++ b/docs/documentation/style-guide.md
@@ -111,7 +111,7 @@ Alternative Text  (ALT Tags) should be included for every image.
 
 ### Machine-readable symbols
 
-Machine-readable symbols (e.g. files names, classes, functions, variables, database tables, database columns, commands, etc.) should be formatted either with inline monospace or preformatted code blocks (also in monospace). See the [markdown syntax](/markdownrules.md#code) to use for such formatting.
+Machine-readable symbols (e.g. files names, classes, functions, variables, database tables, database columns, commands, etc.) should be formatted either with inline monospace or preformatted code blocks (also in monospace). See the [markdown syntax](/documentation/markdown.md#code) to use for such formatting.
 
 ### URLs
 
diff --git a/docs/extensions/civix.md b/docs/extensions/civix.md
index b2699bf8..f043a5ff 100644
--- a/docs/extensions/civix.md
+++ b/docs/extensions/civix.md
@@ -8,7 +8,7 @@ community-endorsed method for building your CiviCRM extensions.
 Follow the installation instructions in the
 [GitHub repository](https://github.com/totten/civix/).
 
-After fulfilling the [Pre-Requisites](/extensions/basics.md#pre-requisites), you can verify that all your configuration is correct by running the following command from
+After fulfilling the [Pre-Requisites](/extensions/index.md#pre-requisites), you can verify that all your configuration is correct by running the following command from
 within your extensions directory with:
 
 ```bash
@@ -31,7 +31,7 @@ civix help civicrm:ping
 ## Generating a skeletal extension {:#generate-module}
 
 To generate a skeletal extension module, we will use `civix generate:module`
-and pass in the name for our extension. See [here](/extensions/basics.md#extension-names)
+and pass in the name for our extension. See [here](/extensions/index.md#extension-names)
 for details of naming conventions.
 
 Start with:
@@ -428,7 +428,7 @@ $values = CRM_Core_BAO_CustomValueTable::getValues($params);
 ### Add a hook function
 
 CiviCRM
-[hook functions](/hooks.md)
+[hook functions](/hooks/index.md)
 allow extensions to run extra logic as
 part of the normal CiviCRM processing. For example,
 `hook_civicrm_buildForm()` allows a module to run logic whenever a
diff --git a/docs/extensions/index.md b/docs/extensions/index.md
index 4561cdac..e79e617a 100644
--- a/docs/extensions/index.md
+++ b/docs/extensions/index.md
@@ -90,7 +90,7 @@ Extension authors may make their extensions available to the larger CiviCRM
 community by publishing them in the [Extensions Directory](https://civicrm.org/extensions).
 >> See: [Publish](/extensions/publish.md)
 
-Extensions which undergo a [formal review](/extend-stages.md#formal-review) may be
+Extensions which undergo a [formal review](/extensions/lifecycle.md#formal-review) may be
 distributed in-app. Approved extensions can be [installed
 directly](https://docs.civicrm.org/user/en/master/introduction/extensions/#installing-extensions)
 into CiviCRM via the user interface, lowering the barrier to entry for many users.
diff --git a/docs/tools/buildkit.md b/docs/tools/buildkit.md
index 9a45a65c..da1a4f40 100644
--- a/docs/tools/buildkit.md
+++ b/docs/tools/buildkit.md
@@ -2,7 +2,7 @@
 
 [Buildkit](https://github.com/civicrm/civicrm-buildkit) is a collection of ~20 tools for developing and testing CiviCRM, the most important of which is [civibuild](/tools/civibuild.md).
 
-Many of these tools are commonly used by web developers, so you may have already installed a few. Even so, it's generally easier to [install](/buildkit/setup.md) the full collection &mdash; installing each individually takes a lot of work.
+Many of these tools are commonly used by web developers, so you may have already installed a few. Even so, it's generally easier to install the full collection &mdash; installing each individually takes a lot of work.
 
 This is the same collection of tools which manages the test/demo/release infrastructure for civicrm.org.
 
diff --git a/docs/tools/civibuild.md b/docs/tools/civibuild.md
index 00b174e4..c08a0203 100644
--- a/docs/tools/civibuild.md
+++ b/docs/tools/civibuild.md
@@ -54,7 +54,7 @@ The command will print out URLs and credentials for accessing the website.
 $ civibuild create dmaster --url http://dmaster.localhost --admin-pass s3cr3t
 ```
 
-Once you have a working build of `dmaster`, you can continue working with `civibuild` to create different builds (as described below) or [learn more about other day-to-day development tasks](/buildkit/tutorials.md).
+Once you have a working build of `dmaster`, you can continue working with `civibuild` to create different builds as described below.
 
 ## Build Types
 
diff --git a/docs/tools/index.md b/docs/tools/index.md
index 016524cd..40e6d4ba 100644
--- a/docs/tools/index.md
+++ b/docs/tools/index.md
@@ -2,7 +2,7 @@
 
 ## Tools included with buildkit {:#with-buildkit}
 
-When you install [buildkit](/buildkit.md) you'll get all these tools.
+When you install [buildkit](/tools/buildkit.md) you'll get all these tools.
 
 *This list of tools is also maintained [in the buildkit readme file](https://github.com/civicrm/civicrm-buildkit/blob/master/README.md).*
 
@@ -21,7 +21,7 @@ When you install [buildkit](/buildkit.md) you'll get all these tools.
     * *documentation: run `civistrings --help`*
     * *[repository](https://github.com/civicrm/civistrings)*
 * `cividist` - Generate tarballs from a series of git branches/tags
-    * *[documentation](/buildkit/cividist.md)*
+    * *[documentation](/tools/cividist.md)*
     * *repository: [within civicrm-buildkit](https://github.com/civicrm/civicrm-buildkit/blob/master/bin/cividist)*
 * `gitify` - Convert a CiviCRM installation to a git repo
     * *documentation: run `gitify` with no arguments*
@@ -41,7 +41,7 @@ When you install [buildkit](/buildkit.md) you'll get all these tools.
 
 ### External tools installed with buildkit {:#external}
 
-These tools are not specific to CiviCRM, so you may already have some of them installed on your system. If you install [buildkit](/buildkit.md) you'll get all these tools at once, in addition to the CiviCRM-specific tools listed above.
+These tools are not specific to CiviCRM, so you may already have some of them installed on your system. If you install [buildkit](/tools/buildkit.md) you'll get all these tools at once, in addition to the CiviCRM-specific tools listed above.
 
 * Dependency management
     * [composer](http://getcomposer.org/) - Manage dependencies for PHP code.
@@ -69,7 +69,7 @@ These tools are not specific to CiviCRM, so you may already have some of them in
 * [git](https://git-scm.com/) - version control system
 * [psysh](http://psysh.org/) - a reply-echo-print-loop for PHP (like `php -a`, but better)
 * [MySQL Workbench](https://www.mysql.com/products/workbench/) - A graphical interface to your local (or remote) MySQL server
-* [MkDocs](http://www.mkdocs.org) - for [editing documentation](/documentation.md)
+* [MkDocs](http://www.mkdocs.org) - for [editing documentation](/documentation/index.md)
 
 ### Text editors
 
-- 
GitLab