From e3f4653111457274e1554f2bd74cc41c9ad0f9b5 Mon Sep 17 00:00:00 2001
From: Arjun Suresh <arjunsuresh1987@gmail.com>
Date: Fri, 18 Oct 2024 19:26:39 +0100
Subject: [PATCH] Support base_url for internal links

---
 _includes/footer.html      |  2 +-
 _includes/header.html      |  6 +++---
 _includes/nav-sub.html     |  2 +-
 _layouts/default.html      |  6 +++---
 _layouts/home.html         | 28 ++++++++++++-------------
 addons/index.md            |  8 ++++----
 addons/plugins.md          |  6 +++---
 addons/themes.md           |  4 ++--
 addons/translations.md     |  6 +++---
 code/external.md           |  2 +-
 code/functions.md          |  8 ++++----
 code/structure.md          |  2 +-
 index.md                   |  2 +-
 install/index.md           |  8 ++++----
 install/single-sign-on.md  |  2 +-
 install/upgrade.md         |  2 +-
 install/versions/index.md  |  4 ++--
 install/wordpress.md       |  2 +-
 plugins/index.md           | 42 +++++++++++++++++++-------------------
 plugins/layers.md          |  4 ++--
 plugins/modules-captcha.md |  4 ++--
 plugins/modules-editor.md  |  8 ++++----
 plugins/modules-event.md   |  4 ++--
 plugins/modules-filter.md  |  6 +++---
 plugins/modules-login.md   |  6 +++---
 plugins/modules-page.md    |  6 +++---
 plugins/modules-process.md |  4 ++--
 plugins/modules-search.md  |  6 +++---
 plugins/modules-viewer.md  |  6 +++---
 plugins/modules-widget.md  |  4 ++--
 plugins/modules.md         | 26 +++++++++++------------
 plugins/overrides.md       |  2 +-
 plugins/tutorial.md        | 32 ++++++++++++++---------------
 themes/index.md            |  2 +-
 translate/index.md         |  6 +++---
 35 files changed, 134 insertions(+), 134 deletions(-)

diff --git a/_includes/footer.html b/_includes/footer.html
index 5977d15..eab3da5 100644
--- a/_includes/footer.html
+++ b/_includes/footer.html
@@ -1,7 +1,7 @@
 <footer class="footer">
 	<nav class="footer-nav">
 		{% for navpage in site.nav.footer %}
-			<a class="footer-nav-link" href="{{ navpage.url }}">{{ navpage.name }}</a>
+			<a class="footer-nav-link" href="{% if navpage.url contains 'http' %}{{ navpage.url }}{% else %}{{ site.baseurl }}{{ navpage.url }}{% endif %}">{{ navpage.name }}</a>
 		{% endfor %}
 	</nav>
 	<div class="credit">
diff --git a/_includes/header.html b/_includes/header.html
index e786056..b894222 100644
--- a/_includes/header.html
+++ b/_includes/header.html
@@ -2,14 +2,14 @@
 
 <header class="header">
 	<div class="header-logo">
-		<a href="/"><img class="logo-img normal-logo" src="/images/question2answer-logo-white-350x40.png" alt="Question2Answer logo"></a>
+		<a href="/"><img class="logo-img normal-logo" src="{{ site.baseurl }}/images/question2answer-logo-white-350x40.png" alt="Question2Answer logo"></a>
 	</div>
 	<nav class="top-nav main-nav">
 		{% for navpage in site.nav.main %}
-			<a class="main-nav-link" href="{{ navpage.path }}">{{ navpage.name }}</a>
+			<a class="main-nav-link" href="{{ site.baseurl }}{{ navpage.path }}">{{ navpage.name }}</a>
 		{% endfor %}
 		{% for navpage in site.nav.second %}
-			<a class="main-nav-link {{ navpage.class | default: '' }}" href="{{ navpage.url }}">{{ navpage.name }}</a>
+			<a class="main-nav-link {{ navpage.class | default: '' }}" href="{% if navpage.url contains 'http' %}{{ navpage.url }}{% else %}{{ site.baseurl }}{{ navpage.url }}{% endif %}">{{ navpage.name }}</a>
 		{% endfor %}
 	</nav>
 </header>
diff --git a/_includes/nav-sub.html b/_includes/nav-sub.html
index 4c2c86b..0a7ca4b 100644
--- a/_includes/nav-sub.html
+++ b/_includes/nav-sub.html
@@ -7,7 +7,7 @@ <h4 class="docs-nav-title">{{ navpage.name }}</h4>
 		{% if navpage.sub %}
 			<ul class="docs-nav">
 				{% for subnavpage in site.nav[navpage.sub] %}
-					<li class="docs-nav-item"><a href="{{ subnavpage.path }}">{{ subnavpage.name }}</a></li>
+					<li class="docs-nav-item"><a href="{{ site.baseurl }}{{ subnavpage.path }}">{{ subnavpage.name }}</a></li>
 				{% endfor %}
 			</ul>
 		{% endif %}
diff --git a/_layouts/default.html b/_layouts/default.html
index 77348c4..ebc5a5b 100644
--- a/_layouts/default.html
+++ b/_layouts/default.html
@@ -8,14 +8,14 @@
 	<link rel="preconnect" href="https://fonts.gstatic.com">
 	<link rel="stylesheet" href="https://fonts.googleapis.com/css2?family=Roboto:ital,wght@0,400;0,700;1,400;1,700">
 	<link rel="stylesheet" href="https://fonts.googleapis.com/icon?family=Material+Icons">
-	<link rel="stylesheet" href="/css/styles2020.css">
+	<link rel="stylesheet" href="{{ site.baseurl }}/css/styles2020.css">
 
 	<title>{% if page.title %}{{ page.title | escape }}{% else %}{{ site.title }}{% endif %}</title>
 	<meta name="description" content="{{ site.description }}">
 
 	<link rel="canonical" href="{{ page.url | replace:'index.html','' | prepend: site.url }}">
-	<link rel="shortcut icon" type="image/x-icon" href="/favicon.ico">
-	<link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png">
+	<link rel="shortcut icon" type="image/x-icon" href="{{ site.baseurl }}/favicon.ico">
+	<link rel="apple-touch-icon" sizes="180x180" href="{{ site.baseurl }}/apple-touch-icon.png">
 	{% include analytics.html %}
 </head>
 
diff --git a/_layouts/home.html b/_layouts/home.html
index 7512c12..b106e5e 100644
--- a/_layouts/home.html
+++ b/_layouts/home.html
@@ -23,8 +23,8 @@ <h1 class="home-intro"><strong>Question2Answer</strong> (Q2A) is a popular open
 		{% include card-showcase.html icon="people" title="Why offer Q&amp;A on my site?" answer=answerText %}
 
 		{% capture answerText %}
-			<p><a href="https://www.question2answer.org/question2answer-latest.zip"><b>Download Question2Answer</b></a>, then read <a href="/install/">how to install</a>.
-				Version 1.8.8 was <a href="/install/versions/">released</a> on July 25th, 2023.
+			<p><a href="https://www.question2answer.org/question2answer-latest.zip"><b>Download Question2Answer</b></a>, then read <a href="{{ site.baseurl }}/install/">how to install</a>.
+				Version 1.8.8 was <a href="{{ site.baseurl }}/install/versions/">released</a> on July 25th, 2023.
 				Also <a href="https://github.com/q2a/question2answer">on GitHub</a>.</p>
 			<p>Question2Answer is open source, <a href="https://www.question2answer.org/license.php">licensed under GPL v2+</a>.</p>
 		{% endcapture %}
@@ -43,9 +43,9 @@ <h1 class="home-intro"><strong>Question2Answer</strong> (Q2A) is a popular open
 
 		{% capture answerText %}
 			<ul>
-				<li>Q2A takes 5 minutes (or less!) to <a href="/install/">install</a>.</li>
-				<li>Easy styling with <a href="/themes/">CSS themes</a>.</li>
-				<li>Supports <a href="/translate/">translation</a> into any language.</li>
+				<li>Q2A takes 5 minutes (or less!) to <a href="{{ site.baseurl }}/install/">install</a>.</li>
+				<li>Easy styling with <a href="{{ site.baseurl }}/themes/">CSS themes</a>.</li>
+				<li>Supports <a href="{{ site.baseurl }}/translate/">translation</a> into any language.</li>
 				<li>Custom sidebar, widgets, pages and links.</li>
 				<li>SEO features such as <a href="https://www.sitemaps.org/">XML Sitemap</a> and neat URLs.</li>
 			</ul>
@@ -68,24 +68,24 @@ <h1 class="home-intro"><strong>Question2Answer</strong> (Q2A) is a popular open
 				<li>Create experts, editors, moderators and admins.</li>
 				<li>User avatars (or <a href="https://en.gravatar.com/">Gravatar</a>) and custom fields.</li>
 				<li>Private messages and public wall posts.</li>
-				<li>Log in via Facebook or others (using <a href="/addons/plugins/">plugins</a>).</li>
+				<li>Log in via Facebook or others (using <a href="{{ site.baseurl }}/addons/plugins/">plugins</a>).</li>
 			</ul>
 		{% endcapture %}
 		{% include card-showcase.html icon="face" title="Built-in user account management ..." answer=answerText %}
 
 		{% capture answerText %}
 			<ul>
-				<li>Out-of-the-box <a href="/install/wordpress/">WordPress</a> and Joomla integration.</li>
-				<li>Custom <a href="/install/single-sign-on/">single sign-on</a> support for other sites.</li>
-				<li>Deep integration and customization via <a href="/plugins/">plugins</a>.</li>
+				<li>Out-of-the-box <a href="{{ site.baseurl }}/install/wordpress/">WordPress</a> and Joomla integration.</li>
+				<li>Custom <a href="{{ site.baseurl }}/install/single-sign-on/">single sign-on</a> support for other sites.</li>
+				<li>Deep integration and customization via <a href="{{ site.baseurl }}/plugins/">plugins</a>.</li>
 			</ul>
 		{% endcapture %}
 		{% include card-showcase.html icon="assignment_ind" title="... or integrate with existing sites" answer=answerText %}
 
 		{% capture answerText %}
 			<ul>
-				<li>PHP/MySQL <a href="/install/optimize/">scalable</a> to millions of users and posts.</li>
-				<li><a href="/install/security/">Safe from</a> XSS, CSRF and SQL injection attacks.</li>
+				<li>PHP/MySQL <a href="{{ site.baseurl }}/install/optimize/">scalable</a> to millions of users and posts.</li>
+				<li><a href="{{ site.baseurl }}/install/security/">Safe from</a> XSS, CSRF and SQL injection attacks.</li>
 				<li>Beat spam with captchas, moderation and/or flagging.</li>
 			</ul>
 		{% endcapture %}
@@ -93,9 +93,9 @@ <h1 class="home-intro"><strong>Question2Answer</strong> (Q2A) is a popular open
 
 		{% capture answerText %}
 			<p>Contribute <a href="https://github.com/q2a/question2answer">via Github</a>,
-				create a <a href="/themes/">theme</a>,
-				<a href="/plugins/">plugin</a> or
-				<a href="/translate/">translation</a>.</p>
+				create a <a href="{{ site.baseurl }}/themes/">theme</a>,
+				<a href="{{ site.baseurl }}/plugins/">plugin</a> or
+				<a href="{{ site.baseurl }}/translate/">translation</a>.</p>
 		{% endcapture %}
 		{% include card-showcase.html icon="translate" title="How can I help?" answer=answerText %}
 
