{ "version": "https://jsonfeed.org/version/1.1", "title": "Cecil - Templates", "home_page_url": "https://cecil.app/documentation/templates/", "feed_url": "https://cecil.app/documentation/templates/feed.json", "description": "Work with Twig layouts, templates and components.", "icon": "https://cecil.app/favicon.7ff4b89eec6dad139a7d2d6561543285.png", "favicon": "https://cecil.app/thumbnails/64x/favicon.7ff4b89eec6dad139a7d2d6561543285.png", "language": "en", "items": [ { "id": "https://cecil.app/documentation/templates/lookup-rules/", "url": "https://cecil.app/documentation/templates/lookup-rules/", "title": "Organization and lookup rules", "summary": "Kinds of templates, naming convention, built-in templates and how a template is chosen for a page.", "date_published": "2021-05-07T00:00:00+00:00", "date_modified": "2026-10-05T00:00:00+00:00","content_text": "Organization and lookup rules\nFiles organization\nKinds of templates\nThere are three kinds of templates: layouts, components, and other templates. Layouts are used to render pages, and each layout can include templates and components.\nNaming convention\nTemplate files are stored in the layouts\/ directory and must be named according to the following convention:\nlayouts\/(<section>\/)<type>|<layout>.<format>(.<language>).twig\n\n<section> (optional)\nThe section of the page (e.g.: blog).\n<type>\nThe page type: home (or index) for homepage, list for list, page for page, etc. (See Lookup rules for details).\n<layout> (optional)\nThe custom layout name defined in the front matter of the page (e.g.: layout: my-layout).\n<format>\nThe output format of the rendered page (e.g.: html, rss, json, xml, etc.).\n<language> (optional)\nThe language of the page (e.g.: fr).\n\nExamples:\nlayouts\/home.html.twig # `type` is \"homepage\"\nlayouts\/page.html.twig # `type` is \"page\"\nlayouts\/page.html.fr.twig # `type` is \"page\" and `language` is \"fr\"\nlayouts\/my-layout.html.twig # `layout` is \"my-layout\"\nlayouts\/blog\/list.html.twig # `section` is \"blog\"\nlayouts\/blog\/list.rss.twig # `section` is \"blog\" and `format` is \"rss\"\n<my-site>\n├─ ...\n├─ layouts\n| ├─ index.html.twig # Used by type \"homepage\"\n| ├─ list.html.twig # Used by types \"homepage\" and \"section\"\n| ├─ list.rss.twig # Used by types \"homepage\" and \"section\", for RSS output format\n| ├─ page.html.twig # Used by type \"page\"\n| ├─ taxonomy\n| | ├─ tags.html.twig # Used by type \"vocabulary\" of `tags` (list of terms)\n| | └─ tag.html.twig # Used by type \"term\" of `tags` (list of pages)\n| ├─ my-layout.html.twig # Used by pages with `layout: my-layout` in the front matter\n| ├─ ...\n| └─ partials # Included templates\n| ├─ footer.html.twig\n| └─ ...\n└─ themes # Themes layouts and templates\n └─ ...\nBuilt-in templates\nCecil comes with a set of built-in templates.\nIf you need to modify built-in templates, you can easily extract them via the following command: they will be copied in the layouts directory of your site.\nphp cecil.phar util:templates:extract\nLookup rules\nIn most of cases you don’t need to specify the layout: Cecil selects the most appropriate layout, according to the page type.\nFor example, the HTML output of home page (index.md) will be rendered:\n\nwith my-layout.html.twig if the layout variable is set to \"my-layout\" (in the front matter)\nif not, with index.html.twig if the file exists\nif not, with home.html.twig if the file exists\nif not, with list.html.twig if the file exists\n\nAll rules are detailed below, for each page type, in the priority order.\nType homepage\n\n<layout>.<format>.twig\nindex.<format>.twig\nhome.<format>.twig\nlist.<format>.twig\n_default\/<layout>.<format>.twig\n_default\/index.<format>.twig\n_default\/home.<format>.twig\n_default\/list.<format>.twig\n_default\/page.<format>.twig\n\nType page\n\n<section>\/<layout>.<format>.twig\n<layout>.<format>.twig\n<section>\/page.<format>.twig\n_default\/<layout>.<format>.twig\npage.<format>.twig\n_default\/page.<format>.twig\n\nType section\n\n<layout>.<format>.twig\n<section>\/index.<format>.twig\n<section>\/list.<format>.twig\nsection\/<section>.<format>.twig\n<parent>\/index.<format>.twig, <parent>\/list.<format>.twig and section\/<parent>.<format>.twig, for each parent section of a sub-section (nearest first)\n_default\/section.<format>.twig\nlist.<format>.twig\n_default\/list.<format>.twig\n\nThe <section> of a sub-section is its full path (e.g.: blog\/2024), and a sub-section falls back to the templates of its parent sections: if blog\/2024\/list.html.twig doesn’t exist, the sub-section blog\/2024 is rendered with blog\/list.html.twig.\nType vocabulary\n\ntaxonomy\/<plural>.<format>.twig\nvocabulary.<format>.twig\n_default\/vocabulary.<format>.twig\n\nType term\n\ntaxonomy\/<plural>\/<term>.<format>.twig\ntaxonomy\/<singular>.<format>.twig\nterm.<format>.twig\n_default\/term.<format>.twig\n_default\/list.<format>.twig\n\nThe vocabulary template is named after the plural (e.g.: taxonomy\/categories.html.twig for \/categories\/), whereas the term template is named after the singular (e.g.: taxonomy\/category.html.twig for \/categories\/data-sovereignty\/).\n<term> is the slugified term name: a dedicated template for the term \"Data Sovereignty\" of the categories vocabulary is taxonomy\/categories\/data-sovereignty.html.twig.\nMost of those layouts are available by default, see built-in templates.", "content_html": "

Organization and lookup rules

\n

Files organization

\n

Kinds of templates

\n

There are three kinds of templates: layouts, components, and other templates. Layouts are used to render pages, and each layout can include templates and components.

\n

Naming convention

\n

Template files are stored in the layouts/ directory and must be named according to the following convention:

\n
layouts/(<section>/)<type>|<layout>.<format>(.<language>).twig
\n
\n
<section> (optional)
\n
The section of the page (e.g.: blog).
\n
<type>
\n
The page type: home (or index) for homepage, list for list, page for page, etc. (See Lookup rules for details).
\n
<layout> (optional)
\n
The custom layout name defined in the front matter of the page (e.g.: layout: my-layout).
\n
<format>
\n
The output format of the rendered page (e.g.: html, rss, json, xml, etc.).
\n
<language> (optional)
\n
The language of the page (e.g.: fr).
\n
\n

Examples:

\n
layouts/home.html.twig       # `type` is \"homepage\"\nlayouts/page.html.twig       # `type` is \"page\"\nlayouts/page.html.fr.twig    # `type` is \"page\" and `language` is \"fr\"\nlayouts/my-layout.html.twig  # `layout` is \"my-layout\"\nlayouts/blog/list.html.twig  # `section` is \"blog\"\nlayouts/blog/list.rss.twig   # `section` is \"blog\" and `format` is \"rss\"
\n
<my-site>\n├─ ...\n├─ layouts\n|  ├─ index.html.twig      # Used by type \"homepage\"\n|  ├─ list.html.twig       # Used by types \"homepage\" and \"section\"\n|  ├─ list.rss.twig        # Used by types \"homepage\" and \"section\", for RSS output format\n|  ├─ page.html.twig       # Used by type \"page\"\n|  ├─ taxonomy\n|  |  ├─ tags.html.twig    # Used by type \"vocabulary\" of `tags` (list of terms)\n|  |  └─ tag.html.twig     # Used by type \"term\" of `tags` (list of pages)\n|  ├─ my-layout.html.twig  # Used by pages with `layout: my-layout` in the front matter\n|  ├─ ...\n|  └─ partials             # Included templates\n|     ├─ footer.html.twig\n|     └─ ...\n└─ themes                  # Themes layouts and templates\n   └─ ...
\n

Built-in templates

\n

Cecil comes with a set of built-in templates.

\n\n

Lookup rules

\n

In most of cases you don’t need to specify the layout: Cecil selects the most appropriate layout, according to the page type.

\n

For example, the HTML output of home page (index.md) will be rendered:

\n
    \n
  1. with my-layout.html.twig if the layout variable is set to \"my-layout\" (in the front matter)
    2. \n
  2. if not, with index.html.twig if the file exists
    3. \n
  3. if not, with home.html.twig if the file exists
    4. \n
  4. if not, with list.html.twig if the file exists
    5. \n
\n

All rules are detailed below, for each page type, in the priority order.

\n

Type homepage

\n
    \n
  1. <layout>.<format>.twig
    2. \n
  2. index.<format>.twig
    3. \n
  3. home.<format>.twig
    4. \n
  4. list.<format>.twig
    5. \n
  5. _default/<layout>.<format>.twig
    6. \n
  6. _default/index.<format>.twig
    7. \n
  7. _default/home.<format>.twig
    8. \n
  8. _default/list.<format>.twig
    9. \n
  9. _default/page.<format>.twig
    10. \n
\n

Type page

\n
    \n
  1. <section>/<layout>.<format>.twig
    2. \n
  2. <layout>.<format>.twig
    3. \n
  3. <section>/page.<format>.twig
    4. \n
  4. _default/<layout>.<format>.twig
    5. \n
  5. page.<format>.twig
    6. \n
  6. _default/page.<format>.twig
    7. \n
\n

Type section

\n
    \n
  1. <layout>.<format>.twig
    2. \n
  2. <section>/index.<format>.twig
    3. \n
  3. <section>/list.<format>.twig
    4. \n
  4. section/<section>.<format>.twig
    5. \n
  5. <parent>/index.<format>.twig, <parent>/list.<format>.twig and section/<parent>.<format>.twig, for each parent section of a sub-section (nearest first)
    6. \n
  6. _default/section.<format>.twig
    7. \n
  7. list.<format>.twig
    8. \n
  8. _default/list.<format>.twig
    9. \n
\n\n

Type vocabulary

\n
    \n
  1. taxonomy/<plural>.<format>.twig
    2. \n
  2. vocabulary.<format>.twig
    3. \n
  3. _default/vocabulary.<format>.twig
    4. \n
\n

Type term

\n
    \n
  1. taxonomy/<plural>/<term>.<format>.twig
    2. \n
  2. taxonomy/<singular>.<format>.twig
    3. \n
  3. term.<format>.twig
    4. \n
  4. _default/term.<format>.twig
    5. \n
  5. _default/list.<format>.twig
    6. \n
\n\n\n", "language": "en" }, { "id": "https://cecil.app/documentation/templates/reference/functions/", "url": "https://cecil.app/documentation/templates/reference/functions/", "title": "Functions", "summary": "url, html, readtime, hash, cache_key, getenv, dump, etc.", "date_published": "2021-05-07T00:00:00+00:00", "date_modified": "2026-10-05T00:00:00+00:00","content_text": "Functions\n\nFunctions can be called to generate content. Functions are called by their name followed by parentheses (()) and may have arguments.\n\nurl\nCreates a valid URL for a page, a menu entry, an asset, a page ID or a path.\n{{ url(value, {options}) }}\n\n\n\nOption\nDescription\nType\nDefault\n\n\n\n\ncanonical\nPrefix URL with baseurl or use canonical.url if exists.\nboolean\nfalse\n\n\nformat\nDefines page output format (e.g.: json).\nstring\nhtml\n\n\nlanguage\nDefines page language (e.g.: fr).\nstring\nnull\n\n\n\nExamples:\n{# page #}\n{{ url(page) }}\n{{ url(page, {canonical: true}) }}\n{{ url(page, {format: json}) }}\n{{ url(page, {language: fr}) }}\n{# menu entry #}\n{{ url(site.menus.main.about) }}\n{# asset #}\n{{ url(asset('styles.css')) }}\n{# page ID #}\n{{ url('page-id') }}\n{# path #}\n{{ url('about-me\/') }}\n{{ url('tags\/' ~ tag) }}\nFor convenience the url function is also available as a filter:\n{# page #}\n{{ page|url }}\n{{ page|url({canonical: true, format: json, language: fr}) }}\n{# asset #}\n{{ asset('styles.css')|url }}\nWhen the value is a string, url() slugifies it to find a matching page ID (e.g.: url('tags\/My Tag') returns the URL of the page tags\/my-tag). If no page matches, the string is kept as a path, with invalid characters (e.g.: spaces) percent-encoded.\nhtml\nCreates an HTML element from an asset (or an array of assets with custom attributes).\n{{ html(asset, {attributes}, {options}) }}\n{# dedicated functions for each common type of asset #}\n{{ css(asset) }}\n{{ js(asset) }}\n{{ image(asset) }}\n{{ audio(asset) }}\n{{ video(asset) }}\n\n\n\nOption\nDescription\nType\n\n\n\n\nattributes\nAdds name=\"value\" couple to the HTML element.\narray\n\n\noptions\n{preload: boolean}: preloads.For images:{formats: array}: adds alternative formats.{responsive: bool|string}: adds responsive images (based on width or pixels density).{placeholder: string}: fills the image background before loading (color or lqip).\narray\n\n\n\nSince version 8.42.0, the html function replace the deprecated html filter.\nYou can define a global default behavior of images options (formats, responsive and placeholder) through the layouts configuration.\nWhen layouts.images.dark_suffix is configured (e.g. .dark), Cecil automatically looks for a dark variant of each image (e.g. photo.dark.jpg alongside photo.jpg) and generates a <picture> element with a <source media=\"(prefers-color-scheme: dark)\">.\nIn the same way, when layouts.images.mobile_suffix is configured (e.g. .mobile), Cecil looks for a mobile variant of each image (e.g. photo.mobile.jpg) and adds a <source> with the layouts.images.mobile_media_query media query. If a dark variant of the mobile image exists (e.g. photo.mobile.dark.jpg), it is used on mobile with dark color scheme.\nExamples:\n{# CSS with an attribute #}\n{{ html(asset('print.css'), {media: 'print'}) }}\n{# CSS with an attribute and an option #}\n{{ html(asset('styles.css'), {title: 'Main theme'}, {preload: true}) }}\n{# Array of assets with media query #}\n{{ html([\n {asset: asset('css\/style.css')},\n {asset: asset('css\/style-dark.css'), attributes: {media: '(prefers-color-scheme: dark)'}}\n]) }}\n{# JavaScript #}\n{{ html(asset('script.js')) }}\n{# image without specific attributes nor options #}\n{{ html(asset('image.png')) }}\n{# image with specific attributes, responsive images and alternative formats #}\n{{ html(asset('image.jpg'), {alt: 'Description', loading: 'lazy'}, {responsive: true, formats: ['avif', 'webp']}) }}\n{# image with responsive pixels density images #}\n{{ html(asset('image.jpg'), options={responsive: 'density'}, attributes={width: 256}) }}\n{# image with a Low-Quality Image Placeholder #}\n{{ html(asset('image.jpg'), {alt: 'Description', loading: 'lazy'}, {placeholder: 'lqip'}) }}\n{# Audio #}\n{{ html(asset('audio.mp3')) }}\n{# Video #}\n{{ html(asset('video.mp4')) }}\nFor convenience the html function stay available as a filter (but is considered as deprecated):\n{{ asset|html({attributes}, {options}) }}\nreadtime\nDetermines read time of a text, in minutes.\n{{ readtime(value) }}\nExample:\n{{ readtime(page.content) }} min\nhash\nCalculates the hash of an object, an array or a string with a given algorithm.\n{{ hash(value, algorithm) }}\nalgorithm can be any algorithm supported by PHP's hash() function (e.g.: md5, sha256, etc.). Default is xxh128.\nExample:\n{{ hash('my string', 'sha256') }}\ncache_key\nCalculates a cache key for fragments cache based on a name and an optional value.\n{% cache cache_key(name, value) %}\n {# cacheable content #}\n{% endcache %}\nThe function adds a hash of the value (could be a string, an array or an object) to the name (and the current language and build ID to be sure the generated cache key is unique) so if the value is changed the cache key is changed too and the cache is automatically cleared.\ngetenv\nGets the value of an environment variable from its key.\n{{ getenv(var) }}\nExample:\n{{ getenv('VAR') }}\ndump\nThe dump function dumps information about a template variable. This is mostly useful to debug a template that does not behave as expected by introspecting its variables:\n{{ dump(user) }}\nThe debug mode must be enabled.\nd\nThe d() function is the HTML version of dump() and use the Symfony VarDumper Component behind the scenes.\n{{ d(variable, {theme: light}) }}\n\nIf variable is not provided then the function returns the current Twig context\nAvailable themes are « light » (default) and « dark »\n\nThe debug mode must be enabled.", "content_html": "

Functions

\n
\n

Functions can be called to generate content. Functions are called by their name followed by parentheses (()) and may have arguments.

\n
\n

url

\n

Creates a valid URL for a page, a menu entry, an asset, a page ID or a path.

\n
{{ url(value, {options}) }}
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
OptionDescriptionTypeDefault
canonicalPrefix URL with baseurl or use canonical.url if exists.booleanfalse
formatDefines page output format (e.g.: json).stringhtml
languageDefines page language (e.g.: fr).stringnull
\n

Examples:

\n
{# page #}\n{{ url(page) }}\n{{ url(page, {canonical: true}) }}\n{{ url(page, {format: json}) }}\n{{ url(page, {language: fr}) }}\n{# menu entry #}\n{{ url(site.menus.main.about) }}\n{# asset #}\n{{ url(asset('styles.css')) }}\n{# page ID #}\n{{ url('page-id') }}\n{# path #}\n{{ url('about-me/') }}\n{{ url('tags/' ~ tag) }}
\n\n\n

html

\n

Creates an HTML element from an asset (or an array of assets with custom attributes).

\n
{{ html(asset, {attributes}, {options}) }}\n{# dedicated functions for each common type of asset #}\n{{ css(asset) }}\n{{ js(asset) }}\n{{ image(asset) }}\n{{ audio(asset) }}\n{{ video(asset) }}
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
OptionDescriptionType
attributesAdds name=\"value\" couple to the HTML element.array
options{preload: boolean}: preloads.
For images:
{formats: array}: adds alternative formats.
{responsive: bool|string}: adds responsive images (based on width or pixels density).
{placeholder: string}: fills the image background before loading (color or lqip).		array
\n\n\n

Examples:

\n
{# CSS with an attribute #}\n{{ html(asset('print.css'), {media: 'print'}) }}\n{# CSS with an attribute and an option #}\n{{ html(asset('styles.css'), {title: 'Main theme'}, {preload: true}) }}\n{# Array of assets with media query #}\n{{ html([\n  {asset: asset('css/style.css')},\n  {asset: asset('css/style-dark.css'), attributes: {media: '(prefers-color-scheme: dark)'}}\n]) }}\n{# JavaScript #}\n{{ html(asset('script.js')) }}\n{# image without specific attributes nor options #}\n{{ html(asset('image.png')) }}\n{# image with specific attributes, responsive images and alternative formats #}\n{{ html(asset('image.jpg'), {alt: 'Description', loading: 'lazy'}, {responsive: true, formats: ['avif', 'webp']}) }}\n{# image with responsive pixels density images #}\n{{ html(asset('image.jpg'), options={responsive: 'density'}, attributes={width: 256}) }}\n{# image with a Low-Quality Image Placeholder #}\n{{ html(asset('image.jpg'), {alt: 'Description', loading: 'lazy'}, {placeholder: 'lqip'}) }}\n{# Audio #}\n{{ html(asset('audio.mp3')) }}\n{# Video #}\n{{ html(asset('video.mp4')) }}
\n\n

readtime

\n

Determines read time of a text, in minutes.

\n
{{ readtime(value) }}
\n

Example:

\n
{{ readtime(page.content) }} min
\n

hash

\n

Calculates the hash of an object, an array or a string with a given algorithm.

\n
{{ hash(value, algorithm) }}
\n

algorithm can be any algorithm supported by PHP's hash() function (e.g.: md5, sha256, etc.). Default is xxh128.

\n

Example:

\n
{{ hash('my string', 'sha256') }}
\n

cache_key

\n

Calculates a cache key for fragments cache based on a name and an optional value.

\n
{% cache cache_key(name, value) %}\n  {# cacheable content #}\n{% endcache %}
\n

The function adds a hash of the value (could be a string, an array or an object) to the name (and the current language and build ID to be sure the generated cache key is unique) so if the value is changed the cache key is changed too and the cache is automatically cleared.

\n

getenv

\n

Gets the value of an environment variable from its key.

\n
{{ getenv(var) }}
\n

Example:

\n
{{ getenv('VAR') }}
\n

dump

\n

The dump function dumps information about a template variable. This is mostly useful to debug a template that does not behave as expected by introspecting its variables:

\n
{{ dump(user) }}
\n\n

d

\n

The d() function is the HTML version of dump() and use the Symfony VarDumper Component behind the scenes.

\n
{{ d(variable, {theme: light}) }}
\n\n", "language": "en" }, { "id": "https://cecil.app/documentation/templates/variables/", "url": "https://cecil.app/documentation/templates/variables/", "title": "Variables", "summary": "Variables available in templates: site, page and cecil.", "date_published": "2021-05-07T00:00:00+00:00", "date_modified": "2026-10-06T00:00:00+00:00","content_text": "Variables\n\nThe application passes variables to the templates for manipulation in the template. Variables may have attributes or elements you can access, too.\nUse a dot (.) to access attributes of a variable: {{ foo.bar }}\n\nYou can use variables from different scopes: site, page, cecil.\nsite\nThe site variable contains built-in variables and those set in the configuration.\n\n\n\nVariable\nDescription\n\n\n\n\nsite.pages\nCollection of all pages, in the current language.\n\n\nsite.allpages\nCollection of all pages, in all languages.\n\n\nsite.page(id)\nA page with the given ID.\n\n\nsite.taxonomies\nCollection of vocabularies.\n\n\nsite.home\nID of the home page.\n\n\nsite.time\nCurrent Timestamp.\n\n\nsite.debug\nDebug mode status (true or false).\n\n\nsite.build\nCurrent build ID.\n\n\n\nExample:\ntitle: \"My amazing website!\"\nCan be displayed in a template with:\n{{ site.title }}\nUse showable method on pages collection to return only published and not virtual\/redirect\/excluded pages.\nExample:\n{% for page in site.pages.showable %}\n <a href=\"{{ url(page) }}\">{{ page.title }}<\/a>\n{% endfor %}\nIn some cases, you can encounter conflicts between configuration and built-in variables (e.g. pages.default configuration). In that case, you can use config.<variable> (where <variable> is the variable name\/path) to access the raw configuration directly.\nExample:\n{{ config.pages.default.sitemap.priority }}\nsite.menus\nLoop on site.menus.<menu> to get each entry of the <menu> collection (e.g.: main).\n\n\n\nVariable\nDescription\n\n\n\n\n<entry>.name\nEntry name.\n\n\n<entry>.url\nEntry URL.\n\n\n<entry>.weight\nEntry weight (useful to sort menu entries).\n\n\n\nExample:\n<nav>\n <ol>\n {% for entry in site.menus.main|sort_by_weight %}\n <li><a href=\"{{ url(entry.url) }}\" data-weight=\"{{ entry.weight }}\">{{ entry.name }}<\/a><\/li>\n {% endfor %}\n <\/ol>\n<\/nav>\nsite.language\nInformation about the current language.\n\n\n\nVariable\nDescription\n\n\n\n\nsite.language\nLanguage code (e.g.: en).\n\n\nsite.language.name\nLanguage name (e.g.: English).\n\n\nsite.language.locale\nLanguage locale code (e.g.: en_US).\n\n\nsite.language.weight\nLanguage position in the languages list.\n\n\n\nYou can retrieve name, locale and weight of a specific language by passing its code as a parameter.\ne.g.: site.language.name('fr').\nsite.static\nThe static files collection can be accessed via site.static if the static load is enabled.\nEach file exposes the following properties:\n\npath: relative path (e.g.: \/images\/img-1.jpg)\ndate: creation date (timestamp)\nupdated: modification date (timestamp)\nname: name (e.g.: img-1.jpg)\nbasename: name without extension (e.g.: img-1)\next: extension (e.g.: jpg)\ntype: media type (e.g.: image)\nsubtype: media sub type (e.g.: image\/jpeg)\nexif: image EXIF data (array)\naudio: Mp3Info object\nvideo: array of basic video information (duration in seconds, width and height)\n\nsite.data\nA data collection can be accessed via site.data.<filename> (without file extension).\nExamples:\n\ndata\/authors.yml : site.data.authors\ndata\/authors.fr.yml : site.data.authors (if site.language = \"fr\")\ndata\/galleries\/gallery-1.json : site.data.galleries['gallery-1']\n\npage\nThe page variable contains built-in variables of a page and those set in the front matter.\n\n\n\nVariable\nDescription\nExample\n\n\n\n\npage.id\nUnique identifier.\nblog\/post-1\n\n\npage.title\nFile name (without extension).\nPost 1\n\n\npage.date\nFile creation date.\nDateTime\n\n\npage.body\nFile body.\nMarkdown\n\n\npage.content\nFile body converted in HTML.\nHTML\n\n\npage.section\nFile root folder (slugified).\nblog\n\n\npage.path\nFile path (slugified).\nblog\/post-1\n\n\npage.slug\nFile name (slugified).\npost-1\n\n\npage.filepath\nFile system path.\nBlog\/Post 1.md\n\n\npage.type\nhomepage, page, section, vocabulary or term.\npage\n\n\npage.pages\nCollection of all sub pages.\nCollection\n\n\npage.translations\nCollection of translated pages.\nCollection\n\n\n\nUse showable method on pages collection to return only published and not virtual\/redirect\/excluded pages.\nExample:\n{% for page in page.pages.showable %}\n <a href=\"{{ url(page) }}\">{{ page.title }}<\/a>\n{% endfor %}\nNested sections\nIn a nested sections context, page.parent, page.ancestors, page.sections and page.toplevel help you build navigation.\n\n\n\nVariable\nDescription\nExample\n\n\n\n\npage.parent\nParent section's page (null if none).\nPage\n\n\npage.ancestors\nCollection of ancestor sections (nearest first).\nCollection\n\n\npage.sections\nCollection of immediate descendant sections.\nCollection\n\n\npage.toplevel\ntrue if the page is a top level section.\nBoolean\n\n\n\nBreadcrumb (from the home page to the current page):\n<nav aria-label=\"breadcrumb\">\n <ul>\n <li><a href=\"{{ url(site.home) }}\">{{ site.title }}<\/a><\/li>\n {% for section in page.ancestors|reverse %}\n <li><a href=\"{{ url(section) }}\">{{ section.title }}<\/a><\/li>\n {% endfor %}\n {% if page.id != site.home %}\n <li><a href=\"{{ url(page) }}\" aria-current=\"page\">{{ page.title }}<\/a><\/li>\n {% endif %}\n <\/ul>\n<\/nav>\nA ready-to-use breadcrumb.html.twig partial is available:\n{{ include('partials\/breadcrumb.html.twig') }}\nSub-sections menu (immediate descendant sections of the current section):\n{% if page.sections|length %}\n<ul>\n {% for section in page.sections|sort_by_title %}\n <li><a href=\"{{ url(section) }}\">{{ section.title }}<\/a><\/li>\n {% endfor %}\n<\/ul>\n{% endif %}\nMain navigation limited to top level sections (from any page):\n<nav>\n {% for section in site.page(site.home).sections|sort_by_title %}\n <a href=\"{{ url(section) }}\">{{ section.title }}<\/a>\n {% endfor %}\n<\/nav>\nLink to the parent section:\n{% if page.parent %}\n<a href=\"{{ url(page.parent) }}\">← {{ page.parent.title }}<\/a>\n{% endif %}\npage.<prev\/next>\nNavigation between pages within the same section, sorted according to the section's sortby (chronological order for dates).\nWith sub-sections, navigation follows the sections tree: the pages of a top level Section and of all its sub-sections are chained, each sub-section (its index page) being placed among the pages of its parent Section and followed by its own pages.\n\n\n\nVariable\nDescription\nExample\n\n\n\n\npage.prev\nPrevious page.\nPage\n\n\npage.next\nNext page.\nPage\n\n\n\nExample:\n<a href=\"{{ url(page.prev) }}\">{{ page.prev.title }}<\/a>\npage.paginator\nPaginator helps you build navigation for list pages: homepage, sections, and taxonomies.\n\n\n\nVariable\nDescription\n\n\n\n\npage.paginator.pages\nPages Collection.\n\n\npage.paginator.pages_total\nNumber total of pages.\n\n\npage.paginator.count\nNumber of paginator's pages.\n\n\npage.paginator.current\nPosition index of the current page.\n\n\npage.paginator.links.first\nPage ID of the first page.\n\n\npage.paginator.links.prev\nPage ID of the previous page.\n\n\npage.paginator.links.self\nPage ID of the current page.\n\n\npage.paginator.links.next\nPage ID of the next page.\n\n\npage.paginator.links.last\nPage ID of the last page.\n\n\npage.paginator.links.path\nPage ID without the position index.\n\n\n\nBecause links entries are Page ID you must use the url() function to create working links.\ne.g: {{ url(page.paginator.links.next) }}\nExample:\n{% if page.paginator %}\n<div>\n {% if page.paginator.links.prev is defined %}\n <a href=\"{{ url(page.paginator.links.prev) }}\">Previous<\/a>\n {% endif %}\n {% if page.paginator.links.next is defined %}\n <a href=\"{{ url(page.paginator.links.next) }}\">Next<\/a>\n {% endif %}\n<\/div>\n{% endif %}\nExample:\n{% if page.paginator %}\n<div>\n {% for paginator_index in 1..page.paginator.count %}\n {% if paginator_index != page.paginator.current %}\n {% if paginator_index == 1 %}\n <a href=\"{{ url(page.paginator.links.first) }}\">{{ paginator_index }}<\/a>\n {% else %}\n <a href=\"{{ url(page.paginator.links.path ~ '\/' ~ paginator_index) }}\">{{ paginator_index }}<\/a>\n {% endif %}\n {% else %}\n {{ paginator_index }}\n {% endif %}\n {% endfor %}\n<\/div>\n{% endif %}\nTaxonomy\nVariables available in vocabulary and term templates.\nVocabulary\nPage \/<plural>\/ (e.g.: \/categories\/).\n\n\n\nVariable\nDescription\n\n\n\n\npage.plural\nVocabulary name in plural form.\n\n\npage.singular\nVocabulary name in singular form.\n\n\npage.terms\nList of terms (Collection).\n\n\n\nEach term of page.terms provides term.id (term ID, e.g.: categories\/php), term.name (term name, e.g.: PHP) and the number of its pages with term|length.\nTerm\nPage \/<plural>\/<term>\/ (e.g.: \/categories\/php\/).\n\n\n\nVariable\nDescription\n\n\n\n\npage.title\nTerm name.\n\n\npage.term\nTerm ID (e.g.: categories\/php).\n\n\npage.plural\nVocabulary name in plural form.\n\n\npage.singular\nVocabulary name in singular form.\n\n\npage.pages\nList of pages in this term, sorted by date (Collection).\n\n\n\nTaxonomy example\nConfiguration:\ntaxonomies:\n categories: category\nPage front matter:\n---\ncategories: [\"Data Sovereignty\"]\n---\nList of terms (\/categories\/), in layouts\/taxonomy\/categories.html.twig:\n{% extends 'page.html.twig' %}\n\n{% block content %}\n <h1>{{ page.title }}<\/h1>\n <ul>\n {% for term in page.terms %}\n <li><a href=\"{{ url(term.id) }}\">{{ term.name }}<\/a> ({{ term|length }})<\/li>\n {% endfor %}\n <\/ul>\n{% endblock %}\nList of pages of a term (\/categories\/data-sovereignty\/), in layouts\/taxonomy\/category.html.twig:\n{% extends 'page.html.twig' %}\n\n{% block content %}\n <h1>{{ page.title }}<\/h1>\n {% for p in page.paginator.pages ?? page.pages %}\n <article>\n <h2><a href=\"{{ url(p) }}\">{{ p.title }}<\/a><\/h2>\n <\/article>\n {% endfor %}\n <a href=\"{{ url(page.plural) }}\">All {{ page.plural }}<\/a>\n{% endblock %}\nLinks to the terms of the current page, in a page template:\n{% for category in page.categories ?? [] %}\n <a href=\"{{ url('categories\/' ~ category) }}\">{{ category }}<\/a>\n{% endfor %}\nThe url() function slugifies the given string to find the matching page: url('categories\/Data Sovereignty') returns \/categories\/data-sovereignty\/.\nYou can also use the built-in partial {{ include('partials\/terms-list.html.twig', {vocabulary: 'categories'}) }}.\ncecil\n\n\n\nVariable\nDescription\n\n\n\n\ncecil.url\nURL of the Cecil website.\n\n\ncecil.version\nCecil current version.\n\n\ncecil.poweredby\nPrint Cecil v%s, with %s is the current version.\n\n\n", "content_html": "

Variables

\n
\n

The application passes variables to the templates for manipulation in the template. Variables may have attributes or elements you can access, too.
\nUse a dot (.) to access attributes of a variable: {{ foo.bar }}

\n
\n

You can use variables from different scopes: site, page, cecil.

\n

site

\n

The site variable contains built-in variables and those set in the configuration.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
VariableDescription
site.pagesCollection of all pages, in the current language.
site.allpagesCollection of all pages, in all languages.
site.page(id)A page with the given ID.
site.taxonomiesCollection of vocabularies.
site.homeID of the home page.
site.timeCurrent Timestamp.
site.debugDebug mode status (true or false).
site.buildCurrent build ID.
\n

Example:

\n
title: \"My amazing website!\"
\n

Can be displayed in a template with:

\n
{{ site.title }}
\n\n\n

site.menus

\n

Loop on site.menus.<menu> to get each entry of the <menu> collection (e.g.: main).

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
VariableDescription
<entry>.nameEntry name.
<entry>.urlEntry URL.
<entry>.weightEntry weight (useful to sort menu entries).
\n

Example:

\n
<nav>\n  <ol>\n  {% for entry in site.menus.main|sort_by_weight %}\n    <li><a href=\"{{ url(entry.url) }}\" data-weight=\"{{ entry.weight }}\">{{ entry.name }}</a></li>\n  {% endfor %}\n  </ol>\n</nav>
\n

site.language

\n

Information about the current language.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
VariableDescription
site.languageLanguage code (e.g.: en).
site.language.nameLanguage name (e.g.: English).
site.language.localeLanguage locale code (e.g.: en_US).
site.language.weightLanguage position in the languages list.
\n\n

site.static

\n

The static files collection can be accessed via site.static if the static load is enabled.

\n

Each file exposes the following properties:

\n\n

site.data

\n

A data collection can be accessed via site.data.<filename> (without file extension).

\n

Examples:

\n\n

page

\n

The page variable contains built-in variables of a page and those set in the front matter.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
VariableDescriptionExample
page.idUnique identifier.blog/post-1
page.titleFile name (without extension).Post 1
page.dateFile creation date.DateTime
page.bodyFile body.Markdown
page.contentFile body converted in HTML.HTML
page.sectionFile root folder (slugified).blog
page.pathFile path (slugified).blog/post-1
page.slugFile name (slugified).post-1
page.filepathFile system path.Blog/Post 1.md
page.typehomepage, page, section, vocabulary or term.page
page.pagesCollection of all sub pages.Collection
page.translationsCollection of translated pages.Collection
\n\n

Nested sections

\n

In a nested sections context, page.parent, page.ancestors, page.sections and page.toplevel help you build navigation.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
VariableDescriptionExample
page.parentParent section's page (null if none).Page
page.ancestorsCollection of ancestor sections (nearest first).Collection
page.sectionsCollection of immediate descendant sections.Collection
page.topleveltrue if the page is a top level section.Boolean
\n

Breadcrumb (from the home page to the current page):

\n
<nav aria-label=\"breadcrumb\">\n  <ul>\n    <li><a href=\"{{ url(site.home) }}\">{{ site.title }}</a></li>\n    {% for section in page.ancestors|reverse %}\n    <li><a href=\"{{ url(section) }}\">{{ section.title }}</a></li>\n    {% endfor %}\n    {% if page.id != site.home %}\n    <li><a href=\"{{ url(page) }}\" aria-current=\"page\">{{ page.title }}</a></li>\n    {% endif %}\n  </ul>\n</nav>
\n\n

Sub-sections menu (immediate descendant sections of the current section):

\n
{% if page.sections|length %}\n<ul>\n  {% for section in page.sections|sort_by_title %}\n  <li><a href=\"{{ url(section) }}\">{{ section.title }}</a></li>\n  {% endfor %}\n</ul>\n{% endif %}
\n

Main navigation limited to top level sections (from any page):

\n
<nav>\n  {% for section in site.page(site.home).sections|sort_by_title %}\n  <a href=\"{{ url(section) }}\">{{ section.title }}</a>\n  {% endfor %}\n</nav>
\n

Link to the parent section:

\n
{% if page.parent %}\n<a href=\"{{ url(page.parent) }}\">← {{ page.parent.title }}</a>\n{% endif %}
\n

page.<prev/next>

\n

Navigation between pages within the same section, sorted according to the section's sortby (chronological order for dates).

\n

With sub-sections, navigation follows the sections tree: the pages of a top level Section and of all its sub-sections are chained, each sub-section (its index page) being placed among the pages of its parent Section and followed by its own pages.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
VariableDescriptionExample
page.prevPrevious page.Page
page.nextNext page.Page
\n

Example:

\n
<a href=\"{{ url(page.prev) }}\">{{ page.prev.title }}</a>
\n

page.paginator

\n

Paginator helps you build navigation for list pages: homepage, sections, and taxonomies.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
VariableDescription
page.paginator.pagesPages Collection.
page.paginator.pages_totalNumber total of pages.
page.paginator.countNumber of paginator's pages.
page.paginator.currentPosition index of the current page.
page.paginator.links.firstPage ID of the first page.
page.paginator.links.prevPage ID of the previous page.
page.paginator.links.selfPage ID of the current page.
page.paginator.links.nextPage ID of the next page.
page.paginator.links.lastPage ID of the last page.
page.paginator.links.pathPage ID without the position index.
\n\n

Example:

\n
{% if page.paginator %}\n<div>\n  {% if page.paginator.links.prev is defined %}\n  <a href=\"{{ url(page.paginator.links.prev) }}\">Previous</a>\n  {% endif %}\n  {% if page.paginator.links.next is defined %}\n  <a href=\"{{ url(page.paginator.links.next) }}\">Next</a>\n  {% endif %}\n</div>\n{% endif %}
\n

Example:

\n
{% if page.paginator %}\n<div>\n  {% for paginator_index in 1..page.paginator.count %}\n    {% if paginator_index != page.paginator.current %}\n      {% if paginator_index == 1 %}\n  <a href=\"{{ url(page.paginator.links.first) }}\">{{ paginator_index }}</a>\n      {% else %}\n  <a href=\"{{ url(page.paginator.links.path ~ '/' ~ paginator_index) }}\">{{ paginator_index }}</a>\n      {% endif %}\n    {% else %}\n  {{ paginator_index }}\n    {% endif %}\n  {% endfor %}\n</div>\n{% endif %}
\n

Taxonomy

\n

Variables available in vocabulary and term templates.

\n

Vocabulary

\n

Page /<plural>/ (e.g.: /categories/).

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
VariableDescription
page.pluralVocabulary name in plural form.
page.singularVocabulary name in singular form.
page.termsList of terms (Collection).
\n

Each term of page.terms provides term.id (term ID, e.g.: categories/php), term.name (term name, e.g.: PHP) and the number of its pages with term|length.

\n

Term

\n

Page /<plural>/<term>/ (e.g.: /categories/php/).

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
VariableDescription
page.titleTerm name.
page.termTerm ID (e.g.: categories/php).
page.pluralVocabulary name in plural form.
page.singularVocabulary name in singular form.
page.pagesList of pages in this term, sorted by date (Collection).
\n

Taxonomy example

\n

Configuration:

\n
taxonomies:\n  categories: category
\n

Page front matter:

\n
---\ncategories: [\"Data Sovereignty\"]\n---
\n

List of terms (/categories/), in layouts/taxonomy/categories.html.twig:

\n
{% extends 'page.html.twig' %}\n\n{% block content %}\n  <h1>{{ page.title }}</h1>\n  <ul>\n  {% for term in page.terms %}\n    <li><a href=\"{{ url(term.id) }}\">{{ term.name }}</a> ({{ term|length }})</li>\n  {% endfor %}\n  </ul>\n{% endblock %}
\n

List of pages of a term (/categories/data-sovereignty/), in layouts/taxonomy/category.html.twig:

\n
{% extends 'page.html.twig' %}\n\n{% block content %}\n  <h1>{{ page.title }}</h1>\n  {% for p in page.paginator.pages ?? page.pages %}\n    <article>\n      <h2><a href=\"{{ url(p) }}\">{{ p.title }}</a></h2>\n    </article>\n  {% endfor %}\n  <a href=\"{{ url(page.plural) }}\">All {{ page.plural }}</a>\n{% endblock %}
\n

Links to the terms of the current page, in a page template:

\n
{% for category in page.categories ?? [] %}\n  <a href=\"{{ url('categories/' ~ category) }}\">{{ category }}</a>\n{% endfor %}
\n\n

cecil

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
VariableDescription
cecil.urlURL of the Cecil website.
cecil.versionCecil current version.
cecil.poweredbyPrint Cecil v%s, with %s is the current version.
", "language": "en" }, { "id": "https://cecil.app/documentation/templates/reference/sorts/", "url": "https://cecil.app/documentation/templates/reference/sorts/", "title": "Sorts", "summary": "Sort collections of pages, menus or taxonomies.", "date_published": "2021-05-07T00:00:00+00:00", "date_modified": "2026-10-05T00:00:00+00:00","content_text": "Sorts\nSorting collections (of pages, menus or taxonomies).\nsort_by_title\nSorts a collection by title (with natural sort).\n{{ collection|sort_by_title }}\nExample:\n{{ site.pages|sort_by_title }}\nsort_by_date\nSorts a collection by date (most recent first).\n{{ collection|sort_by_date(variable='date', desc_title=false) }}\nExample:\n{# sort by date #}\n{{ site.pages|sort_by_date }}\n{# sort by updated variable instead of date #}\n{{ site.pages|sort_by_date(variable='updated') }}\n{# sort items with the same date by desc title #}\n{{ site.pages|sort_by_date(desc_title=true) }}\n{# reverse sort #}\n{{ site.pages|sort_by_date|reverse }}\nsort_by_weight\nSorts a collection by weight (lighter first).\n{{ collection|sort_by_weight }}\nExample:\n{{ site.menus.main|sort_by_weight }}\nsort\nFor more complex cases, you should use Twig’s native sort.\nExample:\n{% set files = site.static|sort((a, b) => a.date|date('U') < b.date|date('U')) %}", "content_html": "

Sorts

\n

Sorting collections (of pages, menus or taxonomies).

\n

sort_by_title

\n

Sorts a collection by title (with natural sort).

\n
{{ collection|sort_by_title }}
\n

Example:

\n
{{ site.pages|sort_by_title }}
\n

sort_by_date

\n

Sorts a collection by date (most recent first).

\n
{{ collection|sort_by_date(variable='date', desc_title=false) }}
\n

Example:

\n
{# sort by date #}\n{{ site.pages|sort_by_date }}\n{# sort by updated variable instead of date #}\n{{ site.pages|sort_by_date(variable='updated') }}\n{# sort items with the same date by desc title #}\n{{ site.pages|sort_by_date(desc_title=true) }}\n{# reverse sort #}\n{{ site.pages|sort_by_date|reverse }}
\n

sort_by_weight

\n

Sorts a collection by weight (lighter first).

\n
{{ collection|sort_by_weight }}
\n

Example:

\n
{{ site.menus.main|sort_by_weight }}
\n

sort

\n

For more complex cases, you should use Twig’s native sort.

\n

Example:

\n
{% set files = site.static|sort((a, b) => a.date|date('U') < b.date|date('U')) %}
", "language": "en" }, { "id": "https://cecil.app/documentation/templates/reference/filters/", "url": "https://cecil.app/documentation/templates/reference/filters/", "title": "Filters", "summary": "filter_by, markdown_to_html, toc, slugify, excerpt, highlight, preg_*, etc.", "date_published": "2021-05-07T00:00:00+00:00", "date_modified": "2026-10-05T00:00:00+00:00","content_text": "Filters\nVariables can be modified by filters. Filters are separated from the variable by a pipe symbol (|). Multiple filters can be chained. The output of one filter is applied to the next.\n{{ page.title|truncate(25)|capitalize }}\nfilter_by\nFilters a pages collection by variable name\/value.\n{{ collection|filter_by(variable, value) }}\nExample:\n{{ pages|filter_by('section', 'blog') }}\nfilter\nFor more complex cases, you should use Twig’s native filter.\nExample:\n{% pages|filter(p => p.virtual == false and p.id not in ['page-1', 'page-2']) %}\nmarkdown_to_html\nConverts a Markdown string to HTML.\n{{ markdown|markdown_to_html }}\n{% apply markdown_to_html %}\n{# Markdown here #}\n{% endapply %}\nExamples:\n{% set markdown = '**This is bold text**' %}\n{{ markdown|markdown_to_html }}\n{% apply markdown_to_html %}\n**This is bold text**\n{% endapply %}\ntoc\nExtracts only headings matching the given selectors (h2, h3, etc.), or those defined in config pages.body.toc if not specified.\nThe format parameter defines the output format: html or json.\nThe url parameter is used to build links to headings.\n{{ markdown|toc(format, selectors, url) }}\nExamples:\n{{ page.body|toc }}\n{{ page.body|toc('html') }}\n{{ page.body|toc(selectors=['h2']) }}\n{{ page.body|toc(url=url(page)) }}\njson_decode\nConverts a JSON string to an array.\n{{ json|json_decode }}\nExample:\n{% set json = '{\"foo\": \"bar\"}' %}\n{% set array = json|json_decode %}\n{{ array.foo }}\nyaml_parse\nConverts a YAML string to an array.\n{{ yaml|yaml_parse }}\nExample:\n{% set yaml = 'key: value' %}\n{% set array = yaml|yaml_parse %}\n{{ array.key }}\nslugify\nConverts a string to a slug.\n{{ string|slugify }}\nu\nThe u filter wraps a text in a Unicode object (a Symfony UnicodeString instance) that exposes methods to \"manipulate\" the string.\nExample:\n{{ 'cecil_string with twig'|u.camel.title }}\n\nCecilStringWithTwig\n\nsingular\nThe singular filter transforms a given noun in its plural form into its singular version.\n{{ string|singular(locale)}}\nExample:\n{# English (en) rules are used by default #}\n{{ 'partitions'|singular }}\n\npartition\n\n{{ 'partitions'|singular('fr') }}\n\npartition\n\nplural\nThe plural filter transforms a given noun in its singular form into its plural version.\n{{ string|plural(locale)}}\nExample:\n{# English (en) rules are used by default #}\n{{ 'animal'|plural }}\n\nanimals\n\n{{ 'animal'|plural('fr') }}\n\nanimaux\n\nexcerpt\nTruncates a string and appends suffix.\n{{ string|excerpt(length, suffix) }}\n\n\n\nOption\nDescription\nType\nDefault\n\n\n\n\nlength\nTruncates after this number of characters.\ninteger\n450\n\n\nsuffix\nAppends characters.\nstring\n…\n\n\n\nExamples:\n{{ variable|excerpt }}\n{{ variable|excerpt(250, '...') }}\nexcerpt_html\nReads characters before or after <!-- excerpt --> or <!-- break --> tag.\nSee Content documentation for details.\n{{ string|excerpt_html({separator, capture}) }}\n\n\n\nOption\nDescription\nType\nDefault\n\n\n\n\nseparator\nString to use as separator.\nstring\nexcerpt|break\n\n\ncapture\nPart to capture, before or after the separator.\nstring\nbefore\n\n\n\nExamples:\n{{ variable|excerpt_html }}\n{{ variable|excerpt_html({separator: 'excerpt|break', capture: 'before'}) }}\n{{ variable|excerpt_html({capture: 'after'}) }}\nhighlight\nHighlights a code string with highlight.php.\n{{ code|highlight(language) }}\nExamples:\n{{ '<?php echo $highlighted->value; ?>'|highlight('php') }}\npreg_split\nSplits a string into an array using a regular expression.\n{{ string|preg_split(pattern, limit) }}\nExample:\n{% set headers = page.content|preg_split('\/<br[^>]*>\/') %}\npreg_match_all\nPerforms a regular expression match and return the group for all matches.\n{{ string|preg_match_all(pattern, group) }}\nExample:\n{% set tags = page.content|preg_match_all('\/<[^>]+>(.*)<\\\/[^>]+>\/') %}\nhex_to_rgb\nConverts a hexadecimal color to RGB.\n{{ color|hex_to_rgb }}", "content_html": "

Filters

\n

Variables can be modified by filters. Filters are separated from the variable by a pipe symbol (|). Multiple filters can be chained. The output of one filter is applied to the next.

\n
{{ page.title|truncate(25)|capitalize }}
\n

filter_by

\n

Filters a pages collection by variable name/value.

\n
{{ collection|filter_by(variable, value) }}
\n

Example:

\n
{{ pages|filter_by('section', 'blog') }}
\n

filter

\n

For more complex cases, you should use Twig’s native filter.

\n

Example:

\n
{% pages|filter(p => p.virtual == false and p.id not in ['page-1', 'page-2']) %}
\n

markdown_to_html

\n

Converts a Markdown string to HTML.

\n
{{ markdown|markdown_to_html }}
\n
{% apply markdown_to_html %}\n{# Markdown here #}\n{% endapply %}
\n

Examples:

\n
{% set markdown = '**This is bold text**' %}\n{{ markdown|markdown_to_html }}
\n
{% apply markdown_to_html %}\n**This is bold text**\n{% endapply %}
\n

toc

\n

Extracts only headings matching the given selectors (h2, h3, etc.), or those defined in config pages.body.toc if not specified.
\nThe format parameter defines the output format: html or json.
\nThe url parameter is used to build links to headings.

\n
{{ markdown|toc(format, selectors, url) }}
\n

Examples:

\n
{{ page.body|toc }}\n{{ page.body|toc('html') }}\n{{ page.body|toc(selectors=['h2']) }}\n{{ page.body|toc(url=url(page)) }}
\n

json_decode

\n

Converts a JSON string to an array.

\n
{{ json|json_decode }}
\n

Example:

\n
{% set json = '{\"foo\": \"bar\"}' %}\n{% set array = json|json_decode %}\n{{ array.foo }}
\n

yaml_parse

\n

Converts a YAML string to an array.

\n
{{ yaml|yaml_parse }}
\n

Example:

\n
{% set yaml = 'key: value' %}\n{% set array = yaml|yaml_parse %}\n{{ array.key }}
\n

slugify

\n

Converts a string to a slug.

\n
{{ string|slugify }}
\n

u

\n

The u filter wraps a text in a Unicode object (a Symfony UnicodeString instance) that exposes methods to \"manipulate\" the string.

\n

Example:

\n
{{ 'cecil_string with twig'|u.camel.title }}
\n
\n

CecilStringWithTwig

\n
\n

singular

\n

The singular filter transforms a given noun in its plural form into its singular version.

\n
{{ string|singular(locale)}}
\n

Example:

\n
{# English (en) rules are used by default #}\n{{ 'partitions'|singular }}
\n
\n

partition

\n
\n
{{ 'partitions'|singular('fr') }}
\n
\n

partition

\n
\n

plural

\n

The plural filter transforms a given noun in its singular form into its plural version.

\n
{{ string|plural(locale)}}
\n

Example:

\n
{# English (en) rules are used by default #}\n{{ 'animal'|plural }}
\n
\n

animals

\n
\n
{{ 'animal'|plural('fr') }}
\n
\n

animaux

\n
\n

excerpt

\n

Truncates a string and appends suffix.

\n
{{ string|excerpt(length, suffix) }}
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
OptionDescriptionTypeDefault
lengthTruncates after this number of characters.integer450
suffixAppends characters.string…
\n

Examples:

\n
{{ variable|excerpt }}\n{{ variable|excerpt(250, '...') }}
\n

excerpt_html

\n

Reads characters before or after <!-- excerpt --> or <!-- break --> tag.
\nSee Content documentation for details.

\n
{{ string|excerpt_html({separator, capture}) }}
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
OptionDescriptionTypeDefault
separatorString to use as separator.stringexcerpt|break
capturePart to capture, before or after the separator.stringbefore
\n

Examples:

\n
{{ variable|excerpt_html }}\n{{ variable|excerpt_html({separator: 'excerpt|break', capture: 'before'}) }}\n{{ variable|excerpt_html({capture: 'after'}) }}
\n

highlight

\n

Highlights a code string with highlight.php.

\n
{{ code|highlight(language) }}
\n

Examples:

\n
{{ '<?php echo $highlighted->value; ?>'|highlight('php') }}
\n

preg_split

\n

Splits a string into an array using a regular expression.

\n
{{ string|preg_split(pattern, limit) }}
\n

Example:

\n
{% set headers = page.content|preg_split('/<br[^>]*>/') %}
\n

preg_match_all

\n

Performs a regular expression match and return the group for all matches.

\n
{{ string|preg_match_all(pattern, group) }}
\n

Example:

\n
{% set tags = page.content|preg_match_all('/<[^>]+>(.*)<\\/[^>]+>/') %}
\n

hex_to_rgb

\n

Converts a hexadecimal color to RGB.

\n
{{ color|hex_to_rgb }}
", "language": "en" }, { "id": "https://cecil.app/documentation/templates/components/", "url": "https://cecil.app/documentation/templates/components/", "title": "Components", "summary": "Create reusable template components.", "date_published": "2021-05-07T00:00:00+00:00", "date_modified": "2026-10-05T00:00:00+00:00","content_text": "Components\nCecil provides a components logic to give you the power making reusable template \"units\".\nThe components feature is provided by the Twig components extension created by Giorgio Pogliani.\nComponents syntax\nComponents are just Twig templates stored in the components\/ subdirectory and can be used anywhere in your templates:\n{# \/components\/button.twig #}\n<button {{ attributes.merge({class: 'rounded px-4'}) }}>\n {{ slot }}\n<\/button>\n\nThe slot variable is any content you will add between the opening and the close tag.\n\nTo reach a component you need to use the dedicated tag x followed by : and the filename of your component without extension:\n{# \/index.twig #}\n{% x:button with {class: 'text-white'} %}\n <strong>Click me<\/strong>\n{% endx %}\nIt will render:\n<button class=\"text-white rounded px-4\">\n <strong>Click me<\/strong>\n<\/button>", "content_html": "

Components

\n

Cecil provides a components logic to give you the power making reusable template \"units\".

\n\n

Components syntax

\n

Components are just Twig templates stored in the components/ subdirectory and can be used anywhere in your templates:

\n
{# /components/button.twig #}\n<button {{ attributes.merge({class: 'rounded px-4'}) }}>\n    {{ slot }}\n</button>
\n
\n

The slot variable is any content you will add between the opening and the close tag.

\n
\n

To reach a component you need to use the dedicated tag x followed by : and the filename of your component without extension:

\n
{# /index.twig #}\n{% x:button with {class: 'text-white'} %}\n    <strong>Click me</strong>\n{% endx %}
\n

It will render:

\n
<button class=\"text-white rounded px-4\">\n    <strong>Click me</strong>\n</button>
", "language": "en" }, { "id": "https://cecil.app/documentation/templates/localization/", "url": "https://cecil.app/documentation/templates/localization/", "title": "Localization", "summary": "Translate texts and localize dates in templates.", "date_published": "2021-05-07T00:00:00+00:00", "date_modified": "2026-10-05T00:00:00+00:00","content_text": "Localization\nCecil support text translation and date localization.\nText translation\nUses the trans tag or filter to translate texts in templates.\n{% trans with variables into locale %}{% endtrans %}\n{{ message|trans(variables = []) }}\nExamples\n{% trans %}Hello World!{% endtrans %}\n{{ message|trans }}\nInclude variables:\n{% trans with {'%name%': 'Arnaud'} %}Hello %name%!{% endtrans %}\n{{ message|trans({'%name%': 'Arnaud'}) }}\nForce locale:\n{% trans into 'fr_FR' %}Hello World!{% endtrans %}\nPluralize:\n{% trans with {'%count%': 42}%}{0}I don't have apples|{1}I have one apple|]1,Inf[I have %count% apples{% endtrans %}\nTranslation files\nTranslation files must be named messages.<locale>.<extension> and stored in the translations directory.\nSupported file extensions are defined by each translation format in layouts.translations.formats.\nThe locale code (e.g.: fr_FR) of a language is defined in the languages entries of the configuration.\nExample:\n<mywebsite>\n└─ translations\n ├─ messages.fr_FR.mo <- Machine Object format\n └─ messages.fr_FR.yaml <- Yaml format\nYou can easily extract translations from your templates with the following command:\nphp cecil.phar util:translations:extract --locale=<code> --show\nUse --save instead of (or in addition to) --show to save the translations to a file. The --locale option is required. The default output format is yaml (use --format=po for gettext PO format).\nPoedit is a simple and cross platform translation editor for gettext (PO), and Poedit Pro supports extraction of translation strings from templates out of the box.\nBe careful about the cache when you update translations files.\nCache can be cleared with with the following command:\nphp cecil.phar cache:clear:translations`\nDate localization\nUses the Twig format_date filter to localize a date in templates.\n{{ page.date|format_date('long') }}\n{# September 30, 2022 #}\nSupported values are: short, medium, long, and full.\nIf you want to use the format_date filter with other locales than \"en\", you should install the intl PHP extension.", "content_html": "

Localization

\n

Cecil support text translation and date localization.

\n

Text translation

\n

Uses the trans tag or filter to translate texts in templates.

\n
{% trans with variables into locale %}{% endtrans %}
\n
{{ message|trans(variables = []) }}
\n

Examples

\n
{% trans %}Hello World!{% endtrans %}
\n
{{ message|trans }}
\n

Include variables:

\n
{% trans with {'%name%': 'Arnaud'} %}Hello %name%!{% endtrans %}
\n
{{ message|trans({'%name%': 'Arnaud'}) }}
\n

Force locale:

\n
{% trans into 'fr_FR' %}Hello World!{% endtrans %}
\n

Pluralize:

\n
{% trans with {'%count%': 42}%}{0}I don't have apples|{1}I have one apple|]1,Inf[I have %count% apples{% endtrans %}
\n

Translation files

\n

Translation files must be named messages.<locale>.<extension> and stored in the translations directory.
\nSupported file extensions are defined by each translation format in layouts.translations.formats.

\n

The locale code (e.g.: fr_FR) of a language is defined in the languages entries of the configuration.

\n

Example:

\n
<mywebsite>\n└─ translations\n   ├─ messages.fr_FR.mo   <- Machine Object format\n   └─ messages.fr_FR.yaml <- Yaml format
\n\n\n\n

Date localization

\n

Uses the Twig format_date filter to localize a date in templates.

\n
{{ page.date|format_date('long') }}\n{# September 30, 2022 #}
\n

Supported values are: short, medium, long, and full.

\n", "language": "en" }, { "id": "https://cecil.app/documentation/templates/cache/", "url": "https://cecil.app/documentation/templates/cache/", "title": "Cache", "summary": "Templates cache and fragments cache.", "date_published": "2021-05-07T00:00:00+00:00", "date_modified": "2026-10-05T00:00:00+00:00","content_text": "Cache\nCecil uses a cache system to speed up the generation process, it can be disabled or cleared.\nThere are three cache types involved in template rendering: templates, assets, and translations.\nClear cache\nYou can clear the cache with the following commands:\nphp cecil.phar cache:clear # clear all caches\nphp cecil.phar cache:clear:assets # clear assets cache\nphp cecil.phar cache:clear:templates # clear templates cache\nphp cecil.phar cache:clear:translations # clear translations cache\nIn practice you don't need to clear the cache manually, Cecil does it for you when needed (e.g. when files change).\nFragments cache\nCecil provides a way to cache parts of templates rendering to avoid re-rendering the same partial content multiple times.\nTo use fragments cache, you must wrap the content you want to cache with the cache tag.\n{% cache 'unique-key' %}\n {# cacheable content #}\n{% endcache %}\nYou should use the cache_key function to be sure to have a unique cache key for each content you want to cache.\nFragments cache is persistent, so if the cache key is too generic, you may end up with wrong content displayed.\nTo clear fragments cache only, you can use the following command:\nphp cecil.phar cache:clear:templates --fragments\nDisable cache\nYou can disable cache with the configuration.\nDisabling cache can slow down the generation process, so it's not recommended.\nDuring local development, if you need to clear cache before each generation, you can use the following option:\nphp cecil.phar serve --clear-cache # clear all caches\nphp cecil.phar serve --clear-cache=<regex> # clear cache for cache key matches with the regular expression <regex>\nExample:\nphp cecil.phar serve --clear-cache=css # clear cache for all CSS files", "content_html": "

Cache

\n

Cecil uses a cache system to speed up the generation process, it can be disabled or cleared.

\n

There are three cache types involved in template rendering: templates, assets, and translations.

\n

Clear cache

\n

You can clear the cache with the following commands:

\n
php cecil.phar cache:clear               # clear all caches\nphp cecil.phar cache:clear:assets        # clear assets cache\nphp cecil.phar cache:clear:templates     # clear templates cache\nphp cecil.phar cache:clear:translations  # clear translations cache
\n\n

Fragments cache

\n

Cecil provides a way to cache parts of templates rendering to avoid re-rendering the same partial content multiple times.

\n

To use fragments cache, you must wrap the content you want to cache with the cache tag.

\n
{% cache 'unique-key' %}\n  {# cacheable content #}\n{% endcache %}
\n\n\n

To clear fragments cache only, you can use the following command:

\n
php cecil.phar cache:clear:templates --fragments
\n

Disable cache

\n

You can disable cache with the configuration.

\n", "language": "en" }, { "id": "https://cecil.app/documentation/templates/extend/", "url": "https://cecil.app/documentation/templates/extend/", "title": "Extend", "summary": "Add custom functions and filters, or use a theme.", "date_published": "2021-05-07T00:00:00+00:00", "date_modified": "2026-10-05T00:00:00+00:00","content_text": "Extend\nFunctions and filters\nYou can add custom functions and custom filters with a Twig extension.\nTheme\nIt’s easy to build a theme, you just have to create a folder <theme> with the following structure (like a website but without pages):\n<mywebsite>\n└─ themes\n └─ <theme>\n ├─ config.yml\n ├─ assets\n ├─ layouts\n ├─ static\n └─ translations", "content_html": "

Extend

\n

Functions and filters

\n

You can add custom functions and custom filters with a Twig extension.

\n

Theme

\n

It’s easy to build a theme, you just have to create a folder <theme> with the following structure (like a website but without pages):

\n
<mywebsite>\n└─ themes\n   └─ <theme>\n      ├─ config.yml\n      ├─ assets\n      ├─ layouts\n      ├─ static\n      └─ translations
", "language": "en" } ] }