Phase 2 · Theme and store structure
Theme Backup and Customization: Copy First, Then Edit Sections, Blocks, and Templates
Preview real customer paths and duplicate the theme first, then organize home, product, and collection pages with global settings, Sections, Blocks, and Templates before desktop/mobile acceptance, publishing, and rollback.
What counts as complete in this lesson
Use Online Store > Themes > Edit theme to reach the correct page, then configure, save, verify, and record the result. Completion means you can point to the saved state, verification result, and condition for continuing.
- Admin path
- Online Store > Themes > Edit theme
- Lesson output
- A dated theme backup, page-template list, home/product structure map, mobile captures, publish record, and rollback method for each change.
- Continue when
- The copy is identifiable, key pages and templates pass desktop/mobile preview, paths remain stable after publishing, and the prior theme and rollback owner are explicit.
- Stop when
- Pause customization and publishing when the live theme is not copied, template assignment is unclear, mobile is obstructed, an App conflicts, or rollback is not possible.
Evidence boundary: Theme-editor preview does not prove the live theme is published or that every device, App, dynamic source, and customer path works; reread after publishing.
Why this lesson comes now
Theme customization affects conversion and can touch every product, collection, menu, and checkout entry. Without a copy and rollback, one padding, template, App embed, or global-color change can put the whole store into an unexplained state.
Prepare before opening the admin
- Prepare current live theme name, version, backup naming rule, and rollback owner.
- List real products, collections, menus, search, cart, templates, and mobile devices.
- Map the home-page hierarchy, purpose of each change, and prior version to retain.
Follow the English admin step by step
After each step, refresh the admin or verify the storefront. A saved admin state does not automatically prove the customer-facing result.
Choose and preview the theme
Open Online Store > Themes to review the current theme and Theme Store options. Use Preview to inspect product, collection, menu, search, cart, and mobile paths instead of only the demo home page.
Expected result: Have preview results for the theme candidate across real store paths.
Completion standard: Product, collection, menu, search, cart, and mobile paths have no critical obstruction or break, so the candidate is safe to copy.
If the result is missing or wrong: When the entry or preview is wrong, confirm store, page title, and Preview context, then return to the complete Online Store > Themes section.
Evidence to keep: Record theme name, version, preview URL, device, critical-path result, and time. Preview does not prove the live theme is published.
Duplicate the theme and name the backup
Duplicate the current theme and use a date-and-purpose name such as `2026-08-01-before-launch`. Make all changes in the copy first and record who changed what and when.
Expected result: Have an identifiable, revertible copy separate from the current live theme.
Completion standard: Copy name, source theme, creation time, editor, and rollback target are reviewable.
If the result is missing or wrong: When a new template does not appear on the storefront, return to the product or collection Theme template assignment and check that the published theme contains the template.
Evidence to keep: Keep copy name, source, date, change record, template assignment, and live theme name.
Failure handling: Do not edit the live theme and rely on history to recover; copying before editing is the safety boundary of this lesson.
Understand Sections, Blocks, and Theme settings
Open Edit theme. A Section is a page module, a Block is an element inside a module, and Theme settings control global color, type, buttons, and layout. Change global settings first, then page-level content, so the same style is not repaired in several places.
Expected result: Have clear responsibility boundaries for global settings, page Sections, and Blocks.
Completion standard: Every change has an identifiable scope, saved state, storefront result, and recovery method.
If the result is missing or wrong: When an entry or field is wrong, confirm template, page title, and section/card instead of editing a similarly named template.
Evidence to keep: Record global setting, template, Section/Block, dynamic source, affected page, and capture.
Organize the information order on the home page
Use the first screen to explain what is sold, who it is for, and the next action; follow with benefits, featured products, trust, use cases, FAQ, and email signup. Give each Section one primary job and remove default modules with no information value.
Expected result: Have a home-page hierarchy and module responsibility from understanding to action.
Completion standard: Desktop and mobile order first screen, benefits, products, trust, FAQ, and CTA around customer tasks without blocked text or buttons.
If the result is missing or wrong: When mobile text or buttons are covered, check Section padding, fixed/sticky elements, App embeds, and safe areas instead of only shrinking the font.
Evidence to keep: Keep home-page map, Section order, mobile capture, CTA path, and retest time.
Failure handling: When every module competes for first-screen attention, return to customer tasks and remove or reorder before adding another banner.
Build product and collection Templates
Create a separate template only when products need a different structure instead of copying one for every SKU. After creating a template, assign it to the product or collection and check that dynamic sources read the current item.
Expected result: Have reusable product/collection templates with explicit assignment and dynamic-data results.
Completion standard: Target products and collections use the correct template, with fields, images, price, and dynamic sources reading the current object on the storefront.
If the result is missing or wrong: When a template exists but the storefront keeps the old structure, check product/collection assignment, published theme, and cache one object at a time.
Evidence to keep: Record template name, assigned products/collections, assignment time, dynamic source, storefront URL, and mobile result.
Complete preview, publish, and rollback records
Preview home, collections, products, cart, and search on desktop and mobile, checking that buttons, copy, image ratios, and sticky elements are not obstructed. Save captures before publishing the copy and keep the previous theme for rollback.
Expected result: Have the published copy, acceptance captures, publish time, prior theme, and an executable rollback action.
Completion standard: Critical paths pass before and after publishing, with a written owner and condition for restoring which theme.
If the result is missing or wrong: When the published result reverts to the old version, confirm the correct copy was published, check theme switch history and saved customization, and roll back to the prior theme when needed.
Evidence to keep: Keep desktop/mobile captures, published theme, time, critical URLs, issue, rollback owner, and rollback result.
Failure handling: When layout, template, or App conflicts appear after publishing, restore the prior theme and preserve evidence before repairing and retesting in the copy.
Apply the decision in your store
Preview real product, collection, search, and cart paths before duplicating and naming a backup. Make changes in the copy: global Theme settings first, page Sections/Blocks second, product/collection Templates third, then capture desktop/mobile, publish, and rehearse rollback.
Use the admin path above, then apply it to one concrete situation.
Use this lesson in your store
By the end, you should have: A dated theme backup, template inventory, home and product-page structure map, mobile screenshots, and a rollback method for every change.
Relevant admin path: Online Store > Themes > Edit theme
Make the decision before reading the reason
Choose the action that solves the problem first, then read the explanation.
Confirm these items in your store
Check each item against the current store; this checklist does not save settings or run tests.
This screen still cannot tell you: Theme-editor preview does not prove the live theme is published or that every device, app, and real customer flow works
Continue when: a clearly named backup exists, key templates and mobile first view are previewed, and publisher/rollback point are explicit
Stop when: If changes exist only in the live theme, no backup exists, or mobile purchase flow is obstructed, do not publish
Next: Next, build Pages, Menus, and URL redirects so customers can actually find the content.
Complete the decision or checks first. When information is missing, a pause is safer than guessing a pass.
Recovery rehearsal after theme backup
Turn common failures into executable recovery actions: locate the version, template, or module first, then repair the copy, pause publishing, or restore the prior version. Record the actual result instead of treating “knowing how to roll back” as a rehearsal.
| Scenario | Check first | Continue when | Failure/rollback | Evidence |
|---|---|---|---|---|
| New template is not visible | Product/collection assignment and published theme | Storefront reads the current object’s template and dynamic source | Return to assignment or prior theme | Object URL/template: ________ |
| Mobile obstruction | Padding, sticky/fixed, App embed, safe area | Buttons, copy, and image ratio are usable | Restore copy or remove conflicting module | Device/capture: ________ |
| Published result becomes old version | Published copy, theme switch history, saved state | Correct copy is stable on critical paths | Restore prior theme and preserve issue evidence | Time/owner: ________ |
| App or template conflict | Copy version, App embed, template assignment | Conflict is located and retest passes | Pause publish or roll back prior version | Issue/retest: ________ |
Decisions to make in this lesson
Enter the actual values for this store row by row. Do not treat examples or planned values as completed work. Mark a row passed only when the condition and saved or tested evidence are present.
| Item | Recommended setting | Why |
|---|---|---|
| Change location | Global Theme settings, then Sections/Blocks | Reduces duplicate fixes and style drift |
| Backup naming | Date + purpose | Makes source and rollback target identifiable |
| Template count | Create for real structural differences | Avoid an unmaintainable template per SKU |
| Publish action | Preview, capture, second-person review, then publish | Turns rollback from a promise into an action |
Do not change these blindly
- Do not make major changes directly on the live theme and rely on memory to recover.
- Do not copy a template for every SKU or forget to assign it back to products or collections.
- Do not check only desktop or a Theme Store demo; accept mobile, real objects, and the post-publish version.
FAQ
Does duplicating a theme make it live automatically?
No. The copy needs separate preview, editing, acceptance, and publishing; keep the current live theme as the rollback target before publishing.
Should every product have its own template?
No. Split templates only when product or collection structure truly differs, or the template count becomes difficult to maintain.
Can we publish after Theme editor preview passes?
Also check real products, collections, search, cart, templates, and App effects on desktop and mobile, and write the post-publish rollback action.
Conclusion and continue line
Theme work is complete not when the page merely looks better, but when every change has a copy, scope, template assignment, real storefront result, and rollback action. Continue only when critical desktop/mobile paths are stable and both published copy and prior theme are identifiable.