tanshu
de0553d0d4
The route from "mozimo.in displays Shopify products" to "mozimo.in sells them", as a plan with a phase spine and gates, plus the open decision tickets that still shape it and the evidence they rest on. - .scratch/shopify-headless-commerce/: plan.md (phases and gates), map.md (the wayfinder map), 10 open decision tickets - CONTEXT.md: Storefront / Theme store / Cart / Parity vocabulary - docs/adr/0001-0003: Checkout stays Shopify-hosted, one Variant per product, the checkout domain stays shop.mozimo.in - docs/research/ and docs/shopify-catalog-inventory.md: verified store facts, the Cart API probe, and the catalogue inventory Raw Shopify doc scrapes under .scratch/shopify-research/ are ignored: they are working material, not record.
24 lines
1.0 KiB
Markdown
24 lines
1.0 KiB
Markdown
# Audit what points at the Theme store
|
|
|
|
`Type:` task (HITL)
|
|
`Status:` open
|
|
|
|
Part of [the map](../map.md).
|
|
|
|
## Question
|
|
|
|
What currently sends traffic to `shop.mozimo.in`?
|
|
|
|
This cannot be answered from the codebase alone, and finding a live campaign pointed at a Theme store URL two days before cutover is the classic way this migration goes wrong. Inventory:
|
|
|
|
- **In the repo** — every hardcoded `shop.mozimo.in` reference, including the header's account and Bag icons, and any product URL built from the Shopify domain. (The audit should cover this, but the repo half is discoverable now.)
|
|
- **Outside the repo** — paid ad campaigns and their landing URLs, Google and Meta shopping feeds, Instagram and Facebook shop, marketplace listings, email templates, and printed packaging or QR codes.
|
|
|
|
For each: what it points at, whether a mozimo.in equivalent exists, and whether it needs updating before or after cutover.
|
|
|
|
This gates Phase 5 and sets how much redirect coverage is actually required.
|
|
|
|
## Answer
|
|
|
|
<!-- filled on resolution -->
|