## assign

## Description

Used to assign a value to a variable.

## Syntax

## Example

## block

## Description

Blocks are regions of content that you may want to override in children pages. Their names are used to define the tabs in the backend and segment editable regions.

## Syntax

🚧

Use only letters and underscores in your block name

Using dashes or other symbols will break functionality.

## Examples

Click file tabs to see how **nesting of blocks** works.

## Options

## capture

## Description

Combine a number of strings into a single string and save it to a variable.

## Syntax

## Example

## consume

## Description

Read an external datasource (either JSON or XML), cache the content and allow you to iterate over the objects.

## Syntax

## Example

## Caching

For the caching, the LocomotiveCMS engine uses the default [Rails caching](🔗).

📘



If you want to use the **Redis cache store**, please read [this blog article](🔗).

## Options

## csrf_meta

## Description

The csrf_meta tag gives the information the javascript code has to include for each AJAX POST request in order to prevent **Cross-Site Request Forgery** (CSRF) attacks.

By default, that protection is **disabled** in order to keep backwards compatibility with the existing public forms.

If you want to enable it, open your **config/initializers/locomotive.rb** file and toggle the csrf property on.

## Syntax

## Example

## csrf_param

## Description

Forms inside the Liquid templates, such as a contact form for instance, can be protected from **Cross-Site Request Forgery (CSRF)** attacks.

By default, that protection is **disabled** in order to keep backwards compatibility with the existing public forms.

If you want to enable it, open your **config/initializers/locomotive.rb** file and toggle the csrf property on.

📘



For AJAX requests, please consider the [csrf_meta tag](🔗).

## Syntax

## Example

## cycle

## Description

Output the next option in a group on each call.

## Syntax

## Examples

## editable_control

## Description

Editable areas contain content you want a user to be able to change. The content within the tag will be the default one.

In the back-office, the editable element will be found under the tab corresponding to the block wrapping it. It is possible to associate the element to another block.

The input field in the back-office used to edit the content is a select field.

An element can be inherited by children, each page keeping its own version of the content. However, in some cases, it may be a requirement to have the element to be editable in one place. If so, just set the "fixed" option to true.

## Syntax

## Example

## Options

## editable_file

## Description

Editable areas contain content you want a user to be able to change. The content within the tag will be the default one.

In the back-office, the editable element will be found under the tab corresponding to the block wrapping it. It is possible to associate the element to another block.

The input field in the back-office used to edit the content is a file field.

An element can be inherited by children, each page keeping its own version of the content. However, in some cases, it may be a requirement to have the element to be editable in one place. If so, just set the "fixed" option to true.

## Syntax

## Example

## Options

## How to use editable image with a default value?

If you want to use a theme image as the default value of your editable file, you might be tempted to do this:

**Which won't work**: editable tags can't include another Liquid tag.

So you need to pass the relative path of an image located in the **public/samples** directory of your Wagon site.

If you want to resize the image, the code should be as follows:

## editable_model

## Description

The editable_model tags are used to display a short link to the content entries they reference in the live editing sidebar as described in this example:

## Example

## Options

## editable_text

## Description

The editable_text tags are placeholders for content that you want users to be able to edit through the back-office. They replaced the now deprecated editable_short_text and editable_long_text tags.

Users can change the content of an editable_text tag by going to the pages section of the back office, selecting the page on which the tag appears, and then selecting the tab which corresponds to the name of the block wrapping the tag. Each editable_text tag is represented by a textarea labled with the editable_text's name. When no text has been entered into the back-office, the content within the tags is displayed by default.

If a block containing an editable_text tags is inherited by child pages, these child pages each store its own version of content and can be edited separately. For cases requring a single version of the content to be used on all pages and editable in only one location (such as text in the header or footer of a site), make use of the fixed option described below.

## Example

## Options

📘

Using editable_text inside a html tag needs a work-around

Use `{{ page.editable_elements.<your block path>.text }}` inside your html tags and define the `editable_text` outside in a `capture` tag.

Text



🚧

Using editable_text inside snippets

Although it may be tempting to use editable_text or any other editable elements within snippets, it is highly recommended to not doing it because it makes the content rendered by the engine not reliable. Make sure it is wrapped inside a block tag if you doing so.

## extends

## Description

🚧



The extends tag must ALWAYS be the first statement.

Set the layout of the current page. A page can be a layout for another page. The tag needs a single parameter which can take two values:

• **parent** the layout for the parent url

• **some/page/path** a specific pages layout

📘



You do not need to close this tag.

## Syntax

## Examples

## google_analytics

## Description

It is simply a helper tag which includes the snippet code that it is asked by Google Analytics to enable traffic analytics.

Just provide your Google account id.

📘



Put your google_analytics tag just before the closing HEAD tag.

## Syntax

## Example

## include

## Description

Include sections of content you would like to repeat across the website. The optional with clause lets you specify a value which is bound to the snippet's name within the snippet's context.

The snippets are declared in the app/views/snippets directory, the snippet slug is the filename.

## Syntax

## Examples

## link_to

## Description

Return a html anchor to a given page or a content entry if the content entry owns a templatized page. The page is identified by its handle.

## Syntax

## Example

## locale_switcher

## Description

Display the links to change the locale of the current page. The links are wrapped inside a DIV tag.

The link to the current locale owns the class current which makes it possible to customize through CSS.

📘



Nothing will be displayed if you do not select at least 2 locales for your site.

## Syntax

## Example

## Options

## model_form

## Description

Display the form html tag with the appropriate hidden fields in order to create a content entry from a public site. It handles callbacks, csrf and target url out of the box.

## Syntax

## Examples

## nav

## Description

Render a list of links pointing to your pages. You can specify a context from where the pages will be pulled out. The context takes the following values: site, parent or page.

Moreover, it is also possible to include the nested pages.

🚧



Your pages must fill 2 conditions to be part of the navigation: be published and be listed.

📘



The order is based on the one you specify in your LocomotiveCMS back-office.

## Syntax

## Examples

**[With a snippet]**

nav tag in the page

{{ page.menu_teaser }} {{ page.menu_image }}

snippet named "menu-entry"

## Options

## paginate

## Description

The paginate tag is responsible for pagination within the LocomotiveCMS engine. It is currently applicable to the entries of content types.

It can be combined with the **with_scope** tag.

## Syntax

## Example

## Properties of the paginate object

## path_to

## Description

Return the link to a given page or a content entry if the content entry owns a templatized page. The page is identified by its handle.

## Syntax

## Examples

## seo

## Description

Output the meta tags and associated content for keywords and description. Depending on the current page, the following fallback is applied:

• if the page is "templatized", check first for the keywords / description of the related content entry.

• if the keywords / description of the page are filled up, use them.

• finally, use those of the site if the previous objects failed to return non-blank keywords / description.

Alternatively, you can access the keywords and description directly from an object among those: site, page, content_entry.

## Syntax

## Example

## session_assign

## Description

Used to store in the session a key and its value.

## Syntax

## Examples

## with_scope

## Description

The with_scope tag is used to filter a list of entries. The filter is applied directly to the MongoDB request which makes it very performant.

## Syntax

## Examples