Building themes
Build a complete Salieno Core storefront theme, step by step — layouts, sections, pages, assets, and publishing to the marketplace.
The mental model for Salieno Core themes: Core ships themeless, a theme owns every public page, and the resolution engine ties them together.
Go from an empty folder to a rendering Salieno Core theme using the scaffolder or the three required files by hand.
The complete theme directory layout plus theme.json and salieno.json field by field, and which files Core and the marketplace actually require.
The two-layer layout chain: the base HTML shell, the header/footer chrome, and the Livewire slot short-circuit that makes both page types work.
Ship precompiled CSS, JS, fonts, and images under assets/, reference them with themeAsset(), and stay inside the docroot security allowlist.
The full section system: sections.json definitions, the render pipeline, admin-editable content, repeatable elements, and a complete worked example.
Every public page a Salieno theme must ship, the controller that renders each one, and the data it hands your Blade view.
Build the eight Livewire-backed auth views a theme must ship, and preserve every wire:model, wire:submit and @error binding while restyling freely.
How the x-theme.* component library works, the fixed overridable set, and how to ship your own copy of one so it wins.
Every helper and Blade directive a Salieno theme uses — signatures, return values, and copy-pasteable examples.
How theme.json colours flow to var(--primary), writing light and dark palettes, and booting the mode switcher without a flash.
A pre-publish routine for verifying a complete Salieno theme: local install, a full surface checklist, light/dark, mobile, forms, and common traps.
How to publish a Salieno theme on the marketplace and ship updates that verify by signature and never lose operator customisation.
The concrete rules that make a Salieno theme read as premium and deliberate rather than generated — colour, type, elevation, accessibility, and parity.