Sitemap / IA: demo-product-first

Visual tree

Home is rendered here as the tree's root so the page has something to hang collections off of. It is a UI convenience only -- the underlying sitemap.json artifact never contains a "home" node, per skills/shopify-ia/SKILL.md ("Home is implicit, not its own sitemap node"). The node count below therefore excludes Home, matching the convention already used by projects/mc-batch-13-general (7 collections + 13 products + 2 pages = 22 nodes).

4 sitemap nodes (excludes Home)

Rationale, URL rules, multi-market architecture, internal linking

# Site Architecture Rationale — demo-product-first (TEST/DEMO DATA)

Deliberately small, matching a single-product demo — not a template for a
real catalog. Every choice below is traced to
`organization.yaml`/`brand.yaml`/`product.yaml`, CONFIRMED Shopify
platform facts, or an explicit Anker-inspired principle, never invented.

## Proposed structure

```
Home (implicit -- not a sitemap node; Shopify's storefront root is not a
      /pages/<handle> object, so it is not represented in sitemap.json)
├── Collection: pet-travel-accessories
│   └── Product: portable-stainless-steel-dog-water-bottle-500ml
├── Page: about
└── Page: support
```

## Decision-by-decision

| Decision | Classification | Rationale |
|---|---|---|
| One collection, named from `product.identity.category` ("Pet Travel Accessories") | **OUR RECOMMENDED STANDARD** | The product has exactly one category and this is a demo, not a real catalog — a single collection matching the category is the minimum honest structure, not an attempt to look like a bigger store |
| Collection/Product/Page URL prefixes (`/collections/`, `/products/`, `/pages/`) | **SHOPIFY NATIVE CAPABILITY** | Fixed, non-negotiable per `scripts/shopify_platform_constraints_check.py`'s constants table — not a choice, a platform fact |
| A dedicated "About" page separate from a Collection/Product | **OBSERVED ANKER PATTERN**, generalized as **OUR RECOMMENDED STANDARD** | Anker (and most real storefronts) separates brand/trust content from transactional pages — the pattern generalizes even though Anker's own About-equivalent content lives on a much larger, partly custom storefront we are not copying |
| A "Support" placeholder page rather than a full FAQ/ticketing system | **OUR RECOMMENDED STANDARD** | `product.limitations.assessment_status` is still `NOT_ASSESSED` and no real support process exists yet for a fictional demo product — a placeholder page is honest; a fabricated FAQ would not be |
| No blog/guide content yet | **OUR RECOMMENDED STANDARD** (deferred) | Blog/guide content requires real customer questions (Tier 2, `customer_reality` — not yet formalized) or genuine product education need; inventing guide topics for a demo product would violate the no-fabricated-content rule |
| Not copying Anker's market path-prefix structure (`/uk`, `/de`, etc.) | **OBSERVED ANKER PATTERN, explicitly NOT adopted** | Anker's multi-market path-prefix structure solves a problem (dozens of live regional storefronts) this single-demo-product project doesn't have. Adopting it here would be copying an Anker URL pattern without the underlying need — exactly what this rule exists to prevent |

## What this does NOT claim

This IA does not represent Anker's own URL structure as something a
standard Shopify theme store can replicate outright — Anker is partly a
custom/headless storefront (see `archive/anker-raw-evidence/`, not yet
distilled into `references/` in this phase). Nothing here assumes
Anker-specific capabilities (per-market subdomains, custom UCP endpoints)
are available in a standard Shopify theme.

Raw sitemap.json

{
  "artifact_type": "site_architecture",
  "sitemap": {
    "nodes": [
      {
        "handle": "pet-travel-accessories",
        "type": "collection"
      },
      {
        "handle": "portable-stainless-steel-dog-water-bottle-500ml",
        "parent": "pet-travel-accessories",
        "type": "product"
      },
      {
        "handle": "about",
        "type": "page"
      },
      {
        "handle": "support",
        "type": "page"
      }
    ]
  },
  "status": "DRAFT"
}