Camel Join waitlist

Sections and templates

Stores are composed, not generated. The library is around fifty components with more than 170 templates between them, every one mobile-safe and every one dressed by all eight design styles.

The vocabulary

Three levels, from the merchant's point of view:

So a store is a list of components, each with a chosen template, all rendered under one design style.

What the library covers

Offers are not sections. Deals, bundles, gifts and cross-sells are added in the Camel app after publishing and drawn inside the buy box and the cart drawer (see Bundles, upsells and cross-sells). Policy pages and any other extra pages are created in Shopify, after publishing.

Why templates rather than free-form generation

A layout generated from scratch is unpredictable on a phone, inconsistent across pages and hard to edit. A template is tested, mobile-safe and editable, and it carries a part contract that every design style honours. Camel's job is to choose well — which components, which templates, in what order, populated with what — and that is where the product data and what Camel knows about the buyer go.

Mobile

Templates are built mobile-first. Card rows that would stack awkwardly on a phone are being given a rail instead: the Review Wall's grid already collapses into one, in one of three authored modes (a still mosaic, a one-card pager, or a slow drift), and the merchant picks the mode in the Template tab.

Motion

Sections reveal on scroll through one shared system, with a tempo set by the design style. A section that wants more (a word-by-word heading, a child cascade, a hero settle) declares it once, and the published theme carries the same motion.