Building Sites Applied Liquid guidance for composing templates, personalization, permissions, and maintainable site patterns.
Once you know Liquid syntax, the next step is using it effectively when building and editing Marketpath CMS templates: includes and snippets, safe output, page and request context, personalization and permissions, and maintainable patterns.
Using Includes and Snippets Includes are developer-owned partial templates; snippets are editor-friendly HTML objects with no URL.
Template Best Practices Register assets and images the documented way — a functional requirement, not just style — plus habits for readability, variable scope, and maintainability.
Where Custom Fields Belong The template that reads a FieldID should define it; including a partial composes its fields onto the page’s editing form.
Choosing a Content Architecture Decide whether a page section reads static custom fields or queries dynamic content, and when to mix both with input-variable partials.
Safe Output and Handling Missing Data Encode for the destination (HTML text, attributes, URLs, JSON) and guard optional data with is_valid or default.
Common Template Patterns Short recipes for conditional layout, entity-driven pages, lists, pagination, and structured field content.
Working with Lists The list type: range markup, looping, size, and how strings differ from real collections.
Page Reserved root-scope inputs on every page load, and how they relate to entity-driven templates.
Working with the Request How to read query parameters and POST data and branch template logic on the request.
Personalization How personalization (client, session, profile, cookies) works and how it is governed by permissions.
Permissions The Liquid-accessible permissions system that drives personalization and how to use it in templates.
Package Development Standards and guidelines for building Marketpath CMS packages that install cleanly, work together, and stay maintainable.