diff options
author | Dave Whiteland <dave@mysociety.org> | 2014-07-09 18:11:33 +0100 |
---|---|---|
committer | Dave Whiteland <dave@mysociety.org> | 2014-07-09 18:11:33 +0100 |
commit | 8ab79db54687bcc503a27fb3f25aa6b05a7580d7 (patch) | |
tree | 320a273d278c5940d001fc1f2b7d8228c86abc7e | |
parent | 2f2852afe9fec3b05a165cec36395f6788507b2b (diff) |
fix glossary links on installation index page
-rw-r--r-- | docs/installing/index.md | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/docs/installing/index.md b/docs/installing/index.md index ff132861c..50bcfd25a 100644 --- a/docs/installing/index.md +++ b/docs/installing/index.md @@ -17,8 +17,8 @@ title: Installing ## Before you start This is important: you need to decide if you are installing Alaveteli for -[development]({{ site.baseurl }}docs/glossary/#development) or -[production]({{ site.baseurl }}docs/glossary/#production). +<a href="{{ site.baseurl }}docs/glossary/#development" class="glossary__link">development</a> or +<a href="{{ site.baseurl }}docs/glossary/#production" class="glossary__link">production</a>. A **development** site is one where you're going to change, customise, and perhaps experiment while you get it up and running. You should always do this @@ -32,9 +32,10 @@ messages switched off. It's important to be able to deploy changes to a production site quickly and efficiently, so we recommend you consider using a [deployment mechanism]({{ site.baseurl }}docs/installing/deploy/) too. -Ideally, you should also have a [staging site]({{ site.baseurl }}docs/glossary/#staging), +Ideally, you should also have a +<a href="{{ site.baseurl }}docs/glossary/#staging" class="glossary__link">staging site</a>, which is used solely to test new code in an identical environment to your -production site but before it goes live. +production site before it goes live. If you're in doubt, you're probably running a development site. Get it up and running, play with it, customise it, and -- later -- you can install it as a |