From cdba66b951edd627080541b38b6519fdd93c116e Mon Sep 17 00:00:00 2001 From: Daniel Rudolf Date: Sat, 17 Sep 2016 16:50:36 +0200 Subject: [PATCH] Inline docs: Use Twig's array literal rather than the split filter for sort_by --- content-sample/index.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/content-sample/index.md b/content-sample/index.md index 666a4ca..6a1a30e 100644 --- a/content-sample/index.md +++ b/content-sample/index.md @@ -227,12 +227,12 @@ 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 %}` +(e.g. `{% for page in pages|sort_by([ 'meta', 'nav' ]) %}...{% 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). +`[ 'meta', 'nav' ]` part of the example, it instructs Pico to sort by +`page.meta.nav`). 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