Theme structure and the theme editor

You edit a theme’s code in the theme editor: Content → Theme, then Theme editor (/admin/themes/12587565). The editor shows the theme’s files in three groups and opens the one you pick in a code editor with Liquid highlighting.

• Directorytemplates/ one file per kind of page

  • Directoryaccount/

    • change_password.liquid
    • dashboard.liquid
    • edit.liquid
    • login.liquid
    • register.liquid
    • register_success.liquid
    • reset_password.liquid
  • Directoryblog/

    • article.liquid
    • category.liquid
    • index.liquid
  • Directorycheckout/

    • order-confirmation.liquid
  • Directorylistings/

    • category.liquid
    • dashboard.liquid
    • form.liquid
    • form_success.liquid
    • listing.liquid
    • search.liquid
    • store.liquid
  • Directoryorders/

    • purchases.liquid
    • sales.liquid
    • vendor_details.liquid
  • contact.liquid
  • index.liquid
  • maintenance.liquid
  • page.liquid
  • page.landing.liquid an alternate page template you created
• Directorysnippets/ pieces of markup included by templates

  • footer.liquid
  • header.liquid
  • homepage-articles.liquid
  • homepage-categories.liquid
  • homepage-edito.liquid
  • homepage-listings.liquid
  • homepage-welcome.liquid
  • listing-thumbnail.liquid
  • menu-categories.liquid
  • menu-default.liquid
  • order-item.liquid
  • order-item-email.liquid
  • purchase-status-flow.liquid
  • sale-status-flow.liquid
  • user-attributes.liquid
  • user-thumbnail.liquid
  • … the snippets you create
• Directoryassets/ the CSS and JavaScript files you create

  • …

• Templates render the content of a page: the homepage, a listing, the search results, the account pages. The platform wraps every template in the page’s <head>, the header and the footer. Templates lists what each one renders and the variables it receives.
• Snippets are reusable pieces included with {% include %}. Some are also rendered by the platform on its own: the header and footer on every page, the listing card in every listing grid, the order item in emails.
• Assets are the CSS and JavaScript files you create. See Assets.

The editor also lists the snippets and assets of a theme installed from the theme library, so you can override them in the same way.

How your changes apply

The theme’s files are the starting point. When you save a file in the editor, the storefront uses your version instead of the theme’s from then on:

1. your version of the file, if you saved one;
2. otherwise the file of the theme installed from the library, if the marketplace uses one;
3. otherwise the file of the base theme, Kindshare.

Saving is immediate: the next page view uses the new file. There is no draft and no version history in the editor, so keep a copy of a file before a large change.

Your copies do not follow theme updates

A file you saved no longer changes when Kreezalid improves the theme’s version of it. Override the few files you need rather than every file, and prefer Custom CSS for visual changes: it survives theme updates untouched.

When the marketplace switches to a theme from the library, the copies you made over the previous theme are set aside, not deleted: they come back if that theme is switched off. Copies you make while the library theme is active belong to it.

Add a file

A snippet

1. Next to Snippets, click Add a new snippet and type a name, for example promo-banner.
2. Write the snippet and save.
3. Include it from a template or another snippet: {% include 'promo-banner' %}.

Do not create a snippet with a theme snippet's name

A new snippet starts empty. Creating one whose name the theme already uses (Kindshare ships more snippets than the editor lists, such as homepage-faq or listings-map) replaces the theme’s snippet with an empty file, and that part of the page disappears. Pick names of your own, with a prefix such as acme-.

An alternate page template

CMS pages (Content → Pages) render with page.liquid. You can give some of them another layout:

1. Next to Templates, click Add a new template, keep page and type a name, for example landing. The editor creates page.landing.liquid as a copy of page.liquid.
2. Edit and save it.
3. In Content → Pages, open a page and choose landing under Template.

Only pages accept alternate templates. Every other template exists once.

An asset

Next to Assets, click Add a new asset, type a name and choose css or js. See Assets to load it.

Remove a file

A snippet or an asset you created or saved can be removed with Delete this file. If the theme has its own version of the file, that version is used again; otherwise the file is gone. A snippet that one of your files still includes cannot be deleted: the editor names the files to fix first. Templates cannot be deleted, since a page needs one.

What the editor does not cover

• The page’s <head>, the admin bar and the cookie banner are managed by the platform. Add tags to <head> or right after <body> with Custom Tags in Settings → General.
• Some pages are not Liquid templates and only take CSS from you: the cart, the checkout steps, the buyer’s order page, the inbox, the wishlist.
• On some marketplaces saving in the theme editor is turned off. The editor then says so under the code; contact Kreezalid support to request a change.
• There is no API to read or write theme files, and no way to upload a theme as a file: themes in the library are published by Kreezalid.