For developers

Build a theme for Abizvo Sites

Themes are written in Liquid, the template language Shopify themes use, and rendered by Fluid on Abizvo's servers. If you have built a Shopify Online Store 2.0 theme, the package, the JSON templates, the {% schema %} blocks and the settings schema will look familiar. What differs is what a theme may reach: only dictionaries, lists and primitives reach Liquid, every output is HTML-encoded, each section renders in isolation so a failing one leaves the page standing, and the platform writes the head, the colour-scheme classes, the fonts and the "Powered by Abizvo" line.

Documentation

The developer documentation, page by page

Every page is written from the code that enforces it, and a test holds the two together: the setting types, the filters, the check's refusals and the marketplace's limits on these pages are the ones the platform runs.

Settings

Forty-two setting types, one gate

ThemeSettingTypes is the one place a stored value is checked: a value is normalized there or refused there, at save and again at publish, and the renderer trusts nothing else. Nothing a setting holds is HTML — richtext is the platform's own markup (blank lines, ## , - ), and a default written as HTML renders its tags as words.

text · textarea · inline_richtext · richtext · date · number · range · checkbox · toggle · select · radio · button_group · color · color_scheme · color_scheme_group · color_background · image_picker · video · video_url · url · page · gallery · product · collection · form · link_list · icon · font_picker · text_alignment · spacing · border · radius · shadow · animation · effect · header · paragraph

• A setting's CSS custom property is its id with _ → -: min_height is --min-height, and a scheme colour button_text is --color-button-text. A theme reading the underscore form gets nothing.
• size, first, last, keys, values and empty are reserved as setting ids: Liquid answers them from the settings dictionary itself, so {{ settings.size }} is the number of settings, not your setting.
• Textual settings may be connected to a dynamic source — the business's own name, phone, address — instead of a typed value.
• A form setting is one of the platform's forms: contact, newsletter, lead, quote, booking. The post goes to the site itself and creates a lead.
• An effect setting picks from the platform's own library — 3D tilt, magnetic, spotlight, lift, image zoom, zoom on scroll, count up, stacking cards, marquee, living gradient, word by word, at subtle, medium or bold — written as {{ section.settings.effect | effect_attributes }}, never as an inline style. The runtime reaches only a page that uses one, and everything that moves sits under prefers-reduced-motion: no-preference.

The theme check

What the check reads, and what it refuses

ThemeChecker runs on import, on every save in the workspace, at release and again in the marketplace review. A theme with any error cannot be installed; a warning is reported and lets it through.

JavaScript is read as a syntax tree

ThemeJsAnalyzer parses each script (at most 400 KB) and refuses, as an error: eval, Function and importScripts; a dynamic import() or an import from another site; a worker; a <script> element built from text or created at runtime; with; document.cookie; navigator.sendBeacon; the credential store; document.write; a timer given a string; and a redirect or form action worked out at runtime. Network calls, storage and HTML sinks (innerHTML and its siblings) are flagged as warnings. Official themes ship no JavaScript at all except Starter; on a site, a theme's script runs only on the site's own origin, never on the platform's path.

Versions

Versioning, updates and the workspace