Start Here — Production Handoff

If you’re picking this theme up to do production work, read this page first. It’s the honest status of the build — what’s solid, what’s thin, and where a day is best spent.

Read this before you start building

This theme was built under heavy schedule pressure. The code is in good shape; the documentation is catching up to it. Some sections you’ll see in the customizer don’t have a page here yet. A missing page means it wasn’t written — not that the feature is broken or unfinished.

If a section isn’t documented and isn’t obvious, ask rather than guessing. The schema is the source of truth, and some sections have behaviour (bleed, gradient chaining, block nesting) that isn’t discoverable from the settings alone.

The one thing that will trip you up

Sections here are block-driven. Most of them expose very little in the section settings — the heading, the body copy and the buttons are all separate blocks nested inside. If you open a section and it looks empty, you’re probably looking at the section settings when the content lives in the blocks below.

The Comparison Table is the extreme case: the whole grid is assembled from nested blocks. Read its page before you touch it.

What’s built and safe to work in

These templates are fully assembled and are the best reference for how sections are meant to be combined:

Template	State	Use it as
index (Homepage)	Richly built	The reference for section stacking and gradient chaining
product	Richly built	The reference for the PDP block system
page.about-us	Richly built	The reference for editorial page composition
page.style-guide	Internal scratchpad	A live catalogue of type, colour and components — look, don’t build
collection	Built	Collection layout
page.ingredients	Thin	Needs building out
page.professionals	Thin	Needs building out

Look at the Style Guide page first

page.style-guide renders the type scale, the full colour palette and the button system on one page, reading live from the theme tokens. Ten minutes there will tell you more about what this theme looks like than any amount of reading.

It is an internal scratchpad, not a production page — it’s marked for deletion before launch. Use it as a reference; don’t build client content on it, and don’t treat it as an example of how to assemble a real page. For that, use the Homepage, Product and About Us templates.

Where a production day is best spent

Ordered by value, and by how safe each is to do without needing decisions from anyone:

1. Build out page.ingredients and page.professionals. Both are thin and both have documented sections available. Lowest risk, clearest value.
2. Populate real content into the homepage sections. The structure is there; much of the copy and imagery is still placeholder.
3. Collection pages. collection-grid is the only section there now, by design — filtering was deliberately removed because the catalogue is small.
4. The PDP. Powerful but the most interconnected part of the theme. Read the Product page docs before changing block order.

Read the known issues before you debug anything

Several settings in this theme don’t do what their label says, and a couple of defaults look broken when they’re just unset. All of it is written up in Known Issues & Gotchas — verified against the code, not guessed.

Worth knowing before you start, because each one reads as “I did something wrong” when you hit it:

• Marquee Image has three settings that do nothing at all.
• Customer Ratings stars default to near-black and vanish on dark backgrounds.
• Comparison Table binds cells to columns by position — add a column late and every row silently shifts.
• Featured Collections’ carousel is disabled at desktop widths, so it looks like the checkbox is broken.
• “Show reviews preview” points at an unimplemented stub. It no longer breaks anything, but it does nothing — leave it off.

Things that are deliberate, not bugs

Worth knowing so you don’t “fix” them:

• Collection filtering doesn’t exist. It was built and then removed on purpose — the catalogue is small enough that filtering added no value. Collection pages render the grid alone.
• Subscriptions use native Shopify selling plans, created by Skio. There is no Skio widget block on the product page. If you’re looking for one, that’s why you can’t find it.
• Some sections have zero bottom padding by default. Sections like Teaser are designed so the image is cropped by the section edge. Adding padding breaks the effect rather than fixing it.
• A brand-new section can show mobile padding at every screen width until the CSS is rebuilt. That’s a stale build, not a broken section.

Conventions you must not break

These are enforced in the repo and will fail a push or a review:

• Colours come from the brand palette only. Never an arbitrary hex. See Colours.
• Padding uses the shared six-setting pattern — mobile, tablet and desktop, top and bottom. See Spacing and Layout.
• Any new schema setting needs a translation in locales/en.default.schema.json — block translations in the blocks key, section translations in sections. Mixing them up causes errors.
• Docs ship in the same commit as the change. If a merchant would notice it, it gets documented. See Keeping Docs Current.

If you get stuck

The schema in the .liquid file is always the source of truth — it’s what the customizer actually renders. If a page here disagrees with the schema, the schema wins and the page needs fixing.