Noted — Content & Setup Guide

What's already been done

So you have the full picture before you start:

• 7 "Shop by Scent" + 4 "Shop by Occasion" collections were created as smart collections that reuse the existing Scent and Occasion product metafields. Nothing was flattened or re-tagged — so there's no metafield/filter content entry to do.
• The filters are unchanged. They still run off the Search & Discovery app exactly like the live store — same Scent / Occasion / Category / Gender facets.
• The mega-menu is wired to these collections (Discover group + inside each of Women's / Men's / Unisex).
• Gender is handled by filtering, not duplication. Opening e.g. Women's → Warm & Spicy shows the one shared "Warm & Spicy" collection auto-filtered to "For Her" — so we avoid creating hundreds of women's/men's/unisex variants.
• All collections are live and published, with a placeholder nav thumbnail on each (that's what you're replacing).

The mapping — which metafields feed each collection

Each is a smart collection using "any condition" (OR): a product joins if its Scent/Occasion metafield contains any listed value. This is the decision made — yours to change if you'd group differently.

Deliberately dropped (non-scent descriptors): Luxury · Modern · Classic · Feminine · Strong. The four seasons (Spring/Summer/Autumn/Winter) are kept out of Occasion — handled by the seasonal shops.

What you need to do

For each of the 11 new collections (7 Scent + 4 Occasion), set the following in Admin → Products → Collections. Click a collection name in the table to open it directly.

1. Navigation thumbnail — the launch priority. This is the image shown in the mega-menu and on the featured-collection tiles. Every collection currently has the same placeholder — replace each with a suitable image (Collection → Metafields → Navigation thumbnail). Remove it if you'd rather show no thumbnail.
2. Short description (optional) — shows on the collection page and is truncated. Aim for ~165 characters (≈20–25 words, one or two short sentences) — that's where the band truncates. Collection → Metafields → Short Description.
3. Long description (optional, SEO) — the main collection description body. Pulled for SEO even when not shown on the page. Ideally add both a short and a long.
4. Featured image (optional) — set a collection Image to override the thumbnail on the collection/featured display with a different shot.

Image sizes & recommendations

Pulled from how the theme actually renders these — follow them so nothing looks soft or mis-cropped.

Format: JPG or WebP, keep each under ~400 KB. The nav thumbnail is the launch priority; the featured image is optional polish.

How it's structured

• Parent → child → grandchild. The top-level items (Women's, Men's, Unisex, Bundles, Gifts, Body & Home) are parents; the links inside them are children; and the Shop by Scent / Shop by Occasion families are grandchildren.
• "Shop by Gender" groups itself. Women's / Men's / Unisex are flagged as Gender collections, so the menu groups them automatically under a "Shop by Gender" heading. Set once — you never need to touch it.
• Three menus feed it: the Main menu, the Discover menu (Father's Day, Shop by Scent, Shop by Occasion, Articles), and an optional Top-nav override (the flat desktop strip of direct links).

Panel hero image + promo cards

Each Level-2 panel can show a hero image and up to 4 promo cards, added as "panel" blocks in the Header section. A block's link title must match its parent menu title exactly (e.g. Women's, Men's, Shop by Scent) — that's how it attaches to the right panel. To add another, duplicate an existing panel block and rename the title. Women's is set up as the example.

Format: JPG or WebP, under ~400 KB each.

What's already been done

• Top / Middle / Base notes — done, no entry needed. A script copied the note lines out of each description into three new metafields (Top · Middle · Base Notes) across 119 perfumes, so those rows already match.
• Copied, not moved. The lines still sit in each description too — deliberately, so the old/live theme is unaffected. Clearing them is an optional tidy-up (below).
• Main Notes is new — the 2-up grid of ingredient photos at the top of the accordion (e.g. Monte Carlo: Saffron · Amberwood · Cedar · Cinnamon), powered by a reusable Ingredient library + a per-product Main notes picker (below).
• 4 ingredients exist so far (Amberwood, Cinnamon, Saffron, Cedar) and Monte Carlo is the demo. Every other product's Main Notes is empty on purpose — which notes are "main" is your call.

How the library + picker fit together

Don't be put off by "metaobject" — it's just a content library. An Ingredient is a reusable tile (name + one photo) you create once in Content → Metaobjects → Ingredient and reuse everywhere. On each product, the Main notes field is where you tick which to show. The grid renders only the ones you pick that have a photo, in your chosen order, no limit — no photo means it never appears, nothing picked hides the grid.

What you need to do

1. Build the ingredient library first — the launch priority. In Content → Metaobjects → Ingredient → Add entry, add one entry (name + photo) per ingredient, most-used first (Musk, Vanilla, Bergamot, Jasmine, Amber… cover the bulk; full order in the content plan). Global — set once, reuse everywhere.
2. Then pick Main notes per product. On a product, select the relevant tiles in the Main notes field — they render image-only, in order, no cap. Empty = no grid. (The front end can take a minute to update after saving.)
3. (Optional, no rush) Clear the Top / Middle / Base lines from descriptions — they're duplicated in metafields now. Tidy at launch via bulk edit / CSV / Matrixify; harmless if left (the page just repeats the new UI). Don't clear them before launch — the old/live theme still reads the description.

Ingredient photo size

How the Main-Notes tiles actually render — follow it so nothing looks soft or mis-cropped.

JPG or WebP, under ~300 KB each. The ingredient library is the launch priority; the descriptions tidy-up is optional polish.

What's already been done

• The sub-collections row is built — it sits directly under the collection description in the collection hero, as a slim row of text links (with a slider / prev-next arrows if there are more than fit on one line).
• It's driven by one content library — a "Collection group" metaobject. Each entry is just a name plus a list of collections that belong together.
• One group is seeded as the example — "Bundles". Land on any Bundles collection and you'll see the others in the group as links.
• It groups itself automatically. A collection only needs to be added to a group once; the links then show on every collection in that group, each one listing the others (the collection you're on is never listed against itself).
• Nothing shows if a collection is in no group — so collections you don't group simply have no sub-collection row. (A grouped collection that isn't published to the Online Store is also skipped.)

What you need to do

Decide which collections should link to each other, then group them in Content → Metaobjects → Collection group.

1. Add a Collection group entry. Open Collection group → Add entry and select all the collections that belong to one family (e.g. every "Gifts" collection).
2. Give it a title. The title is for your reference only — it's not shown on the storefront — so name it whatever helps you find it ("Bundles", "Gifts", "By size"…).
3. Add as many collections as you like — and as many groups as you like. Repeat for each family you want cross-linked. Save, and the links appear on every collection in the group.

No images or descriptions to set here — it's purely which collections are grouped. Only group collections that are published to the Online Store, or they'll be skipped in the row.