diff options
| author | Dave Whiteland <dave@mysociety.org> | 2014-06-12 09:16:38 +0100 |
|---|---|---|
| committer | Dave Whiteland <dave@mysociety.org> | 2014-06-12 09:16:38 +0100 |
| commit | 9d6ff9e88126a65f4763d9145beb82b5363c7472 (patch) | |
| tree | dc80c1ceba90da70ae35214f70cb0ea90c092c2b | |
| parent | 667a3ffb11cb83d08dd40f1ca5a52e65d801aec4 (diff) | |
explicit link to installation from deploy page
| -rw-r--r-- | installing/deploy.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/installing/deploy.md b/installing/deploy.md index 63be3c96d..d0d548a64 100644 --- a/installing/deploy.md +++ b/installing/deploy.md @@ -14,9 +14,9 @@ title: Deploying ## Why deploy? -Although you can install Alaveteli in a number of ways, once you're running, -sooner or later you'll need to make changes to the site. A common example is -updating your site when we issue a new release. +Although you can [install Alaveteli]({{ site.baseurl }}installing/) in a number +of ways, once you're running, sooner or later you'll need to make changes to +the site. A common example is updating your site when we issue a new release. The deployment mechanism takes care of putting all the right files into the right place, so when you need to put changes live, there's no risk of you |