Skip to main content
Eaglecart themes use a Liquid-based template language to render your storefront. Developers can create fully custom themes from scratch or extend existing ones by editing templates, sections, and snippets directly in the admin code editor or locally with the Theme CLI. Every visual layer of your storefront — product pages, collections, the cart, checkout fragments — is controlled by theme files you own and can modify freely.
The theme code editor is accessible at Online Store → Themes → [your theme] → Edit code. Changes saved here take effect immediately on the live theme, so always work on a duplicate unless you intend to publish right away.

Theme Structure

A theme is a directory of Liquid templates, assets, configuration files, and locale strings. The layout below shows every top-level folder and its purpose:

/templates/

Page templates determine what renders when a visitor navigates to a specific route. Each file corresponds to a URL pattern — product.liquid renders at /products/:handle, collection.liquid at /collections/:handle, and so on.

/sections/

Sections are reusable content blocks that merchants can add, remove, and reorder in the Theme Editor without writing code. Each section file contains Liquid markup and an optional {% schema %} block that defines its configurable settings.

/snippets/

Snippets are small, focused Liquid partials. Include them anywhere in a template or section using {% render 'snippet-name' %}. Unlike sections, snippets have no schema block and are not merchant-configurable.

/assets/

Place all CSS, JavaScript, image, and font files here. Eaglecart serves them from a CDN-backed URL. Reference any asset in Liquid using the asset_url filter (see the Customization guide).

/config/

settings_schema.json defines the settings that appear in the Theme Editor. settings_data.json stores the merchant’s saved values. Commit settings_schema.json to version control; treat settings_data.json as environment-specific data.

/locales/

Each file contains a nested JSON object of translation keys for a specific locale. The en.json file is the default fallback. Add a new locale file (e.g. de.json) and Eaglecart automatically offers it when the storefront language is set to German.

Theme Objects

Eaglecart exposes a set of Liquid objects in every template context. Use these objects to access store data and render it dynamically.

Examples

Accessing objects in Liquid

Next Steps

Theme Customization

Learn how to define theme settings, build custom sections, use the asset pipeline, and add translations to your Eaglecart theme.

Webhook Overview

Connect your storefront to external services by sending real-time event notifications with Eaglecart webhooks.