Jessar · Homepage · integration plan v1

Bringing v3 onto the live theme

A step-by-step, non-destructive plan to rebuild the approved homepage_v3 as real Hyper-native sections on the live theme (190048960834), elevated with our scoped CSS — leaving the existing homepage intact for comparison. Built on the same render-before-build, native-first, pull-live-first discipline we used on the collection page. For your approval before I touch the theme.

The three guarantees

Non-destructive — the 9 existing rs- homepage sections are disabled (hidden), never deleted. The new native sections are added alongside, so you toggle/compare in the editor. Cleanup pass later, on your word.

Reversible — a git tag + an index.json backup before any change; re-enabling the old sections is an instant rollback.

Safe to your edits — every file is pulled live first, pushed --only scoped, schema-first, so nothing you've changed in the editor gets clobbered.

AWhat gets built — section map

Every v3 section maps to a real Hyper section (verified against each section's schema). "Where" = editor you can edit it in the theme editor · code needs CSS/Liquid · both native config + our CSS craft.

#v3 sectionHyper nativeKey configSchemeCSS craftWhere
1Heroimage-with-text-overlayimage + heading + subheading + 2 button blocks; content bottom-left18 (cream)gradient scrim + oversized typeboth
2Browse by categorycollection-list4 collection blocks + images; "By category"3 / white— (proven on collection page)editor
3House brandsmulticolumn + buttons-with-icon4 column blocks (image+name+count) · lines = buttonswarmsub-brand dotsboth
4Kitchen, in depthimage-with-featuremain image + heading + 4 image feature-columns (the real product tiles)whitetile + CTA polishboth
5Made for the morningimage-with-textimage-right + text + button blockswarmeditor
6Lighting (full-bleed)image-with-text-overlayfull-bleed image + heading/text/button + content left18 (cream)left scrim, full-bleed heightboth
7Home & Bathimage-with-textimage-left + text + buttonwhiteeditor
8Cast iron, Sundayimage-with-text-overlayfull-bleed + heading/text/button1 (light)light cream scrim, dark textboth
9Inside Jessar (film)image-with-text → videostill + copy + quote now; swap to embedded film when the cut landswhiteimage-bleed + play buttonboth
10In focus this seasoncollection-cards / multicolumn3 image tiles + captionswarmcaption polisheditor
11Presspresslogo blocks + quote (quote via heading/rich-text)whiteeditor
12Retail partnersbrand-logoslogo blocks (Costco / Staples / Linen Chest)warmeditor
13Dual-audience doorsimage-cards2 image_card blocks + 2 buttons18 (cream)reuses the scrim we already shippedboth
14Heritage closerich-textcentered statementbaseeditor
15Footer (dark)footerset footer colour scheme → dark (scheme-inverse)inverseeditor

Native coverage 15/15   No custom sections required. The CSS craft is the same toolkit already live on the collection page + dealer card (schemes, gradient scrims, the eyebrow system).

BPre-flight & foundation

  1. Snapshot & tag. git tag pre-homepage-v3 + back up the live templates/index.json to a revert file. This is the rollback anchor.
  2. Pull live the files I'll touch (index.json, settings_data.json, rs-soft-modern.css, layout/theme.liquid) so I'm editing the current truth, not stale git.
  3. Upload imagery to Shopify Files (~18 images → shop_images, prefixed rs-home-*) via the Admin API, so every image is swappable by you/Michael in the editor later — not hard-baked. Hero · 4 category · 4 brand · kitchen + 4 product tiles · morning · lighting · home · cast-iron · warehouse · seasonal ×3 · door.
  4. Colour schemes — no new scheme needed. scheme-18 (the warm-dark overlay scheme we already shipped) covers hero / lighting / doors; scheme-1 covers the light cast-iron overlay; scheme-inverse covers the dark footer. All already live.
  5. Homepage CSS — add a scoped rs-home.css (loaded only on the index template) holding the craft: hero gradient scrim + type scale, sub-brand dots, kitchen product-tile row, the full-bleed overlay scrims (cream + light variants), the film image-bleed + play button. Scoped to the homepage sections so no other page is affected. Register it via a conditional include in theme.liquid.

CBuild & push order (schema-first, scoped)

  1. Push the CSS + include first: --only assets/rs-home.css layout/theme.liquid --allow-live. Nothing references it yet, so it's inert until the sections exist — zero visible risk.
  2. Assemble the new index.json off the pulled-live copy: (a) set the 9 rs- sections to "disabled": true; (b) add the 14 new native sections with their settings — image refs (shopify://shop_images/…), copy, schemes, buttons, blocks — in the v3 order; (c) leave the order array so old (disabled) + new (enabled) coexist.
  3. Push index.json --only templates/index.json --allow-live --nodelete, immediately after a fresh pull (to avoid racing your editor).
  4. Footer → dark: set the footer section's colour scheme to scheme-inverse (footer lives in the footer group / settings) and push that file only.
  5. Re-pull & verify each pushed file round-tripped (the same confirm step we used for scheme-18 + the scrim).

Why this order: CSS is inert until sections use it; the index.json is the single visible switch; each push is one scoped file, pulled-live-first. If anything looks off, re-enabling the rs- sections + disabling the new ones restores the current homepage instantly.

DValidation (before I call it done)

EOpen dependencies & the 2 decisions I need

Client-gated (sections ship with a tasteful placeholder until these land)

Two build choices I'll lock with you

FSequencing — how I'll run it once you approve

PhaseWhatResult you see
1 · FoundationTag + backup · upload images to Files · push rs-home.cssnothing changes yet (inert)
2 · The easy winscollection-list · 3× image-with-text · multicolumn+buttons · brand-logos · rich-text · seasonalmost of the page, live in the editor
3 · The craft sectionshero overlay+scrim · lighting + cast-iron full-bleeds · kitchen feature tiles · film · doorsthe signature moments
4 · Finishfooter → dark · full validation · mobile passcomplete homepage, old one hidden behind it

I'll check in at the end of Phase 2 and Phase 3 with editor screenshots so you're never surprised — and the old homepage is one toggle away the entire time.

Approve to proceed

Sign off on the plan (and the two decisions in §E), confirm the link targets, and I'll start at Phase 1. Nothing touches the live homepage's visible state until the index.json push in Phase 2 — and that's fully reversible.