Description

A focused course, tailored for you

The Storefront Designer's Conversion-Review Playbook

Turn a theme review from a taste argument into a conversion-evidence decision the merchant signs off in one pass.

Theme review threads collapse into taste arguments because no one named the conversion evidence, the accessibility regression, or the theme-token mismatch before the merchant brand lead and the partner started relitigating the look.

$199 one-time

Tailored to your situation. Access within 24 hours. 30-day money-back.

Includes a hand-built implementation playbook delivered alongside course access, generated for your specific situation.

Why this course

A storefront designer running theme reviews lives in three artefacts at once. The Figma file the merchant signed off two sprints ago. The Liquid templates a partner agency just submitted. The Section 2.0 schema that decides whether a merchant editor can move a block without breaking the page on a 360 px viewport. When a review arrives Friday afternoon with a CRO note pulling one way and a brand-lead comment pulling the other, the design call is rarely about taste. It is about which conversion-evidence trail the reviewer cited, whether the theme-token map between Figma and Liquid still holds, and whether the partner's PR introduced an a11y regression no one caught in QA. Reviewers who name those three things in the first reply close the thread in one pass. Reviewers who lead with a screenshot and a preference comment trigger a week of back-and-forth and a merchant who churns to a different theme. The playbook is the structure that puts the three things in the first reply, every time.

What you walk away with

Close a theme-review thread in one reply by naming the conversion evidence, the a11y regression, and the theme-token mismatch up front.
Run a Section 2.0 schema audit on a partner-submitted theme PR in under thirty minutes with a written verdict.
Build the theme-token map between Figma and Liquid that survives a redesign sprint without drifting.
Draft a partner handoff memo that makes the merchant brand lead the deciding voice on contested sections.
Convert a CRO note and a brand comment into a single ranked decision the merchant signs off on without escalation.

The 12 modules

Module 1. The first-reply structure that closes a review thread in one pass

Reviews collapse when the reviewer leads with a preference and a screenshot. They close in one pass when the first reply names three artefacts the merchant and the partner both have to accept. Module one walks the reply structure, the order the three artefacts arrive in, and the language that pre-empts the brand-lead override. Includes the template reply and the worked example from a real theme migration.

Module 2. Reading a partner-submitted theme PR for conversion regressions before you read it for taste

A partner-submitted PR has a conversion signature. Module two walks the section-by-section read that catches the product page above-the-fold collapse, the cart drawer focus trap, and the checkout-button viewport drift before you open Figma. Includes the PR review checklist, the conversion regression heat map, and the worked verdict on three real PRs.

Module 3. The 360 px regression sweep that catches the Samsung A-series collapse before merge

Mobile-first review on a 360 px viewport is not the same as responsive review at 375 or 414. Module three walks the A-series-specific regression sweep, the safe-area inset trap on Android, and the long-form product-page collapse that only shows up under 365 px width. Includes the device matrix, the regression checklist, and the Lighthouse settings that surface the actual user trace.

Module 4. The Section 2.0 schema audit that decides whether a merchant editor can ship the section unaided

Section 2.0 lets merchants reorder blocks in the theme editor. It also lets them break the page. Module four walks the schema audit that decides whether the partner's section is editor-safe, including the block-limit logic, the preset trap, the conditional setting that breaks the live preview, and the migrate path from sections-everywhere to a section group. Includes the schema audit worksheet and the worked verdict on a real partner submission.

Module 5. The theme-token map between Figma and Liquid that survives a redesign sprint

Figma variables and Liquid settings drift the moment a redesign sprint lands. Module five walks the theme-token map that keeps them in sync, the audit cadence, the way to catch a typography ramp regression at PR time, and the bridge file that tells the partner which Figma token maps to which schema setting. Includes the map template and the audit script.

Module 6. Converting a CRO note and a brand comment into one ranked decision the merchant signs off on

CRO notes pull one way. Brand-lead comments pull another. Module six walks the ranking structure that turns the two inputs into one written decision, the conversion-evidence weighting, the brand-rule weighting, and the merchant-side sign-off language. Includes the decision memo template and the worked example from a contested PDP review.

Module 7. Accessibility review at PR time that prevents the post-launch regression report

Most a11y regressions surface a week after launch when the merchant runs their own audit and complains. Module seven walks the PR-time a11y review that catches contrast drift, focus-order breaks, ARIA-mismatch on the cart drawer, and the alt-text regression on dynamically rendered product images before merge. Includes the WCAG 2.2 AA checklist and the axe-DevTools workflow.

Module 8. The partner-handoff memo that ends the relitigation loop

Partners relitigate review comments because the memo gave them room. Module eight walks the handoff memo structure that closes the loop in one round, names the conversion evidence the partner has to address, separates blocker comments from preference comments, and makes the merchant brand lead the deciding voice on the preference list. Includes the memo template and three worked examples from real partner threads.

Module 9. Theme performance review that survives the Lighthouse merchant complaint

Merchants run Lighthouse on a launched theme and email screenshots when the score drops. Module nine walks the performance review at PR time, the LCP regression that hides behind a hero image, the CLS the partner introduced with the product-recommendations section, the JS budget the analytics app blew past, and the merchant-facing performance memo. Includes the budget worksheet and the worked verdict.

Module 10. Reviewing a redesign brief for the things that will break later

