Introduction to Marketpath Liquid: a templating language for CMS templates and where to find reference documentation.
Marketpath CMS templates are written in Marketpath Liquid, based on Shopify's Liquid and significantly extended for Marketpath CMS. Treat this documentation as the source of truth for syntax, objects, methods, filters, and conditions — generic Liquid references from other platforms will not match Marketpath's dialect.
Custom field definitions - the Types, Conditions, and Validators you declare on templates, datastores, site settings, and forms - are catalogued separately under Custom Fields.
Getting Started
Where to create templates, what to add first, and how to see the result.
Templates in Marketpath CMS are written using the Marketpath Liquid templating language and used in several places: page templates (which define the layout and content of pages), form and gallery templates (which define how forms and galleries are rendered), and partial templates (reusable pieces of template code).
A minimal first template is to output something that is always available. For example, you can output the current request path using {{ request.path }}, or a property of the entity such as {{ entity.title }}. Use output markup (double curly braces) to display a value: {{ object.property }}.
To preview or test your template, use the normal workflow for your site: save the template and load a page that uses it in the browser. You should immediately be able to view the updated output on the preview site, or you can publish your template and any related assets in order to view the output on the live site.