diff --git a/_docs/creating-content.md b/_docs/creating-content.md
index 7087251cebe2766059b27462e770a02c9119b56d..29276fc65bd6995b2710c38ab6f3f4b957abe61a 100644
--- a/_docs/creating-content.md
+++ b/_docs/creating-content.md
@@ -89,7 +89,7 @@ If you want to use Pico as a blogging software, you probably want to do somethin
     <li>
         Create a <code>blog.md</code> in your <code>content</code> folder and set its <code>Template</code> meta header to e.g. <code>blog</code>. Also create a <code>blog.twig</code> in your theme directory. This template will show a list of your articles, so you probably want to do something like this:
 
-        {% raw %}<pre><code>{% for page in pages %}
+        {% raw %}<pre><code>{% for page in pages|sort_by("time")|reverse %}
     {% if page.id starts with &quot;blog/&quot; %}
         &lt;div class=&quot;post&quot;&gt;
             &lt;h3&gt;&lt;a href=&quot;{{ page.url }}&quot;&gt;{{ page.title }}&lt;/a&gt;&lt;/h3&gt;
@@ -100,10 +100,7 @@ If you want to use Pico as a blogging software, you probably want to do somethin
 {% endfor %}</code></pre>{% endraw %}
     </li>
     <li>
-        Let Pico sort pages by date by setting <code>$config['pages_order_by'] = 'date';</code> in your <code>config/config.php</code>. To use a descending order (newest articles first), also add <code>$config['pages_order'] = 'desc';</code>. The former won't affect pages without a <code>Date</code> meta header, but the latter does. To use ascending order for your page navigation again, add Twigs <code>reverse</code> filter to the navigation loop (<code>{&#37; for page in pages|reverse &#37;}...{&#37; endfor &#37;}}</code>) in your themes <code>index.twig</code>.
-    </li>
-    <li>
-        Make sure to exclude the blog articles from your page navigation. You can achieve this by adding <code>{&#37; if not page starts with "blog/" &#37;}...{&#37; endif &#37;}</code> to the navigation loop.
+        Make sure to exclude the blog articles from your page navigation. You can achieve this by adding <code>{&#37; if not page starts with "blog/" &#37;}...{&#37; endif &#37;}</code> to the navigation loop (<code>{&#37; for page in pages &#37;}...{&#37; endfor &#37;}}</code>) in your themes <code>index.twig</code>.
     </li>
 </ol>
 
diff --git a/_docs/customization.md b/_docs/customization.md
index dfb84673579b4ee277f8b894177799737cc3ef7a..a90f1cb876bc2a950cf181ae36c35dabae582770 100644
--- a/_docs/customization.md
+++ b/_docs/customization.md
@@ -60,6 +60,8 @@ Pages can be used like the following:
     {% endfor %}
 &lt;/ul&gt;</code></pre>{% endraw %}
 
+Additional to Twigs extensive list of filters, functions and tags, Pico also provides some useful additional filters to make theming easier. You can parse any Markdown string to HTML using the `markdown` filter. Arrays can be sorted by one of its keys or a arbitrary deep sub-key using the `sort_by` filter (e.g. `{% for page in pages|sort_by("meta:nav"|split(":")) %}...{% endfor %}` iterates through all pages, ordered by the `nav` meta header; please note the `"meta:nav"|split(":")` part of the example, which passes `['meta', 'nav']` to the filter describing a key path). You can return all values of a given key or key path of an array using the `map` filter (e.g. `{{ pages|map("title") }}` returns all page titles).
+
 You can use different templates for different content files by specifying the `Template` meta header. Simply add e.g. `Template: blog-post` to a content file and Pico will use the `blog-post.twig` file in your theme folder to render the page.
 
 You don't have to create your own theme if Pico's default theme isn't sufficient for you, you can use one of the great themes third-party developers and designers created in the past. As with plugins, you can find themes in [our Wiki][WikiThemes].