A redesign brief reads as ambition. The review job is to name the things that will break by sprint three. Module ten walks the brief review, the structural risks that show up in week one, the merchant editor risks that show up at handoff, and the conversion-evidence gaps the brief did not address. Includes the brief review checklist and the worked review of a real redesign brief.

Module 11. The cross-theme regression sweep when the section pattern lands in multiple themes

A section pattern that lands in one theme will land in three more by next quarter. Module eleven walks the cross-theme regression sweep, the pattern-library discipline that keeps drift down, the way to write a section once and let it inherit theme-specific tokens, and the review cadence when the same pattern shows up in a partner submission. Includes the pattern-library template and the regression sweep checklist.

Module 12. Closing the merchant feedback loop after launch so the next review is faster

Post-launch feedback is the input to the next review. Module twelve walks the feedback loop, the conversion-evidence trail the merchant generates in the first two weeks, the way to fold that evidence into the next theme version's review brief, and the partner conversation that turns the loop into a roadmap instead of a complaint thread. Includes the feedback loop template and the worked roadmap memo.

How this addresses your situation

Specific modules that map to what you said you are dealing with.

Friday-afternoon theme review thread with a CRO note and a brand-lead comment pulling opposite directions, modules 1 and 6.

Partner-submitted theme PR with a section that breaks on 360 px width, modules 2, 3, and 4.

Redesign sprint where Figma variables and Liquid settings have drifted, modules 5 and 11.

Post-launch merchant complaint about Lighthouse score, modules 7 and 9.

What you get with this course

Twelve written modules with worked examples drawn from real theme reviews and partner submissions.
Downloadable templates for the first-reply structure, the PR review checklist, the Section 2.0 schema audit worksheet, the theme-token map, the WCAG 2.2 AA review checklist, the partner handoff memo, the performance budget worksheet, the redesign brief review checklist, the pattern-library template, and the post-launch feedback loop template.
The hand-built implementation playbook tuned to your specific review queue and merchant mix, delivered alongside course access.
Thirty-day money-back if the review structure does not close a thread in one pass.

What you will have in hand by Day 1, Week 1, Month 1

Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.

Modules one to four cover the immediate review-queue triage, the next review thread closes in one pass.

Modules five to eight cover the Figma-to-Liquid map and the partner handoff, the next sprint inherits the discipline.

Modules nine to twelve cover performance, redesign brief review, cross-theme patterns, and the post-launch feedback loop.

Before and after

Before

Theme review threads run for a week. The CRO note and the brand-lead comment never reconcile. Partner PRs land with section schemas the merchant editor breaks on the first reorder. Lighthouse regressions surface from the merchant inbox a week after launch.

After

Reviews close in one reply. The CRO note and the brand-lead comment reconcile into a single ranked decision the merchant signs off on. Partner PRs ship with editor-safe section schemas. Performance and a11y regressions get caught at PR time, not in the merchant inbox.

What happens if you do not address this

Every review thread that drags into a taste argument costs the merchant trust, the partner momentum, and the reviewer credibility. Reviewers who do not move from preference language to conversion-evidence language get routed around. The merchant takes the next theme to the partner who replies fastest, not the reviewer who is right.

Who it is for

Storefront designers and theme reviewers inside Shopify or working closely with the merchant-facing storefront surface. People who sit between Figma, the Section 2.0 schema, partner-submitted theme PRs, and the CRO/brand-lead conversations that decide whether a merchant migrates. The course assumes you already know Liquid basics, Section 2.0 structure, the theme editor, and Lighthouse or the equivalent. It teaches you the reviewer's discipline that turns design taste into a defensible conversion decision.

Who this is NOT for. Not for designers who want a generic UI/UX course, not for partner agency leads who only build themes and never review them, not for merchants choosing a theme for their own store. The course is for the person whose name goes on the review reply that the merchant and the partner both have to accept.

How it arrives

Text-based course in the Art of Service learning environment, plus downloadable templates and worked examples for every module, plus the hand-built implementation playbook delivered alongside course access.

Time investment. Roughly six to eight hours across twelve modules. Each module is read once, applied once on a live review, and revisited when the situation recurs.

Why $199 is the right number

Free Shopify Polaris and partner-facing docs cover the theme editor and the Section 2.0 schema. They do not cover the reviewer's discipline that turns a review thread into a one-pass sign-off. Generic UX courses cover the design principles. They do not cover the conversion-evidence trail or the partner handoff memo. The gap this playbook fills is the reviewer's job, specifically.

FAQ

Does the course teach Liquid or theme development from scratch?

No. It assumes you already know Liquid, Section 2.0, the theme editor, and the basic accessibility checklist. It teaches the reviewer's discipline that turns those skills into a one-pass review reply.

Is the implementation playbook generic or tuned to my review queue?

Tuned. After purchase, the playbook is hand-built around the merchant mix and theme types you actually review, delivered alongside course access.

What does the thirty-day guarantee cover?

Full refund if the first-reply structure does not close a review thread in one pass on a real review you run in the first thirty days.

Is there a live cohort or office hours?

No. The course is self-paced text plus templates plus the hand-built implementation playbook. The discipline transfers through applied use, not through live sessions.

30-day money-back guarantee. If after a week of working through the materials this is not what you needed, reply to the receipt email and a full refund is processed. No questions, no forms.

Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.