diff --git a/files/howto_sortorder_1.png b/files/howto_sortorder_1.png
new file mode 100644
index 00000000..97d996f8
Binary files /dev/null and b/files/howto_sortorder_1.png differ
diff --git a/files/howto_sortorder_2.png b/files/howto_sortorder_2.png
new file mode 100644
index 00000000..80fda055
Binary files /dev/null and b/files/howto_sortorder_2.png differ
diff --git a/index.php b/index.php
index d4a064fe..b24fda8d 100644
--- a/index.php
+++ b/index.php
@@ -12,6 +12,7 @@
// Yeah, this is turning into a bit of black magic voodoo. Refactor at some point.
$prefix = dirname($parseurl['path']);
$prefix = strtr($prefix, array("/extensions" => "","/internals" => "", "/tutorial" => "", "/howto" => "", "/storage" => ""));
+$linkPrefix = '';
$request = str_replace($prefix, "", $parseurl['path']);
diff --git a/menu_docs.yml b/menu_docs.yml
index 62a10edd..8659ae0f 100644
--- a/menu_docs.yml
+++ b/menu_docs.yml
@@ -72,3 +72,4 @@ howto:
howto/making-sure-htaccess-works: "Making sure .htaccess and mod_rewrite are working as they should"
howto/muti-site-setup: "Running Multiple Bolt sites from one source directory"
howto/curl-ca-certificates: "Setting Up cURL SSL/TLS Certificate Authority Certificates"
+ howto/sortingorder-in-contenttypes: "Sorting a contenttype with a 'sortorder'"
diff --git a/source_docs/howto/sortingorder-in-contenttypes.md b/source_docs/howto/sortingorder-in-contenttypes.md
new file mode 100644
index 00000000..25965746
--- /dev/null
+++ b/source_docs/howto/sortingorder-in-contenttypes.md
@@ -0,0 +1,77 @@
+Sorting a contenttype with a 'sortorder'
+========================================
+
+Sometimes you might need to sort Pages or some other contenttype on an
+arbitrary order, instead of on "Title, aphabetically" or "Date added". In these
+cases, you can use the built-in taxonomy that can use a given sortorder. This
+will allow you to manually define the order of all records in that specific
+contenttype. To set it up, follow these two steps:
+
+First, make sure you have a taxonomy set up to use the 'sortorder' sorting.
+Make sure it has set both `behaves_like: grouping` as well as `has_sortorder:
+true`. The below example comes straight from the default `taxonomy.yml`, and it
+has this feature enabled:
+
+```
+chapters:
+ slug: chapters
+ singular_slug: chapter
+ behaves_like: grouping
+ options: { main: "The main chapter", meta: "Meta Chapter", other: "The other stuff" }
+ has_sortorder: true
+```
+
+Tip: You will _need_ to keep the `options:` setting in there. Even if you don't
+really need to order the records into different groups, you'll need to keep at
+least one of the 'options' present in your taxonomy.
+
+Secondly, you'll want to make sure that you configure your contenttype to use
+this taxonomy in your `contenttypes.yml`. Note that the contenttype does _not_
+require a `sort:` option. In this case Bolt will use the sorting, as defined in
+our taxonomy, so defining another sort option would make no sense. For example,
+see this `pages` contenttype:
+
+```
+pages:
+ name: Pages
+ singular_name: Page
+ fields:
+ title:
+ type: text
+ class: large
+ group: content
+ slug:
+ type: slug
+ uses: title
+ […]
+ taxonomy: [ chapters ]
+ recordsperpage: 100
+```
+
+Once you've done this, you can edit the records in Bolt, assigning them the
+sortorder you need:
+
+
+
+In the overview page, you'll see the records listed ascending, in the order
+you've specified:
+
+
+
+Note that retrieving these records in the frontend works automatically. If you
+wish to get the records ordered by the given sortorder, just use a plain
+`setcontent`:
+
+```
+{% setcontent orderedpages = 'pages' %}
+{{ dump(orderedpages) }}
+```
+
+You can still order by a specific field, by overriding the order in the
+`setcontent` tag:
+
+```
+{% setcontent orderedpages = 'pages' orderby 'title' %}
+{{ dump(orderedpages) }}
+```
+