diff --git a/addons/index.md b/addons/index.md
index 52441f0..9500091 100644
--- a/addons/index.md
+++ b/addons/index.md
@@ -8,11 +8,11 @@ title: "Question2Answer - Add-ons"
 
 This page links to add-ons created by Question2Answer users. These are not endorsed for quality or suitability, but we hope they are useful. If you have something to contribute, please submit a pull request to [the docs](https://github.com/q2a/q2a.github.io/) or [get in touch](https://www.question2answer.org/feedback.php) - your help is much appreciated!
 
-## [Translations](/addons/translations/)
+## [Translations]({{ site.baseurl }}/addons/translations/)
 
-## [Themes](/addons/themes/)
+## [Themes]({{ site.baseurl }}/addons/themes/)
 
-## [Plugins](/addons/plugins/)
+## [Plugins]({{ site.baseurl }}/addons/plugins/)
 
-## [Clients](/addons/clients/)
+## [Clients]({{ site.baseurl }}/addons/clients/)
 
diff --git a/addons/plugins.md b/addons/plugins.md
index 0ad791e..c3b8b38 100644
--- a/addons/plugins.md
+++ b/addons/plugins.md
@@ -137,7 +137,7 @@ To install a plugin (requires Q2A 1.3 or later), place its directory in Q2A's `q
 - [Social Sharing Plugin](https://github.com/NoahY/q2a-share) by [NoahY](http://www.question2answer.org/qa/user/NoahY). Adds social sharing buttons to question pages.
 - [Sort Answers](https://github.com/amiyasahu/q2a-sort-answers) by [Amiya Sahu](http://amiyasahu.com/). Allows answers on a question page to be sorted by oldest, newest and highest voted.
 - [Tag Search](https://github.com/arjunsuresh/tag-search) by [Arjun](http://gateoverflow.in/user/Arjun). Allows tags to be searched via AJAX and with auto complete.
-- [Tag Descriptions Plugin](http://www.question2answer.org/releases/q2a-tag-descriptions-tutorial.zip) from the [plugin tutorial](/plugins/tutorial/). Allows tag descriptions to be shown on tag pages and in tooltips.
+- [Tag Descriptions Plugin](http://www.question2answer.org/releases/q2a-tag-descriptions-tutorial.zip) from the [plugin tutorial]({{ site.baseurl }}/plugins/tutorial/). Allows tag descriptions to be shown on tag pages and in tooltips.
 - [Theme Switcher Plugin](https://github.com/arjunsuresh/q2a-theme-switch) by [NoahY](http://www.question2answer.org/qa/user/NoahY) and updated by [Arjun](http://gateoverflow.in/user/Arjun). Allows users to choose their own theme on their profile page for normal as well as mobile view.
 - [Top Searches](https://github.com/arjunsuresh/q2a-top-search) by [Arjun](http://gateoverflow.in/user/Arjun). Adds a widget to display the top searched words. Also have an option to display top seacrhed tags if using [Tag Search](https://github.com/arjunsuresh/tag-search) plugin.
 - [User Signatures Plugin](https://github.com/NoahY/q2a-signatures) by [NoahY](http://www.question2answer.org/qa/user/NoahY). Allows users to define a signature for all of their posts. Also [forked here](https://github.com/pupi1985/q2a-signatures) by [pupi1985](https://www.question2answer.org/qa/user/pupi1985).
@@ -162,7 +162,7 @@ To install a plugin (requires Q2A 1.3 or later), place its directory in Q2A's `q
 - [Newsletter-favtags](https://github.com/ProThoughts/q2apro-newsletter-favtags) by [q2apro.com](https://github.com/q2apro).Users can subscribe to their favorite tags and the plugin emails them daily if there are new questions.
 - [Newsletter Plugin](https://github.com/NoahY/q2a-newsletter) by [NoahY](http://www.question2answer.org/qa/user/NoahY). Allows users to receive an HTML newsletter of the latest top questions, answers and comments.
 - [Tag and Category Notification](https://github.com/amiyasahu/q2a-email-notification) by [Amiya Sahu](http://amiyasahu.com/). When a question is asked with a tag/category, emails users who favorited that tag/category.
-- [Votes-manager](https://github.com/ProThoughts/q2apro-votes-manager) by [q2apro.com](https://github.com/q2apro).Lists all votes made in your forum.](https://github.com/q2apro).Sends emails to users about activities on questions they have favorited.
+- [Votes-manager](https://github.com/ProThoughts/q2apro-votes-manager) by [q2apro.com](https://github.com/q2apro). Lists all votes made in your forum. Sends emails to users about activities on questions they have favorited.
 
 ## Anti-spam tools
 
@@ -213,4 +213,4 @@ To install a plugin (requires Q2A 1.3 or later), place its directory in Q2A's `q
 - [Comment Voting Plugin](https://github.com/NoahY/q2a-comment-voting) by [NoahY](http://www.question2answer.org/qa/user/NoahY). Allows comments to be voted on, similarly to questions and answers.
 - [Question Closing](https://github.com/NoahY/q2a-close) by [NoahY](http://www.question2answer.org/qa/user/NoahY). Allows questions to be closed in Q2A 1.4.x.
 
-Click for documentation on [creating Q2A plugins](/plugins/) (requires PHP programming).
+Click for documentation on [creating Q2A plugins]({{ site.baseurl }}/plugins/) (requires PHP programming).
diff --git a/addons/themes.md b/addons/themes.md
index 3ea3c67..0b2f6bd 100644
--- a/addons/themes.md
+++ b/addons/themes.md
@@ -6,7 +6,7 @@ title: "Question2Answer Add-ons - Themes"
 
 # Question2Answer Themes
 
-To install a theme, place its directory in Q2A's `qa-theme` directory, then open the General section of the Admin panel and choose the theme from the menu provided. **Many good themes can be found at [Q2A service providers](/services/)**. Below is a list of other recently updated themes:
+To install a theme, place its directory in Q2A's `qa-theme` directory, then open the General section of the Admin panel and choose the theme from the menu provided. **Many good themes can be found at [Q2A service providers]({{ site.baseurl }}/services/)**. Below is a list of other recently updated themes:
 
 - [MayroPro](https://github.com/MominRaza/MayroPro) (A Google Material Design Theme with Dark Mode, RTL, PWA Support) by [Momin Raza](https://mominraza.github.io).
 - [Blog Theme](https://github.com/ostack/qa-ostack-blog-theme) by [ZhaoGuangyue](https://www.linkedin.com/in/%E5%85%89%E8%B7%83-%E8%B5%B5-b58234146) based on SnowFlat. [Demo](https://www.ostack.cn). This theme can show pictures and content in question lists, to make the Q2A site look like a blog.
@@ -35,4 +35,4 @@ To install a theme, place its directory in Q2A's `qa-theme` directory, then open
 - [Paid] [Frapuchino theme](https://rxchun.github.io/shop/frapuchino/) by [Chun](https://www.question2answer.org/qa/user/gold-developer). Shape shifter. Blog type of theme with thumbnail switch. RTL ready.
 - [Paid] [Legacy theme](https://rxchun.github.io/shop/legacy/) by [Chun](https://www.question2answer.org/qa/user/gold-developer). Fast, Simple, Material Design theme with inbuilt support for Q2A Blog Tool and other plugins. RTL ready.
 
-You can also [create your own themes](/themes/) using CSS only, or (optionally) [modify the HTML code](/themes/#creating-an-advanced-theme-for-question2answer).
+You can also [create your own themes]({{ site.baseurl }}/themes/) using CSS only, or (optionally) [modify the HTML code]({{ site.baseurl }}/themes/#creating-an-advanced-theme-for-question2answer).
diff --git a/addons/translations.md b/addons/translations.md
index 6f1b66a..7d1e42e 100644
--- a/addons/translations.md
+++ b/addons/translations.md
@@ -6,7 +6,7 @@ title: "Question2Answer - Add-ons - Language files"
 
 # Question2Answer Language Files
 
-The language files below are marked by the corresponding Question2Answer version. You can safely install a language file from a different version, and [update it with the missing phrases](/translate/). To install a language, place its directory (such as `fr` or `ru`) in Q2A's `qa-lang` directory, then open the General section of the Admin panel and choose the language from the menu provided.
+The language files below are marked by the corresponding Question2Answer version. You can safely install a language file from a different version, and [update it with the missing phrases]({{ site.baseurl }}/translate/). To install a language, place its directory (such as `fr` or `ru`) in Q2A's `qa-lang` directory, then open the General section of the Admin panel and choose the language from the menu provided.
 
 ## Q2A 1.8
 
@@ -89,6 +89,6 @@ The language files below are marked by the corresponding Question2Answer version
 - [Q2A 1.6.x - Ukrainian (Українська)](http://sourceforge.net/projects/q2a-lang-uk/) by Andriy Bokiy.
 - [Q2A 1.6.x - Vietnamese (Tiếng Việt)](http://annguyenco.com/hoidap/vi-qa-lang.zip) by [AnNguyenCo](http://www.annguyenco.com). Also: [Updated version](https://www.dropbox.com/s/z1gzuow0rz4rkyu/vi.zip?dl=0) by [NTHQ Team](https://namgivu.wordpress.com/2015/01/09/vietnamese-translation-for-question2answer-website/).
 
-_View [older language files](/addons/translations-old/)._
+_View [older language files]({{ site.baseurl }}/addons/translations-old/)._
 
-If your language is not listed, or is out-of-date, you can [create or update language files](/translate/) using a text editor.
+If your language is not listed, or is out-of-date, you can [create or update language files]({{ site.baseurl }}/translate/) using a text editor.
diff --git a/code/external.md b/code/external.md
index e0b2f5f..2f536ac 100644
--- a/code/external.md
+++ b/code/external.md
@@ -6,7 +6,7 @@ title: "Question2Answer - Developers - External Access"
 
 # Accessing Question2Answer from external PHP code
 
-Question2Answer provides a self-contained environment for your Q&A site. However you may wish to access parts of Q2A from other PHP code running on your server, e.g. to access the Q2A database, check if a Q2A user is logged in, or call [other functions](/code/functions/).
+Question2Answer provides a self-contained environment for your Q&A site. However you may wish to access parts of Q2A from other PHP code running on your server, e.g. to access the Q2A database, check if a Q2A user is logged in, or call [other functions]({{ site.baseurl }}/code/functions/).
 
 To access Q2A 1.3.2 or later from an external script, simply `require_once` the file `qa-include/qa-base.php` from Q2A's directory, along with any other Q2A files containing functions you need. You can then freely call any of the functions defined within these files. Each function is documented at the top of the function definition. (Note: Versions of Q2A prior to 1.3.2 also required you to define `QA_BASE_DIR` and call `qa_base_db_connect()` with a failure handler - see [here](http://www.question2answer.org/qa/4583/login-system-outside-q%26a-directory#a4608).)
 
diff --git a/code/functions.md b/code/functions.md
index aa6b6e0..185257d 100644
--- a/code/functions.md
+++ b/code/functions.md
@@ -18,7 +18,7 @@ Many of these functions take optional additional parameters which are not shown
 
 ## General functions in qa-base.php
 
-- **`qa_exit($reason)`** calls the `shutdown()` method of any installed [process modules](/plugins/modules-process/), passing the supplied `$reason`. Then it terminates execution of the PHP script with PHP's `exit;` command. Requires Q2A 1.5+.
+- **`qa_exit($reason)`** calls the `shutdown()` method of any installed [process modules]({{ site.baseurl }}/plugins/modules-process/), passing the supplied `$reason`. Then it terminates execution of the PHP script with PHP's `exit;` command. Requires Q2A 1.5+.
 - **`qa_fatal_error($message)`** outputs and logs `$message`, then calls `qa_exit('error');` to terminate execution.
 - **`qa_list_modules($type)`** returns an array containing the names of all installed modules of type `$type`.
 - **`qa_load_module($type, $name)`** returns an object belonging to the class defined in module `$name` of type `$type`, or `null` if it cannot be loaded. You can use this to communicate between multiple modules within a plugin, or between different plugins. Note that multiple calls to `qa_load_module()` with the same `$type` and `$name` will return the same object.
@@ -36,7 +36,7 @@ Many of these functions take optional additional parameters which are not shown
 - **`qa_is_https_probably()`** returns whether the current request is using the HTTPS protocol. It is hard to determine this absolutely.
 - **`qa_is_human_probably()`** returns `true` if the current request appears to be from a person using a web browser, rather than a search engine bot or automated script. This assessment is based on the HTTP user agent containing a known string such as `MSIE` or `Firefox`. Note that it is perfectly possible for a malicious bot or script to masquerade as a web browser.
 - **`qa_is_mobile_probably()`** returns `true` if the current request appears to be from a mobile phone. This assessment is based on the presence of mobile HTTP headers or the HTTP user agent containing a mobile identifying string. Requires Q2A 1.5+.
-- **`qa_lang($identifier)`** and **`qa_lang_html($identifier)`** return a localized language phrase from the appropriate `qa-lang-*.php` file. For example, `qa_lang('main/cancel_button')` would return the phrase with key `'cancel_button'` from the file `qa-lang-main.php`. The phrase returned by `qa_lang_html()` is escaped for output in HTML. From Q2A 1.5+, language files can also be [registered by plugins](/plugins/) and then accessed via these functions.
+- **`qa_lang($identifier)`** and **`qa_lang_html($identifier)`** return a localized language phrase from the appropriate `qa-lang-*.php` file. For example, `qa_lang('main/cancel_button')` would return the phrase with key `'cancel_button'` from the file `qa-lang-main.php`. The phrase returned by `qa_lang_html()` is escaped for output in HTML. From Q2A 1.5+, language files can also be [registered by plugins]({{ site.baseurl }}/plugins/) and then accessed via these functions.
 - **`qa_path_to_root()`** returns the URL to the root of the Q2A site, relative to the currently requested page. Requires Q2A 1.5+.
 - **`qa_path($request)`** returns the URL for Q2A page `$request`, relative to the currently requested page. You can also call **`qa_path($request, $params)`** to add GET-style parameters to the URL, where `$params` is an array of parameter name `=>` parameter value, not yet urlencoded. **To ensure compatibility with different Q2A URL structures, please use this (or a related `qa_path_*()` function to build URLs instead of hard-coding their structure.**
 - **`qa_path_html($request)`** and **`qa_path_html($request, $params)`** return the URL for Q2A page `$request` (with optional `$params`), relative to the currently requested page, escaped for output in HTML. Usage example:
@@ -46,7 +46,7 @@ Many of these functions take optional additional parameters which are not shown
 - **`qa_q_path($questionid, $title, $absolute, $showtype, $showid)`** and **`qa_q_path_html(...)`** return the URL for question `$questionid` which has `$title` as its title. If `$absolute` is `true`, this will be an absolute URL, otherwise it will be relative to the currently requested page. To link to a particular answer or comment within that question page, pass `'A'` or `'C'` as the `$showtype` and the `postid` of the answer or comment in `$showid`. Otherwise, pass `null` or omit these last two parameters. The URL returned by `qa_q_path_html()` is escaped for output in HTML. Requires Q2A 1.5+.
 - **`qa_self_html()`** returns the relative URL for the current Q2A page, preserving URL parameters, escaped for output in HTML. It is particularly useful for creating form tags, e.g. `echo '<FORM METHOD="POST" ACTION="'.qa_self_html().'">';`
 - **`qa_redirect($request)`** and **`qa_redirect($request, $params)`** perform an HTTP redirect to a Q2A page, specified in the same way as the parameters to `qa_path()`.
-- **`qa_redirect_raw($url)`** performs an HTTP redirect to `$url`, without processing the URL in any way. Generally you should use `qa_redirect()` however this function can be useful for [login modules](/plugins/modules-login/).
+- **`qa_redirect_raw($url)`** performs an HTTP redirect to `$url`, without processing the URL in any way. Generally you should use `qa_redirect()` however this function can be useful for [login modules]({{ site.baseurl }}/plugins/modules-login/).
 - **`qa_retrieve_url($url)`** returns the content of remote `$url`, using PHP's `file_get_contents()` or curl functions.
 - **`qa_opt($name)`** gets the value of the option labelled `$name` from Q2A's internal options storage.
 - **`qa_opt($name, $value)`** sets the option labelled `$name` to `$value` in Q2A's internal options storage. To prevent interference with Q2A or other plugins, your options should be named using a prefix which is unique to your plugin. Do not use this to store large pieces of content, since all options are retrieved for every Q2A page request - instead, look at `app/blobs.php`.
@@ -87,7 +87,7 @@ Many of these functions take optional additional parameters which are not shown
 
 Note that all `qa_post_...()` functions will send the appropriate email notifications and event reports, as well as update database indexes and counts. This can be prevented with the `qa_suspend...()` functions, described elsewhere on this page.
 
-- **`qa_post_create($type, $parentpostid, $title, $content, $format, $categoryid, $tags, $userid)`** creates a new post in the database, and returns its `postid`. Set `$type` to `'Q'` for a new question, `'A'` for an answer, or `'C'` for a comment. To queue the post for moderation (requires Q2A 1.5+), set `$type` to `'Q_QUEUED'`, `'A_QUEUED'`, or `'C_QUEUED'`. For questions, set `$parentpostid` to the `postid` of the answer to which the question is related, or `null` if (as in most cases) the question is not related to an answer. For answers, set `$parentpostid` to the `postid` of the question being answered. For comments, set `$parentpostid` to the `postid` of the question or answer to which the comment relates. The `$content` and `$format` parameters go together - if `$format` is `''` then `$content` should be in plain UTF-8 text, and if `$format` is `'html'` then `$content` should be in UTF-8 HTML. Other values of `$format` may be allowed if an appropriate [viewer module](/plugins/modules-viewer/) is installed. The `$title`, `$categoryid` and `$tags` parameters are only relevant when creating a question - `$tags` can either be an array of tags, or a string of tags separated by commas. The new post will be assigned to `$userid` if it is not `null`, otherwise it will be anonymous. Additional optional parameters set notification, extra question fields and names on anonymous posts.
+- **`qa_post_create($type, $parentpostid, $title, $content, $format, $categoryid, $tags, $userid)`** creates a new post in the database, and returns its `postid`. Set `$type` to `'Q'` for a new question, `'A'` for an answer, or `'C'` for a comment. To queue the post for moderation (requires Q2A 1.5+), set `$type` to `'Q_QUEUED'`, `'A_QUEUED'`, or `'C_QUEUED'`. For questions, set `$parentpostid` to the `postid` of the answer to which the question is related, or `null` if (as in most cases) the question is not related to an answer. For answers, set `$parentpostid` to the `postid` of the question being answered. For comments, set `$parentpostid` to the `postid` of the question or answer to which the comment relates. The `$content` and `$format` parameters go together - if `$format` is `''` then `$content` should be in plain UTF-8 text, and if `$format` is `'html'` then `$content` should be in UTF-8 HTML. Other values of `$format` may be allowed if an appropriate [viewer module]({{ site.baseurl }}/plugins/modules-viewer/) is installed. The `$title`, `$categoryid` and `$tags` parameters are only relevant when creating a question - `$tags` can either be an array of tags, or a string of tags separated by commas. The new post will be assigned to `$userid` if it is not `null`, otherwise it will be anonymous. Additional optional parameters set notification, extra question fields and names on anonymous posts.
 - **`qa_post_set_content($postid, $title, $content, $format, $tags)`** changes the data stored for post `$postid` based on any of the `$title`, `$content`, `$format` and `$tags` parameters passed which are not `null`. The meaning of these parameters is the same as for `qa_post_create()` above. Additional optional parameters allow changes to post notification, extra question fields, names on anonymous posts and can identify the user who made the change.
 - **`qa_post_set_category($postid, $categoryid)`** changes the category of `$postid` to `$categoryid`. The category of all related posts (shown together on the same question page) will also be changed.
 - **`qa_post_set_selchildid($questionid, $answerid)`** sets the selected best answer of `$questionid` to `$answerid` (or to none if `$answerid` is `null`).
diff --git a/code/structure.md b/code/structure.md
index 8f03ff4..78a594d 100644
--- a/code/structure.md
+++ b/code/structure.md
@@ -23,7 +23,7 @@ All HTTP requests for Q2A are routed through the root `index.php` file. This fil
 
 For the latter four types above, we include `qa-include/qa-base.php` which initializes the PHP environment, various constants and settings, and then connects to the database. It also defines an autoloader (from v1.7+) which automatically loads core classes of a specific format:
 
-1. From Q2A 1.9 namespaces are used. The main core namespace is `Q2A` which maps to the `qa-src/` directory. So a class of the form `\Q2A\Storage\FileCacheDriver` will automatically load the file `qa-src/Storage/FileCacheDriver.php`. See the [coding style](/contribute/coding-style/#new-autoloaded-classes) page for full details.
+1. From Q2A 1.9 namespaces are used. The main core namespace is `Q2A` which maps to the `qa-src/` directory. So a class of the form `\Q2A\Storage\FileCacheDriver` will automatically load the file `qa-src/Storage/FileCacheDriver.php`. See the [coding style]({{ site.baseurl }}/contribute/coding-style/#new-autoloaded-classes) page for full details.
 2. In Q2A 1.7-1.8, classes of the form `Q2A_Util_Usage` map to files in the `qa-include/Q2A/` directory, e.g. `qa-include/Q2A/Util/Usage.php`. These are being phased out in favor of namespaces.
 
 Here we "normalize" the request, which converts the URL from one of multiple formats (parameters or SEO-friendly) into a standard format such as `/activity` or `/question/1234/title`.
diff --git a/index.md b/index.md
index 64a2b81..50f25ce 100644
--- a/index.md
+++ b/index.md
@@ -5,4 +5,4 @@ title: "Question2Answer documentation"
 
 Welcome to the Question2Answer docs! This is a community-focused initiative to improve the documentation for Q2A. The docs contains information about installing and using Q2A, as well as developing themes/plugins and an API reference.
 
-This site is hosted via GitHub Pages, using the Jekyll static site generator. Everyone is welcome to contribute improvements - see [the contributing page](/contribute/docs/) for information about setting up Jekyll locally.
+This site is hosted via GitHub Pages, using the Jekyll static site generator. Everyone is welcome to contribute improvements - see [the contributing page]({{ site.baseurl }}/contribute/docs/) for information about setting up Jekyll locally.
diff --git a/install/index.md b/install/index.md
index ea4717e..07b4ff5 100644
--- a/install/index.md
+++ b/install/index.md
@@ -26,13 +26,13 @@ If you are not sure about this, please check with your web hosting provider.
 
 ## Installing Question2Answer for the first time (without single sign-on)
 
-The instructions below are for installing Question2Answer where it manages user accounts and logins for you. If you would like Question2Answer to integrate with your existing user database and account system, see the instructions for [single sign-on](/install/single-sign-on/) installation. From version 1.4, Question2Answer also offers easy [integration with a WordPress 3.x](/install/wordpress/) site and user database.
+The instructions below are for installing Question2Answer where it manages user accounts and logins for you. If you would like Question2Answer to integrate with your existing user database and account system, see the instructions for [single sign-on]({{ site.baseurl }}/install/single-sign-on/) installation. From version 1.4, Question2Answer also offers easy [integration with a WordPress 3.x]({{ site.baseurl }}/install/wordpress/) site and user database.
 
 1. Download the [latest version of Question2Answer](https://www.question2answer.org/question2answer-latest.zip) to your computer or web server (also available [on GitHub](https://github.com/q2a/question2answer/tree/master) - make sure to use the master branch for the latest stable version).
 
 2. Unzip the download using a tool such as [WinZip](http://www.winzip.com/) (or `unzip` in the Unix shell).
 
-3. If you want to run a non-English site, check if the appropriate [language file](/addons/) is available. If so, download and install it in the `qa-lang` folder. If not, it's simple to [translate](/translate/) Question2Answer for yourself.
+3. If you want to run a non-English site, check if the appropriate [language file]({{ site.baseurl }}/addons/) is available. If so, download and install it in the `qa-lang` folder. If not, it's simple to [translate]({{ site.baseurl }}/translate/) Question2Answer for yourself.
 
 4. Create a MySQL database, and a MySQL user with full permissions for that database.
     <small>If you're interested, the [privileges](http://dev.mysql.com/doc/mysql/en/privilege-system.html) actually needed are: CREATE, ALTER, DELETE, INSERT, SELECT, UPDATE, LOCK TABLES</small>
@@ -53,8 +53,8 @@ The instructions below are for installing Question2Answer where it manages user
 
 10. Follow the on-screen instructions to set up your database and administrator account. That's it!
 
-See also: [Upgrading Question2Answer](/install/upgrade/)
+See also: [Upgrading Question2Answer]({{ site.baseurl }}/install/upgrade/)
 
 ## Add-Ons
 
-See the [add-ons](/addons/) page for language files, themes and plugins created by Question2Answer users.
+See the [add-ons]({{ site.baseurl }}/addons/) page for language files, themes and plugins created by Question2Answer users.
diff --git a/install/single-sign-on.md b/install/single-sign-on.md
index 493f9be..9da1ca7 100644
--- a/install/single-sign-on.md
+++ b/install/single-sign-on.md
@@ -6,7 +6,7 @@ title: "Question2Answer - Single Sign-On Integration"
 
 # Installing Question2Answer with single sign-on
 
-Question2Answer is designed to integrate with websites which have an existing user database and management system. If your site is running WordPress 3.x, you should follow the instructions for [WordPress integration](/install/wordpress/). To implement single sign-on for other sites, a small amount of PHP programming is required. Please follow the instructions below:
+Question2Answer is designed to integrate with websites which have an existing user database and management system. If your site is running WordPress 3.x, you should follow the instructions for [WordPress integration]({{ site.baseurl }}/install/wordpress/). To implement single sign-on for other sites, a small amount of PHP programming is required. Please follow the instructions below:
 
 1. Download the [latest version of Question2Answer](https://github.com/q2a/question2answer/releases) to your computer or web server (also available [on GitHub](https://github.com/q2a/question2answer)).
 
diff --git a/install/upgrade.md b/install/upgrade.md
index a2edeb9..c1e56d7 100644
--- a/install/upgrade.md
+++ b/install/upgrade.md
@@ -6,7 +6,7 @@ title: "Upgrading Question2Answer"
 
 # Upgrading to the latest version of Question2Answer
 
-Question2Answer regularly has [new releases](/install/versions/) that fix bugs and add new features. Updating your Q2A site is usually a simple process of uploading the new files and visiting your site to check for any database upgrades. Instructions in more detail:
+Question2Answer regularly has [new releases]({{ site.baseurl }}/install/versions/) that fix bugs and add new features. Updating your Q2A site is usually a simple process of uploading the new files and visiting your site to check for any database upgrades. Instructions in more detail:
 
 1. Before upgrading, it is recommended to make a backup of your website, and of your MySQL database using `mysqldump` or a similar tool.
 
diff --git a/install/versions/index.md b/install/versions/index.md
index 1cc351a..d4307b4 100644
--- a/install/versions/index.md
+++ b/install/versions/index.md
@@ -140,7 +140,7 @@ First beta of major feature release, 26th September 2017.
 - Performance has been improved by around 20% on average (even more on questions with many answers).
 - Added caching system. Currently caches question data, related questions and category list for anonymous users. Caches can be stored in files or in memory (requires Memcached PHP extension).
 - Added comment voting. Comments may be voted up or down, and points may be given as with answers (default is no points).
-- Added ability to enable/disable plugins. For backwards compatibility, by default plugins cannot be disabled (except by removing the plugin folder entirely). Plugin developers must "opt-in" to this feature using the `load_order` property in the plugin's `metadata.json`. See the [plugin documentation](/plugins/#plugin-metadata).
+- Added ability to enable/disable plugins. For backwards compatibility, by default plugins cannot be disabled (except by removing the plugin folder entirely). Plugin developers must "opt-in" to this feature using the `load_order` property in the plugin's `metadata.json`. See the [plugin documentation]({{ site.baseurl }}/plugins/#plugin-metadata).
 - Added support for IPv6 addresses.
 - Schema.org microdata is now used throughout Q2A.
 - Number formatting characters (decimal point, thousands separator) can be specified in language files.
@@ -434,4 +434,4 @@ First community-developed version of Question2Answer, 6th November 2014.
 - `qa-theme-base.php/ranking_spacer`: same as above.
 
 
-## [Changelog for older versions](/install/versions/1/)
+## [Changelog for older versions]({{ site.baseurl }}/install/versions/1/)
diff --git a/install/wordpress.md b/install/wordpress.md
index eff276c..84b65e0 100644
--- a/install/wordpress.md
+++ b/install/wordpress.md
@@ -52,4 +52,4 @@ From version 1.4, Question2Answer offers out-of-the-box integration with your [W
 
 8. Follow the on-screen instructions to set up your database and Question2Answer functionality.
 
-9. You can now integrate the styling of Question2Answer with your WordPress site by [creating a Question2Answer theme](/themes/).
+9. You can now integrate the styling of Question2Answer with your WordPress site by [creating a Question2Answer theme]({{ site.baseurl }}/themes/).
diff --git a/plugins/index.md b/plugins/index.md
index 14417f6..6e3c3d6 100644
--- a/plugins/index.md
+++ b/plugins/index.md
@@ -8,26 +8,26 @@ title: "Question2Answer - Developers - Creating Plugins"
 
 Question2Answer plugins (introduced in Q2A 1.3) allow the platform to be modified or extended without changing the Q2A core. Plugins can integrate with Q2A in one of three ways:
 
-- **[Modules](/plugins/modules/) extend Q2A in a defined and specific way.** The following types of module are supported:
-    - [*page*](/plugins/modules-page/) modules add a new type of page to a Question2Answer site.
-    - [*login*](/plugins/modules-login/) modules allow users to log in to Q2A via an external identity provider such as Facebook.
-    - [*editor*](/plugins/modules-editor/) modules provide a web interface for writing and editing posts.
-    - [*viewer*](/plugins/modules-viewer/) modules render content as HTML or text, and often work together with an editor module.
-    - [*event*](/plugins/modules-event/) modules are notified when something important happens, such as content being posted or voted on.
-    - [*widget*](/plugins/modules-widget/) modules allow extra content to be shown on Q2A pages, as chosen by the site administrator.
-    - [*filter*](/plugins/modules-filter/) modules can validate and/or modify many types of user input, including the content of posts.
-    - [*search*](/plugins/modules-search/) modules can implement a custom indexer and/or search engine for a Q2A site.
-    - [*captcha*](/plugins/modules-captcha/) modules provide a web interface for human verification, such as reCAPTCHA.
-    - [*process*](/plugins/modules-process/) modules have the opportunity to run at specific stages of Q2A's response processing.
+- **[Modules]({{ site.baseurl }}/plugins/modules/) extend Q2A in a defined and specific way.** The following types of module are supported:
+    - [*page*]({{ site.baseurl }}/plugins/modules-page/) modules add a new type of page to a Question2Answer site.
+    - [*login*]({{ site.baseurl }}/plugins/modules-login/) modules allow users to log in to Q2A via an external identity provider such as Facebook.
+    - [*editor*]({{ site.baseurl }}/plugins/modules-editor/) modules provide a web interface for writing and editing posts.
+    - [*viewer*]({{ site.baseurl }}/plugins/modules-viewer/) modules render content as HTML or text, and often work together with an editor module.
+    - [*event*]({{ site.baseurl }}/plugins/modules-event/) modules are notified when something important happens, such as content being posted or voted on.
+    - [*widget*]({{ site.baseurl }}/plugins/modules-widget/) modules allow extra content to be shown on Q2A pages, as chosen by the site administrator.
+    - [*filter*]({{ site.baseurl }}/plugins/modules-filter/) modules can validate and/or modify many types of user input, including the content of posts.
+    - [*search*]({{ site.baseurl }}/plugins/modules-search/) modules can implement a custom indexer and/or search engine for a Q2A site.
+    - [*captcha*]({{ site.baseurl }}/plugins/modules-captcha/) modules provide a web interface for human verification, such as reCAPTCHA.
+    - [*process*]({{ site.baseurl }}/plugins/modules-process/) modules have the opportunity to run at specific stages of Q2A's response processing.
 
-    Modules are the preferred method for extending Q2A - [more about modules](/plugins/modules/).
+    Modules are the preferred method for extending Q2A - [more about modules]({{ site.baseurl }}/plugins/modules/).
 
-- **[Layers](/plugins/layers/) modify the HTML output for some elements of a Q2A page**. Layers work similarly to [advanced themes](/themes/), by overriding some functions in the base theme class in `qa-theme-base.php`. Unlike advanced themes, multiple layers can be installed simultaneously via their respective plugins. Layers require Q2A 1.4+.
-- **[Overrides](/plugins/overrides/) allow over 150 core Q2A functions to be modified**. Core functions can be replaced by the plugin's code, or they can be wrapped, with the plugin modifying the function's inputs and/or outputs. With wrapping, multiple overrides for the same function in different plugins can be active simultaneously. Overrides require Q2A 1.5+.
+- **[Layers]({{ site.baseurl }}/plugins/layers/) modify the HTML output for some elements of a Q2A page**. Layers work similarly to [advanced themes]({{ site.baseurl }}/themes/), by overriding some functions in the base theme class in `qa-theme-base.php`. Unlike advanced themes, multiple layers can be installed simultaneously via their respective plugins. Layers require Q2A 1.4+.
+- **[Overrides]({{ site.baseurl }}/plugins/overrides/) allow over 150 core Q2A functions to be modified**. Core functions can be replaced by the plugin's code, or they can be wrapped, with the plugin modifying the function's inputs and/or outputs. With wrapping, multiple overrides for the same function in different plugins can be active simultaneously. Overrides require Q2A 1.5+.
 
-The sections below explain the general principles behind plugins. You will also need to read about implementing [modules](/plugins/modules/), [layers](/plugins/layers/) and/or [overrides](/plugins/overrides/), as well as some [functions](/code/functions/) in Q2A that may be useful in developing your plugin.
+The sections below explain the general principles behind plugins. You will also need to read about implementing [modules]({{ site.baseurl }}/plugins/modules/), [layers]({{ site.baseurl }}/plugins/layers/) and/or [overrides]({{ site.baseurl }}/plugins/overrides/), as well as some [functions]({{ site.baseurl }}/code/functions/) in Q2A that may be useful in developing your plugin.
 
-An alternative is to work through the [plugin tutorial](/plugins/tutorial/), which introduces all of this material in a more gentle and gradual way.
+An alternative is to work through the [plugin tutorial]({{ site.baseurl }}/plugins/tutorial/), which introduces all of this material in a more gentle and gradual way.
 
 To see some examples of plugins, modules and layers, take a look at the `qa-plugin` directory in your Q2A installation as well as the modules registered in the function `qa_register_core_modules()` in `qa-base.php` of Q2A 1.5+.
 
@@ -41,11 +41,11 @@ Plugins for Question2Answer have the following directory structure:
 - The plugin directory may also contain any other files and subdirectories, including PHP, HTML, Javascript, CSS, etc...
 - A plugin is activated by installing its directory inside Q2A's `qa-plugin` directory.
 
-The `qa-plugin.php` file has two main purposes. First, it registers any modules, layers or overrides provided by the plugin. Second, it contains optional metadata about the plugin and its author. As of Q2A 1.5, it is not recommended for `qa-plugin.php` to perform any other actions - if this seems necessary, please consider using a [process module](/plugins/modules-process/) instead. If you wish to use non English characters in `qa-plugin.php`, ensure your text editor is using UTF-8 encoding without a BOM (byte order mark).
+The `qa-plugin.php` file has two main purposes. First, it registers any modules, layers or overrides provided by the plugin. Second, it contains optional metadata about the plugin and its author. As of Q2A 1.5, it is not recommended for `qa-plugin.php` to perform any other actions - if this seems necessary, please consider using a [process module]({{ site.baseurl }}/plugins/modules-process/) instead. If you wish to use non English characters in `qa-plugin.php`, ensure your text editor is using UTF-8 encoding without a BOM (byte order mark).
 
 ## Registering modules
 
-Each module is implemented as a PHP `class` with specific member functions, as [detailed here](/plugins/modules/). For the sake of speed, the class definition for each module should be in a separate PHP file, since Q2A will only `include` this file when necessary.
+Each module is implemented as a PHP `class` with specific member functions, as [detailed here]({{ site.baseurl }}/plugins/modules/). For the sake of speed, the class definition for each module should be in a separate PHP file, since Q2A will only `include` this file when necessary.
 
 To register a module, call `qa_register_plugin_module()` in `qa-plugin.php`, with the following parameters in order:
 
@@ -56,18 +56,18 @@ To register a module, call `qa_register_plugin_module()` in `qa-plugin.php`, wit
 
 ## Registering layers
 
-Each layer is implemented as a PHP file containing a fixed `class` declaration, as [described here](/plugins/layers/). To register a layer, call `qa_register_plugin_layer()` in `qa-plugin.php`, with the following parameters in order:
+Each layer is implemented as a PHP file containing a fixed `class` declaration, as [described here]({{ site.baseurl }}/plugins/layers/). To register a layer, call `qa_register_plugin_layer()` in `qa-plugin.php`, with the following parameters in order:
 
 1. The name of the PHP file in the plugin directory containing the layer's class declaration, e.g. `qa-mouseover-layer.php`.
 2. A human-readable layer name, which should be descriptive and unique, e.g. `'Mouseover Layer'`. This may also be used to refer to the layer within Q2A's internals.
 
 ## Registering overrides
 
-Overrides are implemented as PHP files which contain the replacement function definitions, as [described here](/plugins/overrides/). Your functions can call the original Q2A functions using the `_base` suffix, e.g. `qa_lang_base()`. To register a file containing overrides, call `qa_register_plugin_overrides()` in `qa-plugin.php` with the name of the overrides PHP file in the plugin directory.
+Overrides are implemented as PHP files which contain the replacement function definitions, as [described here]({{ site.baseurl }}/plugins/overrides/). Your functions can call the original Q2A functions using the `_base` suffix, e.g. `qa_lang_base()`. To register a file containing overrides, call `qa_register_plugin_overrides()` in `qa-plugin.php` with the name of the overrides PHP file in the plugin directory.
 
 ## Plugin localization
 
-Throughout Q2A, the [functions](/code/functions/) `qa_lang()` and `qa_lang_html()` are used to obtain localized language phrases. An identifier string is passed to these functions, which consists of a file prefix, a slash (`/`) and a phrase key. For example, the identifier `'main/cancel_button'` obtains the element with key `'cancel_button'` from the appropriate `qa-lang-main.php` language file. Each language file is a PHP script which returns an array mapping keys to phrases, e.g. see `qa-lang-main.php`. If you wish to use non English characters in your language files, ensure your text editor is using UTF-8 encoding without a BOM (byte order mark).
+Throughout Q2A, the [functions]({{ site.baseurl }}/code/functions/) `qa_lang()` and `qa_lang_html()` are used to obtain localized language phrases. An identifier string is passed to these functions, which consists of a file prefix, a slash (`/`) and a phrase key. For example, the identifier `'main/cancel_button'` obtains the element with key `'cancel_button'` from the appropriate `qa-lang-main.php` language file. Each language file is a PHP script which returns an array mapping keys to phrases, e.g. see `qa-lang-main.php`. If you wish to use non English characters in your language files, ensure your text editor is using UTF-8 encoding without a BOM (byte order mark).
 
 From Q2A 1.5+, plugins can add their own language prefixes and phrases by calling `qa_register_plugin_phrases()` from within `qa-plugin.php`, with the following parameters in order:
 
diff --git a/plugins/layers.md b/plugins/layers.md
index d2dc554..78c51c5 100644
--- a/plugins/layers.md
+++ b/plugins/layers.md
@@ -16,9 +16,9 @@ class qa_html_theme_layer extends qa_html_theme_base
 }
 ```
 
-Layers work similarly to [advanced themes](/themes/), except multiple layers can be installed simultaneously via their respective plugins. The PHP code for each layer is automatically modified at runtime (by `qa_load_theme_class()` in `qa-app-format.php`) to build an inheritance chain of appropriately renamed classes. This process is transparent to you as a layer developer. If you wish to use non English characters in your layer, ensure your text editor is using UTF-8 encoding without a BOM (byte order mark).
+Layers work similarly to [advanced themes]({{ site.baseurl }}/themes/), except multiple layers can be installed simultaneously via their respective plugins. The PHP code for each layer is automatically modified at runtime (by `qa_load_theme_class()` in `qa-app-format.php`) to build an inheritance chain of appropriately renamed classes. This process is transparent to you as a layer developer. If you wish to use non English characters in your layer, ensure your text editor is using UTF-8 encoding without a BOM (byte order mark).
 
-For more information on how to override theme functions in your layer class declaration, **start at step 3** of the documentation for [advanced themes](/themes/). When overriding functions in your layer, you should use PHP's double colon (`::`) notation to call through to the parent class as much as possible. This will maximize the chance of your layer working well with advanced themes, layers in other plugins, and future versions of Question2Answer.
+For more information on how to override theme functions in your layer class declaration, **start at step 3** of the documentation for [advanced themes]({{ site.baseurl }}/themes/). When overriding functions in your layer, you should use PHP's double colon (`::`) notation to call through to the parent class as much as possible. This will maximize the chance of your layer working well with advanced themes, layers in other plugins, and future versions of Question2Answer.
 
 Within a plugin's layer PHP file, the following pseudo-constants (substituted for strings at runtime) might prove useful:
 
diff --git a/plugins/modules-captcha.md b/plugins/modules-captcha.md
index f45a15d..bc17030 100644
--- a/plugins/modules-captcha.md
+++ b/plugins/modules-captcha.md
@@ -6,7 +6,7 @@ title: "Question2Answer - Developers - Captcha Modules"
 
 # Captcha Modules
 
-[« Back to modules](/plugins/modules/)
+[« Back to modules]({{ site.baseurl }}/plugins/modules/)
 
 A captcha module (requires Q2A 1.5+) provides a web interface for verifying that a user is a human, rather than an automated script generating spam. The [captcha](http://en.wikipedia.org/wiki/CAPTCHA) should provide a challenge that is easy for humans but difficult for computers, such as reading some warped text or answering a common sense question.
 
@@ -16,4 +16,4 @@ The PHP `class` for a captcha module should contain the following functions (all
 - **`form_html(&$qa_content, $error)`**. This function returns the HTML form to be displayed for the captcha challenge. You can use hidden fields in this form to provide any information required by `validate_post()` - see below. If `$error` is not `null`, it contains an error message that should be displayed with the captcha, as passed out previously by your `validate_post()` function. You can also inject elements (such as Javascript) into the global `$qa_content` array for the page - see `qa-plugin/recaptcha-captcha/qa-recaptcha-captcha.php` for an example, or [ask here](http://www.question2answer.org/qa/). Note that if a captcha is required in multiple places on a web page, Q2A will only call `form_html()` once, and will take care of moving the captcha around the page as appropriate. This means your captcha must continue to work even if it was moved inside the [DOM](http://en.wikipedia.org/wiki/Document_Object_Model).
 - **`validate_post(&$error)`**. This function returns whether the user responded to the captcha correctly. The function should retrieve the necessary form fields from PHP's `$_POST` array or Q2A's `qa_post_text()` function, and then perform the appropriate verification. Return `true` if the verification succeeded, otherwise `false`. If verification failed, you should also set `$error` to a textual error message which will passed back to `form_html()` for display to the user.
 
-[« Back to modules](/plugins/modules/)
+[« Back to modules]({{ site.baseurl }}/plugins/modules/)
diff --git a/plugins/modules-editor.md b/plugins/modules-editor.md
index b30a38a..8cf7344 100644
--- a/plugins/modules-editor.md
+++ b/plugins/modules-editor.md
@@ -6,11 +6,11 @@ title: "Question2Answer - Developers - Editor Modules"
 
 # Editor Modules
 
-[« Back to modules](/plugins/modules/)
+[« Back to modules]({{ site.baseurl }}/plugins/modules/)
 
 An editor module implements a web interface for editing the content of questions, answers and comments. The module controls the HTML field which is displayed for editing, and converts the input from that field into data for storage in Q2A's database.
 
-For example, the default editor module in `qa-editor-basic.php` displays a simple text field and generates text content for storage. The WYSIWYG Editor plugin included with Q2A wraps [CKEditor](http://ckeditor.com/) and generates text or HTML content for storage. Your editor can also store content in a format other than text or HTML, but a [viewer module](/plugins/modules-viewer/) will be required to render that content for Q2A.
+For example, the default editor module in `qa-editor-basic.php` displays a simple text field and generates text content for storage. The WYSIWYG Editor plugin included with Q2A wraps [CKEditor](http://ckeditor.com/) and generates text or HTML content for storage. Your editor can also store content in a format other than text or HTML, but a [viewer module]({{ site.baseurl }}/plugins/modules-viewer/) will be required to render that content for Q2A.
 
 The PHP `class` for an editor module must contain the following functions (all are **required**):
 
@@ -18,7 +18,7 @@ The PHP `class` for an editor module must contain the following functions (all a
 
 - **`get_field(&$qa_content, $content, $format, $fieldname, $rows)`** should return an HTML-based field for your editor. The `$content` and `$format` parameters specify the content that needs editing or `null` if new content is being created. The `$fieldname` parameter contains the HTML element name that you should use - if your editor outputs multiple HTML elements, use `$fieldname` as a prefix. The `$rows` parameter indicates a suggested height for your editor, in lines of text. To output custom HTML for your editor, return `array('type' => 'custom', 'html' => '[the html]')` from this function. You can also return an array representing any standard Q2A form field and inject elements (such as Javascript) into the `$qa_content` array - see `qa-editor-basic.php` and `qa-wysiwyg-editor.php` for some examples, or [ask here](http://www.question2answer.org/qa/).
 
-- **`read_post($fieldname)`** should retrieve the content from your editor, as POSTed from the user's web browser, and convert it for storage in Q2A's database. The `$fieldname` parameter matches the value that was previously passed to `get_field()`. To store plain text, return `array('format' => '', 'content' => '[text in UTF-8]')` from this function. To store HTML, return `array('format' => 'html', 'content' => '[html in UTF-8]')`. **If you are storing HTML as submitted by the user's browser, you must sanitize it using `qa_sanitize_html()` to prevent Javascript injection and other security issues.** Aside from plain text and HTML, your `read_post()` function can store any other type of content in Q2A's database, by supplying an appropriate `'format'` (up to 20 ASCII characters in length) and corresponding `'content'`. In this case, a [viewer module](/plugins/modules-viewer/) will be required to render the stored content as plain text or HTML.
+- **`read_post($fieldname)`** should retrieve the content from your editor, as POSTed from the user's web browser, and convert it for storage in Q2A's database. The `$fieldname` parameter matches the value that was previously passed to `get_field()`. To store plain text, return `array('format' => '', 'content' => '[text in UTF-8]')` from this function. To store HTML, return `array('format' => 'html', 'content' => '[html in UTF-8]')`. **If you are storing HTML as submitted by the user's browser, you must sanitize it using `qa_sanitize_html()` to prevent Javascript injection and other security issues.** Aside from plain text and HTML, your `read_post()` function can store any other type of content in Q2A's database, by supplying an appropriate `'format'` (up to 20 ASCII characters in length) and corresponding `'content'`. In this case, a [viewer module]({{ site.baseurl }}/plugins/modules-viewer/) will be required to render the stored content as plain text or HTML.
 
 In addition, the following **optional** functions may also be defined (all require Q2A 1.5+):
 
@@ -28,4 +28,4 @@ In addition, the following **optional** functions may also be defined (all requi
 
 - **`update_script($fieldname)`** can return a Javascript that prepares the editor content for submission via the enclosing form (requires Q2A 1.5+). If your editor manipulates content outside the form's field, e.g. in an iframe, this allows it to update the field content immediately before the form is submitted.
 
-[« Back to modules](/plugins/modules/)
+[« Back to modules]({{ site.baseurl }}/plugins/modules/)
diff --git a/plugins/modules-event.md b/plugins/modules-event.md
index 851af9c..39775b9 100644
--- a/plugins/modules-event.md
+++ b/plugins/modules-event.md
@@ -6,7 +6,7 @@ title: "Question2Answer - Developers - Event Modules"
 
 # Event Modules
 
-[« Back to modules](/plugins/modules/)
+[« Back to modules]({{ site.baseurl }}/plugins/modules/)
 
 An event module (requires Q2A 1.4+) is notified when something important happens within Q2A. It can be used to react to this event in any way it wishes. The PHP class for an event module must contain the following function to react to events:
 
@@ -88,4 +88,4 @@ Below is a list of possible values for `$event` and the event that each value de
 
 - `'search'` when a search is performed. The search query is in `$params['query']` and the start position in `$params['start']`.
 
-[« Back to modules](/plugins/modules/)
+[« Back to modules]({{ site.baseurl }}/plugins/modules/)
diff --git a/plugins/modules-filter.md b/plugins/modules-filter.md
index 78848a3..824fa1a 100644
--- a/plugins/modules-filter.md
+++ b/plugins/modules-filter.md
@@ -6,7 +6,7 @@ title: "Question2Answer - Developers - Filter Modules"
 
 # Filter Modules
 
-[« Back to modules](/plugins/modules/)
+[« Back to modules]({{ site.baseurl }}/plugins/modules/)
 
 A filter module (requires Q2A 1.5+) enables plugins to validate and/or modify many different types of user input. This includes the content of posts as well as user information such as usernames and email addresses. Filter modules can also control whether or not the post is queued for moderation. Possible applications of filter modules include cleaning up user input, restricting users of a site, creating specialized Q&A applications, and advanced spam checking.
 
@@ -36,7 +36,7 @@ The PHP class for a filter module may contain the following functions (all are o
 		</tr>
 		<tr>
 			<td>`'editor'`</td>
-			<td>The name of the [editor module](/plugins/modules-editor/) used</td>
+			<td>The name of the [editor module]({{ site.baseurl }}/plugins/modules-editor/) used</td>
 			<td>No</td>
 			<td>No</td>
 			<td>Maybe</td>
@@ -133,4 +133,4 @@ The PHP class for a filter module may contain the following functions (all are o
 
 - **`validate_password($password, $olduser)`**. This allows a filter module to validate an entered password for new or existing Q2A user accounts. The `$password` parameter contains the password entered. Note than unlike other filter module functions, `validate_password()` cannot modify a password, but rather only validate it. The function can declare the pssword invalid by returning a textual error, otherwise it should return `null`. For your reference, if the password is for an existing user, `$olduser` contains an array of information about the user, but this will not contain the user's previous password, since Q2A doesn't store passwords in their original form. If the password is for a new user, `$olduser` will be `null`.
 
-[« Back to modules](/plugins/modules/)
+[« Back to modules]({{ site.baseurl }}/plugins/modules/)
diff --git a/plugins/modules-login.md b/plugins/modules-login.md
index db92f47..9b2e403 100644
--- a/plugins/modules-login.md
+++ b/plugins/modules-login.md
@@ -6,7 +6,7 @@ title: "Question2Answer - Developers - Login Modules"
 
 # Login Modules
 
-[« Back to modules](/plugins/modules/)
+[« Back to modules]({{ site.baseurl }}/plugins/modules/)
 
 A login module enables users to log in to Q2A via an external identity provider, such as [Open ID](http://openid.net/). The module can display some HTML alongside Q2A's login and register links in the navigation menu, and/or on Q2A's login and register pages. This HTML can use a variety of methods to obtain the user's credentials, such as linking to a separate form or showing a pop-up via Javascript.
 
@@ -39,6 +39,6 @@ The PHP `class` for a login module can contain the following functions (all are
 
 - **`logout_html($tourl)`** allows your module to display some HTML for logging out the user, to be displayed in the top right menu. Your `logout_html()` function is only called if the current Q2A user was logged in via `qa_log_in_external_user()` and your `match_source()` function returns `true` for the `$source` value that was used. The `$tourl` parameter contains the URL of the Q2A logout page, to which you **must** redirect the user once your own logout process is complete.
 
-You may choose to request the user's external login credentials on a page which is served by Q2A. In this case you would include both a login module and a [page module](/plugins/modules-page/) in your plugin. The HTML displayed by the login module would link to your custom page, and the page module would display the appropriate form and call `qa_log_in_external_user()` when the form was submitted.
+You may choose to request the user's external login credentials on a page which is served by Q2A. In this case you would include both a login module and a [page module]({{ site.baseurl }}/plugins/modules-page/) in your plugin. The HTML displayed by the login module would link to your custom page, and the page module would display the appropriate form and call `qa_log_in_external_user()` when the form was submitted.
 
-[« Back to modules](/plugins/modules/)
+[« Back to modules]({{ site.baseurl }}/plugins/modules/)
diff --git a/plugins/modules-page.md b/plugins/modules-page.md
index 19dd255..613bfa6 100644
--- a/plugins/modules-page.md
+++ b/plugins/modules-page.md
@@ -6,7 +6,7 @@ title: "Question2Answer - Developers - Plugin Modules"
 
 # Page Modules
 
-[« Back to modules](/plugins/modules/)
+[« Back to modules]({{ site.baseurl }}/plugins/modules/)
 
 A page module adds one or more new pages to a Q2A installation. In Q2A, every page displayed has a corresponding `$request` string. For example, the `$request` for Q2A's page for user John Doe is `'user/John Doe'`. Page modules are able to control the output for particular `$request` strings in the same way. (Depending on the chosen URL structure for a Q2A installation, `$request` can be represented in different ways on the actual URL - you need not worry about this, nor should you make any assumptions.)
 
@@ -26,8 +26,8 @@ The PHP `class` for a page module can contain the following functions (all are o
     - All elements within the nested `$qa_content` array should be made HTML safe - use `qa_html()` as appropriate.
     - Use `$qa_content['title']` and `$qa_content['error']` to display a page title or error message respectively.
     - To add some custom HTML to the page, add an element to `$qa_content` whose key begins with `custom`, e.g. `$qa_content['custom']` or `$qa_content['custom_2']`. The value of the element should contain the actual HTML.
-    - To add a Q2A-style form to the page, add an element to `$qa_content` whose key begins with `form`, e.g. `$qa_content['form']` or `$qa_content['form_2']`. The value of the element should contain a Q2A form array, whose definition is also beyond the scope of this documentation, although see the [comments here](/plugins/modules/).
+    - To add a Q2A-style form to the page, add an element to `$qa_content` whose key begins with `form`, e.g. `$qa_content['form']` or `$qa_content['form_2']`. The value of the element should contain a Q2A form array, whose definition is also beyond the scope of this documentation, although see the [comments here]({{ site.baseurl }}/plugins/modules/).
     - Other possible types of structured content in `$qa_content` are question lists (keys starting `q_list`), question views (`q_view`), answer lists (`a_list`) and rankings (`ranking`). Look through the `qa-page-*.php` files for examples.
     - The elements in `$qa_content` are displayed in array order, with a few exceptions such as page titles and errors.
 
-[« Back to modules](/plugins/modules/)
+[« Back to modules]({{ site.baseurl }}/plugins/modules/)
diff --git a/plugins/modules-process.md b/plugins/modules-process.md
index f99a98a..beef155 100644
--- a/plugins/modules-process.md
+++ b/plugins/modules-process.md
@@ -6,7 +6,7 @@ title: "Question2Answer - Developers - Process Modules"
 
 # Process Modules
 
-[« Back to modules](/plugins/modules/)
+[« Back to modules]({{ site.baseurl }}/plugins/modules/)
 
 A process module (requires Q2A 1.5+) can perform any task at specific stages of Q2A's response processing. For example, process modules could provide logging, implement a page cache, change database settings, or perform extra user authentication.
 
@@ -32,4 +32,4 @@ The PHP `class` for a process module can define one or more of the following fun
 
 - **`shutdown($reason)`** will be called at the end of Q2A's response processing. The `$reason` parameter will be `'error'` if an error occurred, `'redirect'` if there was a redirection, otherwise it will be `null`. More values may be added in future.
 
-[« Back to modules](/plugins/modules/)
+[« Back to modules]({{ site.baseurl }}/plugins/modules/)
diff --git a/plugins/modules-search.md b/plugins/modules-search.md
index c271454..ad20d5b 100644
--- a/plugins/modules-search.md
+++ b/plugins/modules-search.md
@@ -6,13 +6,13 @@ title: "Question2Answer - Developers - Search Modules"
 
 # Search Modules
 
-[« Back to modules](/plugins/modules/)
+[« Back to modules]({{ site.baseurl }}/plugins/modules/)
 
 A search module (requires Q2A 1.5+) enables plugins to create a custom index of the content in a Q2A site, including questions, answers, comments and custom pages. If a search module is selected by the site administrator, it can replace the default Q2A search results with its own, and optionally include pages from external websites in those results.
 
 The PHP class for a search module may contain the following functions (all are optional):
 
-- **`index_post($postid, $type, $questionid, $parentid, $title, $content, $format, $text, $tagstring, $categoryid)`**. If defined, this function is called when a post should be added to the search index, either because it is new, or because it has just been edited. The parameter `$postid` contains the `postid` from the database. The `$type` will be `'Q'` for questions, `'A'` for answers, `'C'` for comments or `'NOTE'` for a note (currently used for question closing explanations). The `$questionid` is the `postid` of the question to which the post belongs and the `$parentid` is the `postid` of its immediate parent, or `null` if it has none. For questions, `$title` contains the title in UTF-8 format, otherwise it is `null`. The `$content` and `$format` parameters describe the post's content. If `$format` is `''`, then `$content` contains plain text in UTF-8 encoding. If `$format` is `'html'`, then `$content` contains HTML with UTF-8 encoding. Other values of `$format` may be present if a non-standard [editor module](/plugins/modules-editor/) is installed. The `$text` parameter contains a UTF-8 plain text rendering of the post, which is particularly useful for building a search index. For questions, `$tagstring` contains a comma-separated list of tags, otherwise it is `null`. Finally, `$categoryid` contains the category ID of the post, or `null` if there is none. Note that `index_post()` is only called when a post has been made visible on the Q2A site - it is not called if a new post was marked for moderation.
+- **`index_post($postid, $type, $questionid, $parentid, $title, $content, $format, $text, $tagstring, $categoryid)`**. If defined, this function is called when a post should be added to the search index, either because it is new, or because it has just been edited. The parameter `$postid` contains the `postid` from the database. The `$type` will be `'Q'` for questions, `'A'` for answers, `'C'` for comments or `'NOTE'` for a note (currently used for question closing explanations). The `$questionid` is the `postid` of the question to which the post belongs and the `$parentid` is the `postid` of its immediate parent, or `null` if it has none. For questions, `$title` contains the title in UTF-8 format, otherwise it is `null`. The `$content` and `$format` parameters describe the post's content. If `$format` is `''`, then `$content` contains plain text in UTF-8 encoding. If `$format` is `'html'`, then `$content` contains HTML with UTF-8 encoding. Other values of `$format` may be present if a non-standard [editor module]({{ site.baseurl }}/plugins/modules-editor/) is installed. The `$text` parameter contains a UTF-8 plain text rendering of the post, which is particularly useful for building a search index. For questions, `$tagstring` contains a comma-separated list of tags, otherwise it is `null`. Finally, `$categoryid` contains the category ID of the post, or `null` if there is none. Note that `index_post()` is only called when a post has been made visible on the Q2A site - it is not called if a new post was marked for moderation.
 
 - **`unindex_post($postid)`**. If defined, this function is called when a post should be removed from the search index, because it has been hidden, deleted, or is about to be edited (in which case `index_post()` will be called immediately after). Generally, the parameter `$postid` matches a value previously passed to `index_post()` when the post was indexed. However in some circumstances the `$postid` might never have been indexed, in which case the function should do nothing.
 
@@ -33,4 +33,4 @@ The PHP class for a search module may contain the following functions (all are o
 
     To save additional database queries, it is also possible to pass through more information about a matching question, post or page in `'question'`, `'match_type'` or `'page'` elements. This requires knowledge of Q2A's internals - see `qa-app-search.php` for more information on how these elements are used with the `$fullcontent` parameter.
 
-[« Back to modules](/plugins/modules/)
+[« Back to modules]({{ site.baseurl }}/plugins/modules/)
diff --git a/plugins/modules-viewer.md b/plugins/modules-viewer.md
index 925dc7a..7ee4973 100644
--- a/plugins/modules-viewer.md
+++ b/plugins/modules-viewer.md
@@ -6,9 +6,9 @@ title: "Question2Answer - Developers - Viewer Modules"
 
 # Viewer Modules
 
-[« Back to modules](/plugins/modules/)
+[« Back to modules]({{ site.baseurl }}/plugins/modules/)
 
-A viewer module takes content stored in the database, as generated by an [editor module](/plugins/modules-editor/), and renders it for display by Q2A. The default viewer module in `qa-viewer-basic.php` takes care of rendering stored text or HTML, so you will only need to create a viewer module if you have an editor module which stores content in a different format.
+A viewer module takes content stored in the database, as generated by an [editor module]({{ site.baseurl }}/plugins/modules-editor/), and renders it for display by Q2A. The default viewer module in `qa-viewer-basic.php` takes care of rendering stored text or HTML, so you will only need to create a viewer module if you have an editor module which stores content in a different format.
 
 The PHP `class` for a viewer module must contain the following functions (all are **required**):
 
@@ -22,4 +22,4 @@ The PHP `class` for a viewer module must contain the following functions (all ar
 
 - **`get_text($content, $format, $options)`** should take the supplied `$content` in `$format` and render it as plain text with UTF-8 encoding. The text is primarily used in notification emails and for search indexing. `$options['blockwordspreg']` should be treated in the same way as for `get_html()`.
 
-[« Back to modules](/plugins/modules/)
+[« Back to modules]({{ site.baseurl }}/plugins/modules/)
diff --git a/plugins/modules-widget.md b/plugins/modules-widget.md
index 522eac9..ad2dcaf 100644
--- a/plugins/modules-widget.md
+++ b/plugins/modules-widget.md
@@ -6,7 +6,7 @@ title: "Question2Answer - Developers - Widget Modules"
 
 # Widget Modules
 
-[« Back to modules](/plugins/modules/)
+[« Back to modules]({{ site.baseurl }}/plugins/modules/)
 
 A widget module (requires Q2A 1.4+) displays some extra HTML content on one or more of Q2A's pages. The widget specifies which types of pages ("templates") it can be displayed on, and where it can be displayed on the page. The Q2A site admin then chooses exactly where and when the widget is shown, out of those options that the widget makes available.
 
@@ -52,4 +52,4 @@ The PHP class for a widget module must contain the following functions (all are
     - `$request` - the Q2A request that generated the page, e.g. `'user/John Doe'`. The `$request` uses slash as a separator, independent of the type of URLs a particular Q2A site is using.
     - `$qa_content` - the nested Q2A array containing the full content for the page being displayed, as it was passed to the theme object. Use PHP's `print_r()` function to see what's inside and find any bits you need.
 
-[« Back to modules](/plugins/modules/)
+[« Back to modules]({{ site.baseurl }}/plugins/modules/)
diff --git a/plugins/modules.md b/plugins/modules.md
index 64db497..fb95c32 100644
--- a/plugins/modules.md
+++ b/plugins/modules.md
@@ -6,22 +6,22 @@ title: "Question2Answer - Developers - Plugin Modules"
 
 # Implementing plugin modules
 
-Plugin modules enable Question2Answer to be extended in specific ways. Each module is implemented as a PHP `class` with specific member functions. Some functions are relevant for all module types, as described below. Other functions are specific to a certain type of module, e.g. [page modules](/plugins/modules-page/) implement the functions `match_request()` and `process_request()`. If you wish to use non English characters in the PHP code for a module, ensure your text editor is using UTF-8 encoding without a BOM (byte order mark).
+Plugin modules enable Question2Answer to be extended in specific ways. Each module is implemented as a PHP `class` with specific member functions. Some functions are relevant for all module types, as described below. Other functions are specific to a certain type of module, e.g. [page modules]({{ site.baseurl }}/plugins/modules-page/) implement the functions `match_request()` and `process_request()`. If you wish to use non English characters in the PHP code for a module, ensure your text editor is using UTF-8 encoding without a BOM (byte order mark).
 
 ## Types of Module
 
 Below is a list of the module types supported by Q2A - click for more information about each type:
 
-- [**page**](/plugins/modules-page/) modules add a new type of page to a Q2A installation. The XML Sitemap plugin included with Q2A is an example.
-- [**login**](/plugins/modules-login/) modules allow users to log in to Q2A via an external identity provider, like the Facebook Login plugin included with Q2A.
-- [**editor**](/plugins/modules-editor/) modules provide a web interface for writing and editing posts. The WYSIWYG Editor included with Q2A is implemented via a plugin that registers an editor module.
-- [**viewer**](/plugins/modules-viewer/) modules render content as HTML or text, and often work together with an editor module. Support for [Markdown](http://en.wikipedia.org/wiki/Markdown) or equations could be added via a plugin with both an editor and viewer module.
-- [**event**](/plugins/modules-event/) modules (from Q2A 1.4+) are notified when something important happens, such as content being posted or voted on. They can be used for analytics, notifications or integrating with external services such as [Twitter](http://www.twitter.com/). The Event Logger plugin included with Q2A logs all events to a database table and/or log files.
-- [**widget**](/plugins/modules-widget/) modules (from Q2A 1.4+) allow extra content to be shown on Q2A pages. The site admin can decide exactly where the widget is displayed. The Tag Cloud widget plugin that comes with Q2A is one example.
-- [**filter**](/plugins/modules-filter/) modules (from Q2A 1.5+) can validate and/or modify many types of user input, including the content of posts. They can also mark whether a particular post should be queued for moderation.
-- [**search**](/plugins/modules-search/) modules (from Q2A 1.5+) can implement a custom indexer and/or search engine for a Q2A site. They are given the opportunity to index posts and/or custom page content, and replace the default search results with their own.
-- [**captcha**](/plugins/modules-captcha/) modules (from Q2A 1.5+) provide a web interface for human verification. The reCAPTCHA plugin that comes with Q2A provides an example, using the popular [reCAPTCHA](http://www.google.com/recaptcha) service.
-- [**process**](/plugins/modules-process/) modules (from Q2A 1.5+) have the opportunity to run at specific stages of Q2A's response processing. They can be used for logging, analytics, additional authentication, caching, etc...
+- [**page**]({{ site.baseurl }}/plugins/modules-page/) modules add a new type of page to a Q2A installation. The XML Sitemap plugin included with Q2A is an example.
+- [**login**]({{ site.baseurl }}/plugins/modules-login/) modules allow users to log in to Q2A via an external identity provider, like the Facebook Login plugin included with Q2A.
+- [**editor**]({{ site.baseurl }}/plugins/modules-editor/) modules provide a web interface for writing and editing posts. The WYSIWYG Editor included with Q2A is implemented via a plugin that registers an editor module.
+- [**viewer**]({{ site.baseurl }}/plugins/modules-viewer/) modules render content as HTML or text, and often work together with an editor module. Support for [Markdown](http://en.wikipedia.org/wiki/Markdown) or equations could be added via a plugin with both an editor and viewer module.
+- [**event**]({{ site.baseurl }}/plugins/modules-event/) modules (from Q2A 1.4+) are notified when something important happens, such as content being posted or voted on. They can be used for analytics, notifications or integrating with external services such as [Twitter](http://www.twitter.com/). The Event Logger plugin included with Q2A logs all events to a database table and/or log files.
+- [**widget**]({{ site.baseurl }}/plugins/modules-widget/) modules (from Q2A 1.4+) allow extra content to be shown on Q2A pages. The site admin can decide exactly where the widget is displayed. The Tag Cloud widget plugin that comes with Q2A is one example.
+- [**filter**]({{ site.baseurl }}/plugins/modules-filter/) modules (from Q2A 1.5+) can validate and/or modify many types of user input, including the content of posts. They can also mark whether a particular post should be queued for moderation.
+- [**search**]({{ site.baseurl }}/plugins/modules-search/) modules (from Q2A 1.5+) can implement a custom indexer and/or search engine for a Q2A site. They are given the opportunity to index posts and/or custom page content, and replace the default search results with their own.
+- [**captcha**]({{ site.baseurl }}/plugins/modules-captcha/) modules (from Q2A 1.5+) provide a web interface for human verification. The reCAPTCHA plugin that comes with Q2A provides an example, using the popular [reCAPTCHA](http://www.google.com/recaptcha) service.
+- [**process**]({{ site.baseurl }}/plugins/modules-process/) modules (from Q2A 1.5+) have the opportunity to run at specific stages of Q2A's response processing. They can be used for logging, analytics, additional authentication, caching, etc...
 
 ## Common module functions
 
@@ -37,11 +37,11 @@ Some functions are relevant for all module types, as listed below. You may also
 
     - All elements within the nested form array should be made HTML safe - use `qa_html()` as appropriate.
     - The `NAME=...` of all buttons and fields (within `tags` elements) should have a prefix which is unique to your plugin.
-    - Use `qa_clicked()` and `qa_post_text()`, as described [here](/code/functions/), to check for button clicks and retrieve submitted fields.
+    - Use `qa_clicked()` and `qa_post_text()`, as described [here]({{ site.baseurl }}/code/functions/), to check for button clicks and retrieve submitted fields.
     - Use `qa_opt()` to get or set an option that is stored in Q2A's options table. To prevent interference with Q2A or other plugins, any options should be named using a prefix which is unique to your plugin.
 
 - **`init_queries($tableslc)`**. If a module requires some database initialization, e.g. to create its own table, it can define this function to integrate into Q2A's installation and updating process (requires Q2A 1.5+). For your convenience, `$tableslc` contains an array of lower case names of tables currently in the Q2A database. Your function should examine the `$tableslc` array and perform any other diagnostics in order to determine whether initialization is required. If so, return an array of one or more MySQL queries that should be run, otherwise return `null`. If you are creating a table with a `CREATE TABLE` query, you should add the appropriate prefix to the table name - see `qa_db_add_table_prefix()` in `qa-db.php` or use the `^` symbol before the table name. This will prevent clashes between separate Q2A installations sharing a database.
 
 ## Communication between modules
 
-A module can define any additional functions for its own purposes, in the usual way for a PHP class. These functions can also be used for communication between modules, either within a plugin, or between different plugins. To call a function defined in a module, call [`qa_load_module()`](/code/functions/) to retrieve an object of the module's class, then call the object's function in the usual PHP way. Note that multiple calls to `qa_load_module()` will return the same object.
+A module can define any additional functions for its own purposes, in the usual way for a PHP class. These functions can also be used for communication between modules, either within a plugin, or between different plugins. To call a function defined in a module, call [`qa_load_module()`]({{ site.baseurl }}/code/functions/) to retrieve an object of the module's class, then call the object's function in the usual PHP way. Note that multiple calls to `qa_load_module()` will return the same object.
diff --git a/plugins/overrides.md b/plugins/overrides.md
index fb0d16b..cc288df 100644
--- a/plugins/overrides.md
+++ b/plugins/overrides.md
@@ -6,7 +6,7 @@ title: "Question2Answer - Developers - Overrides"
 
 # Implementing plugin overrides
 
-Plugin overrides (requires Q2A 1.5+) can replace or wrap over 150 functions defined within the Q2A core. Overrides can be very powerful, but they run a risk of incompatibility with future versions of Q2A. If possible, it is recommended to use [modules](/plugins/modules/) or [layers](/plugins/layers/) instead. Nonetheless, some things can only be done via overrides, and future versions of Q2A will try not to break them.
+Plugin overrides (requires Q2A 1.5+) can replace or wrap over 150 functions defined within the Q2A core. Overrides can be very powerful, but they run a risk of incompatibility with future versions of Q2A. If possible, it is recommended to use [modules]({{ site.baseurl }}/plugins/modules/) or [layers]({{ site.baseurl }}/plugins/layers/) instead. Nonetheless, some things can only be done via overrides, and future versions of Q2A will try not to break them.
 
 Not all functions in Q2A can be overridden. To check a particular function, see whether its definition begins with:
 
diff --git a/plugins/tutorial.md b/plugins/tutorial.md
index 68cbd30..0a3a273 100644
--- a/plugins/tutorial.md
+++ b/plugins/tutorial.md
@@ -6,9 +6,9 @@ title: "Question2Answer - Developers - Tutorial - Writing a Plugin"
 
 # Tutorial: Writing a Question2Answer plugin
 
-In this tutorial, we will create a Question2Answer (1.5+) [plugin](/plugins/) from scratch. Our plugin will allow descriptions to be added to tags on a Q2A site. These descriptions will be displayed and edited on the page listing recent questions for each tag. They will also be shown in a tooltip when users mouse over a tag. The Q2A administrator will be able to decide who can edit tag descriptions.
+In this tutorial, we will create a Question2Answer (1.5+) [plugin]({{ site.baseurl }}/plugins/) from scratch. Our plugin will allow descriptions to be added to tags on a Q2A site. These descriptions will be displayed and edited on the page listing recent questions for each tag. They will also be shown in a tooltip when users mouse over a tag. The Q2A administrator will be able to decide who can edit tag descriptions.
 
-The tutorial will touch on each of the main areas of Q2A plugin `function`ality. Tag descriptions will be stored in the Q2A database, using Q2A's tag metadata table. The descriptions will be displayed on a tag's page using a [widget module](/plugins/modules-widget/). Tags will be edited on pages provided by a [page module](/plugins/modules-page/). An [override](/plugins/overrides/) will be used to show the tooltips, and then a [layer](/plugins/layers/) will allow us to do this with fewer database queries. An admin form for the plugin will be displayed in the 'Plugins' section of the admin panel, with the corresponding settings stored by Q2A's options mechanism. At the end of this process, we will see how to make the plugin localizable.
+The tutorial will touch on each of the main areas of Q2A plugin `function`ality. Tag descriptions will be stored in the Q2A database, using Q2A's tag metadata table. The descriptions will be displayed on a tag's page using a [widget module]({{ site.baseurl }}/plugins/modules-widget/). Tags will be edited on pages provided by a [page module]({{ site.baseurl }}/plugins/modules-page/). An [override]({{ site.baseurl }}/plugins/overrides/) will be used to show the tooltips, and then a [layer]({{ site.baseurl }}/plugins/layers/) will allow us to do this with fewer database queries. An admin form for the plugin will be displayed in the 'Plugins' section of the admin panel, with the corresponding settings stored by Q2A's options mechanism. At the end of this process, we will see how to make the plugin localizable.
 
 This tutorial assumes you are familiar with the [PHP](http://www.php.net/) programming language as well as some basic [HTML](http://en.wikipedia.org/wiki/HTML) and [MySQL](http://www.mysql.com/).
 
@@ -17,7 +17,7 @@ This tutorial assumes you are familiar with the [PHP](http://www.php.net/) progr
 
 In this first step we will set up the directory for the plugin and create the crucial `qa-plugin.php` file within.
 
-- Create a new empty directory `tag-descriptions` in Q2A's `qa-plugin` directory - see [here](/plugins/) for naming conventions.
+- Create a new empty directory `tag-descriptions` in Q2A's `qa-plugin` directory - see [here]({{ site.baseurl }}/plugins/) for naming conventions.
 
 - Create an empty `qa-plugin.php` file inside this directory. This file is the core of the plugin. It registers each of the plugin's elements with Q2A and contains meta information for display in Q2A's admin interface.
 
@@ -46,7 +46,7 @@ In this first step we will set up the directory for the plugin and create the cr
     }
     ```
 
-    See [here](/plugins/) for a detailed description of the metadata fields. The code below the metadata ensures that visitors to your Q2A site cannot request the `qa-plugin.php` page directly (even though doing so would cause no actual harm).
+    See [here]({{ site.baseurl }}/plugins/) for a detailed description of the metadata fields. The code below the metadata ensures that visitors to your Q2A site cannot request the `qa-plugin.php` page directly (even though doing so would cause no actual harm).
 
 - Reopen the 'Plugins' page of your Q2A site admin panel and check that the listing has been updated. We're on our way!
 
@@ -70,7 +70,7 @@ In this step we will create the initial version of the widget module which displ
     }
     ```
 
-    This is the beginning of the PHP class that will define the widget's functionality. The `allow_template()` function is one of three class functions required in a widget module ([more here](/plugins/modules-widget/)). It is called by Q2A to determine which types of pages the widget can be displayed on. In this case, the widget can only be displayed on pages listing recent questions for a tag, so the function only returns `true` if the `$template` parameter is `'tag'`.
+    This is the beginning of the PHP class that will define the widget's functionality. The `allow_template()` function is one of three class functions required in a widget module ([more here]({{ site.baseurl }}/plugins/modules-widget/)). It is called by Q2A to determine which types of pages the widget can be displayed on. In this case, the widget can only be displayed on pages listing recent questions for a tag, so the function only returns `true` if the `$template` parameter is `'tag'`.
 
 - Add the following two additional functions **inside** the `class` definition in `qa-tag-desc-widget.php`:
 
@@ -99,7 +99,7 @@ In this step we will create the initial version of the widget module which displ
     );
     ```
 
-    Each parameter to `qa_register_plugin_module()` is explained by a comment in the code above - [more here](/plugins/).
+    Each parameter to `qa_register_plugin_module()` is explained by a comment in the code above - [more here]({{ site.baseurl }}/plugins/).
 
 - Now it's time to test out the widget. Ensure you have saved/uploaded the `qa-plugin.php` and `qa-tag-desc-widget.php` files. Then open the 'Layout' section of your Q2A site admin panel. The list of available widgets should include the name 'Tag Descriptions'. Click 'add widget' next to it, and choose to display the widget somewhere on tag pages. Note how the options shown in the admin panel reflect the widget module's responses from `allow_template()` and `allow_region()`.
 
@@ -132,7 +132,7 @@ In this step we will create the page module that allows tag descriptions to be e
     }
     ```
 
-    The `match_request()` function let a page module decide if it will process a particular web page request. The `$request` parameter is always slash-separated, independent of the URL structure used by a particular Q2A site - [more here](/plugins/modules-page/). We have decided that the URLs for our tag description editor will take the form `tag-edit/*` where `*` is the tag to be edited. For now, the `process_request()` function in the page module generates an empty page for these requests.
+    The `match_request()` function let a page module decide if it will process a particular web page request. The `$request` parameter is always slash-separated, independent of the URL structure used by a particular Q2A site - [more here]({{ site.baseurl }}/plugins/modules-page/). We have decided that the URLs for our tag description editor will take the form `tag-edit/*` where `*` is the tag to be edited. For now, the `process_request()` function in the page module generates an empty page for these requests.
 
 - Activate the page model within the plugin by pasting the following code at the end of your `qa-plugin.php` file:
 
@@ -203,7 +203,7 @@ In this step we will get the tag description editing page up and working.
 
     There is a lot happening here, so let's go through it step by step:
 
-    - First, we include the Q2A core file `qa-db-metas.php`, since we will need use some of its functions to access the Q2A database table for tag meta information. (If necessary, modules can also create their own database tables by implementing the `init_queries()` function - [more here](/plugins/modules/)).
+    - First, we include the Q2A core file `qa-db-metas.php`, since we will need use some of its functions to access the Q2A database table for tag meta information. (If necessary, modules can also create their own database tables by implementing the `init_queries()` function - [more here]({{ site.baseurl }}/plugins/modules/)).
 
     - The main work consists of adding an element with key `'form'` to the `$qa_content` array. This element describes a form on the page, which is converted by the Q2A theme class into appropriate HTML code. (To add more forms to the page, more elements could be added with keys `'form2'`, `'form_extra'`, or anything else beginning with `'form'`.)
 
@@ -268,7 +268,7 @@ In this step we will get the tag description editing page up and working.
     }
     ```
 
-    The `output_widget()` function now identifies which tag page is being requested, retrieves the appropriate tag description from the database, and displays it if it exists, after HTML escaping. An appropriate link to edit the description is also shown, using Q2A's `qa_path_html(...)` function to create an HTML-escaped relative URL to the tag editor page - [more here](/code/functions/).
+    The `output_widget()` function now identifies which tag page is being requested, retrieves the appropriate tag description from the database, and displays it if it exists, after HTML escaping. An appropriate link to edit the description is also shown, using Q2A's `qa_path_html(...)` function to create an HTML-escaped relative URL to the tag editor page - [more here]({{ site.baseurl }}/code/functions/).
 
 - Save/upload as usual. If everything is in place, you should be able to view your descriptions on the tag page, click to edit them on a different page, and then click to save and view them back again on the tag page. Congratulations!
 
@@ -290,7 +290,7 @@ In this step we will implement the tooltips which display tag descriptions when
     }
     ```
 
-    This `qa_tag_html()` function will override the standard version of that function, which we saw just before. However our version makes uses of the standard function by calling it using the name `qa_tag_html_base()` - [more here](/plugins/overrides/). Instead of passing through the `$tag` as is, we add underscores before and after it, so that we can test that the override is working. Note that the optional `$favorited` parameter was added in Q2A 1.6, but this code will still work fine in Q2A 1.5.x, with PHP ignoring the extra unexpected parameter.
+    This `qa_tag_html()` function will override the standard version of that function, which we saw just before. However our version makes uses of the standard function by calling it using the name `qa_tag_html_base()` - [more here]({{ site.baseurl }}/plugins/overrides/). Instead of passing through the `$tag` as is, we add underscores before and after it, so that we can test that the override is working. Note that the optional `$favorited` parameter was added in Q2A 1.6, but this code will still work fine in Q2A 1.5.x, with PHP ignoring the extra unexpected parameter.
 
 - Activate the function override by pasting the following line at the end of your plugin's `qa-plugin.php`:
 
@@ -326,7 +326,7 @@ In this step we will implement the tooltips which display tag descriptions when
 
     Let's explain this function step by step:
 
-    - First, we call the standard version of the function using `qa_tag_html_base()` and store the standard HTML to represent a tag in the variable `$taghtml`. By calling through to the base function rather than copying its code here, we protect ourselves better against changes in future versions of Q2A. We also enable multiple plugins to override the same function for different purposes, with Q2A building an appropriate chain of renamed functions that call each other in turn. If possible, it is always a good idea to do this when overriding a function - [more here](/plugins/overrides/).
+    - First, we call the standard version of the function using `qa_tag_html_base()` and store the standard HTML to represent a tag in the variable `$taghtml`. By calling through to the base function rather than copying its code here, we protect ourselves better against changes in future versions of Q2A. We also enable multiple plugins to override the same function for different purposes, with Q2A building an appropriate chain of renamed functions that call each other in turn. If possible, it is always a good idea to do this when overriding a function - [more here]({{ site.baseurl }}/plugins/overrides/).
 
     - We retrieve the description for `$tag` from the database, using `qa_db_tagmeta_get()` in the same way as before.
 
@@ -413,7 +413,7 @@ In the second stage, a layer will replace the `post_tag_item()` function in Q2A'
 
     - Then `$plugin_tag_desc_list` is set to `null` so that this branch is skipped next time `post_tag_item(...)` is called.
 
-    - Finally, we call through to the `post_tag_item()` function in Q2A's base theme class using PHP's double colon notation - [more here](/plugins/layers/). Note how base functions are called differently for overrides and for layers.
+    - Finally, we call through to the `post_tag_item()` function in Q2A's base theme class using PHP's double colon notation - [more here]({{ site.baseurl }}/plugins/layers/). Note how base functions are called differently for overrides and for layers.
 
 - As with modules and overrides, we need to activate the layer by adding this in our plugin's `qa-plugin.php` file:
 
@@ -457,7 +457,7 @@ In the second stage, a layer will replace the `post_tag_item()` function in Q2A'
 
     - As before, we check if the global `$plugin_tag_desc_list` array variable contains any items, If so, we need to retrieve some tag descriptions from the database.
 
-    - We retrieve all the tag descriptions in one database query. There is no function to retrieve metadata for multiple tags in `qa-db-metas.php`, so we write and run the query ourselves using Q2A's `qa_db_query_sub()` function. This substitutes `^` in the query string for the Q2A table prefix set in `qa-config.php`. It also substitutes `$` and `#` for any additional parameters passed, escaping them to ensure the SQL is secure - [more here](/code/functions/#database-access-in-qa-dbphp). In this case, the `$` symbol will be turning into a comma-separated list of tags in `array_keys($plugin_tag_desc_list)`.
+    - We retrieve all the tag descriptions in one database query. There is no function to retrieve metadata for multiple tags in `qa-db-metas.php`, so we write and run the query ourselves using Q2A's `qa_db_query_sub()` function. This substitutes `^` in the query string for the Q2A table prefix set in `qa-config.php`. It also substitutes `$` and `#` for any additional parameters passed, escaping them to ensure the SQL is secure - [more here]({{ site.baseurl }}/code/functions/#database-access-in-qa-dbphp). In this case, the `$` symbol will be turning into a comma-separated list of tags in `array_keys($plugin_tag_desc_list)`.
 
     - The `$result` obtained from the database query is turned into a map from tags to descriptions using Q2A's `qa_db_read_all_assoc()` function - see the function's definition in `qa-db.php`. The map is stored in the global `$plugin_tag_desc_map` variable so that it is available every time our `post_tag_item()` function is called.
 
@@ -539,7 +539,7 @@ In this step, we will add an options form to the plugin which controls how the t
 
     The `admin_form()` function can also be added to any module, and enables that module to display a form on the 'Plugins' page of the Q2A admin panel. The function returns a Q2A form definition array for display on the page, after processing any appropriate user input. Most of this should be familiar from our earlier encounter with a Q2A form, but a few things are new:
 
-    - We're using Q2A's `qa_opt()` function to both set and retrieve option values - [more here](/code/functions/).
+    - We're using Q2A's `qa_opt()` function to both set and retrieve option values - [more here]({{ site.baseurl }}/code/functions/).
     - An element `'ok'` is used to add a confirmation message at the top of the form.
     - An element `'suffix'` is used within field definitions to show some text after the field.
 
@@ -684,7 +684,7 @@ In this final step we will make your plugin ready for localization into differen
     );
     ```
 
-    This sets up localization for your plugin. The `*` in the file name passed to `qa_register_plugin_phrases()` will be substituted for language codes such as `fr` or `ru`, or `default` to load the default phrases. The second parameter `'plugin_tag_desc'` sets the prefix for retrieving your language strings using Q2A's `qa_lang()` or `qa_lang_html()` functions - [more here](/plugins/).
+    This sets up localization for your plugin. The `*` in the file name passed to `qa_register_plugin_phrases()` will be substituted for language codes such as `fr` or `ru`, or `default` to load the default phrases. The second parameter `'plugin_tag_desc'` sets the prefix for retrieving your language strings using Q2A's `qa_lang()` or `qa_lang_html()` functions - [more here]({{ site.baseurl }}/plugins/).
 
 - Find the line in `qa-tag-desc-widget.php` containing the phrase `Create tag description` and replace it with:
 
@@ -746,4 +746,4 @@ If you made it this far, congratulations! This completes the tutorial. To recap,
 
 To check you followed the instructions correctly, you can [download the completed plugin](http://www.question2answer.org/releases/q2a-tag-descriptions-tutorial.zip).
 
-Now you can think about the plugin that **you** want to build and how to go about it. To get started, take a look at the different [types of module](/plugins/modules/) that Q2A supports - as of Q2A 1.5, there are ten available, and we only covered two in this tutorial. You should also take a look at this list of useful [Q2A functions](/code/functions/) and have a browse around the Q2A source code to learn about many more. Finally, take a look at the code of the [many plugins](/addons/) already developed for Q2A. Thank you and good luck!
+Now you can think about the plugin that **you** want to build and how to go about it. To get started, take a look at the different [types of module]({{ site.baseurl }}/plugins/modules/) that Q2A supports - as of Q2A 1.5, there are ten available, and we only covered two in this tutorial. You should also take a look at this list of useful [Q2A functions]({{ site.baseurl }}/code/functions/) and have a browse around the Q2A source code to learn about many more. Finally, take a look at the code of the [many plugins]({{ site.baseurl }}/addons/) already developed for Q2A. Thank you and good luck!
diff --git a/themes/index.md b/themes/index.md
index f95a544..bb5764c 100644
--- a/themes/index.md
+++ b/themes/index.md
@@ -31,7 +31,7 @@ Question2Answer supports multiple themes, and makes it easy for you to create yo
 
     Some of this metadata will be displayed next to the theme setting in the Q2A admin interface. In addition, `Theme Update Check URI` allows you to inform users about new versions of the theme. Q2A will retrieve the content from `Theme Update Check URI`, and look for metadata in the same format as above. If the `Theme Version` values don't match, a message will show up, along with a link to the `Theme URI` from the online metadata. The simplest way to use this mechanism is to keep the latest version of `qa-styles.css` at a particular location online, and set that location as the `Theme Update Check URI`.
 
-6. Please consider offering your theme online as a .zip file for others to download, then [telling us](http://www.question2answer.org/feedback.php) so we can [link to it here](/addons/).
+6. Please consider offering your theme online as a .zip file for others to download, then [telling us](http://www.question2answer.org/feedback.php) so we can [link to it here]({{ site.baseurl }}/addons/).
 
 
 ## Creating an advanced theme for Question2Answer
diff --git a/translate/index.md b/translate/index.md
index 93102ba..8c7f86b 100644
--- a/translate/index.md
+++ b/translate/index.md
@@ -5,7 +5,7 @@ title: "Question2Answer - Developers - Translation / Localization"
 
 # Translating Question2Answer into another language
 
-Question2Answer fully supports non-English languages and is easy to translate. Before proceeding, it's worth [checking here](/addons/translations/) to see if a translation is already available. You may be able to use this immediately, or only have to add some missing phrases.
+Question2Answer fully supports non-English languages and is easy to translate. Before proceeding, it's worth [checking here]({{ site.baseurl }}/addons/translations/) to see if a translation is already available. You may be able to use this immediately, or only have to add some missing phrases.
 
 
 ## Creating a new translation
@@ -31,7 +31,7 @@ To create a new Question2Answer translation from scratch, follow the steps below
 
 7. **`qa-check-lang.php` is your friend!** As you work, use your web browser to view the `qa-include/qa-check-lang.php` page within your Question2Answer site. This will check your language files for any omitted phrases or substitutions.
 
-8. Please consider sending us your translation or making it available online, so that we can [link to it here](/addons/translations/).
+8. Please consider sending us your translation or making it available online, so that we can [link to it here]({{ site.baseurl }}/addons/translations/).
 
 
 ## Updating an existing translation
@@ -52,7 +52,7 @@ An incomplete Question2Answer translation may be available for your language, fo
 
 5. As you work, refresh `qa-include/qa-check-lang.php` in your web browser and ensure that you resolve all issues shown. You can also browse around your Q2A site to see how the translated phrases are used in context.
 
-6. Please consider sending us your translation or making it available online, so that we can [link to it here](/addons/translations/).
+6. Please consider sending us your translation or making it available online, so that we can [link to it here]({{ site.baseurl }}/addons/translations/).
 
 
 ## Customizing selected URLs or phrases