Documentation Abizvo Sites themes
Build a theme for Abizvo Sites
Themes are written in Liquid and rendered by Fluid on Abizvo's servers. These pages say what a theme may contain, what a template can read and call, what the theme check refuses, and the bar a theme sold on the Abizvo Marketplace meets. Every list here — the setting types, the filters, the check's refusals, the marketplace's limits — is read from the code that enforces it, and a test holds the two together.
For a look to start from, use design.abizvo.com, Abizvo's design reference library; Design reference says how a direction maps onto a theme's settings.
Getting started
What an Abizvo Sites theme is, the two ways to start one, and the check → release → install → publish loop every theme goes through.
Package layout
The manifest, the ten folders a theme may contain, the path rules and size caps, the config files, templates, section groups, locales and assets.
Liquid
The Liquid dialect Abizvo themes are written in — the platform's tags, its eighteen filters, the objects and globals a template reads, what is encoded, and two traps.
Sections and blocks
The {% schema %} of a section or theme block — settings, accepted blocks, presets, placement, visible_if, dynamic sources, reusable sections and the limits.
Settings
Every setting type a theme may declare, the shape each stores and the value Liquid reads, the validation, CSS custom property naming, colour schemes, fonts, animation and effect settings.
Templates and pages
Layouts, page templates and alternate templates, the 404, galleries and albums, collections and entry pages, page.{slug}, the head the platform writes, and what sits outside the theme.
Assets, motion and effects
asset_url and content-versioned assets, the stylesheet and script bundles, the motion runtime and its clip-reveal rule, the effects library, the behaviour runtime's data-ab attributes, and the performance budget.
The theme check
Every pass of the theme check, what each refuses as an error and flags as a warning — manifest, structure, Liquid, schemas, data, assets, CSS tokens, JavaScript syntax tree, SVG, locales, budget, accessibility — and how to read the findings.
Design reference
How to use design.abizvo.com — the library of 134 styles, the presets, discover, the mixer and the exports — as the starting point for a theme's look, and how a design direction maps onto colour schemes, type and spacing settings.
Premium theme standards
The bar a paid theme on the Abizvo Marketplace meets — the check, every look on every template in both languages, accessibility and contrast, the budget, honest sample content, documentation and support, listing media, versioning, pricing and the price lock, the licence and the review.
Submitting to the marketplace
From a released theme to a listing on the Abizvo Marketplace — the seller account, the product, the listing, packaging the ZIP, the submission checklist, the review, publication and updates.
Site apps
Blocks a theme section accepts and embeds placed on every page — the app package, its manifest and permissions, how a block and an embed are written, the app check, the developer workspace, installing on a site, and selling on the marketplace.