Sitemap / IA: demo-test-b-general

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).

14 sitemap nodes (excludes Home)

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

# Site Architecture Rationale — demo-test-b-general (TEST/DEMO DATA)

## Proposed structure

```
Home (implicit)
├── Collection: kitchen (1 product: knife set)
├── Collection: electronics (1 product: speaker)
├── Collection: fitness-wellness (1 product: yoga mat)
├── Collection: home-office (1 product: desk lamp)
├── Collection: pet-supplies (1 product: dog leash)
├── Collection: home-garden (1 product: plant pot set)
├── Page: about
└── Page: support
```

## Decision-by-decision

| Decision | Classification | Rationale |
|---|---|---|
| **Six collections, one per category — not two, not one** | **OUR RECOMMENDED STANDARD** | Unlike Test A, these six products share no coherent grouping principle beyond "distinct household/lifestyle category." Merging any of them into a shared collection (e.g. forcing Kitchen + Home & Garden into one "Home" collection) would misrepresent the catalog to make it look more coherent than the evidence supports — the honest structure is one collection per category |
| Collection names taken directly from `product.identity.category` | **OUR RECOMMENDED STANDARD** | Same discipline as Test A — no separate naming decision invented |
| **No deeper subcategory nesting attempted, despite 6 distinct top-level groupings** | **OUR RECOMMENDED STANDARD**, per the Architecture SOP's shallow-hierarchy principle | With exactly 1 product per category, there is nothing to nest — depth should track real catalog density, not be added preemptively. If this catalog grows (e.g. 5 more kitchen products), *that* is when Kitchen would earn its own subcategories, not now. **This is a genuine, calibrated finding**: category *breadth* differs sharply from Test A (6 collections vs. 2), but category *depth* does not (both stay flat, 1 level) — the difference the evidence actually supports is breadth, not depth, and forcing artificial depth here would be exactly the kind of "look more sophisticated than the evidence warrants" the OBSERVED/NATIVE/RECOMMENDED discipline exists to prevent |
| One "About" page, unchanged in kind from Test A | **OUR RECOMMENDED STANDARD** | Every store needs one, regardless of catalog coherence — but note (see `brand.yaml`) that what this page can *honestly say* differs: Test A's About page can credibly claim category expertise; this one cannot, since `brand.positioning` itself is still `NOT YET CONFIRMED` |
| Fixed URL prefixes | **SHOPIFY NATIVE CAPABILITY** | Same non-negotiable platform facts as Test A |

## What this does NOT claim

This structure does not manufacture false thematic unity across six
unrelated products. Where Test A's IA could confidently draw on a
coherent Brand Direction, this one is built while `brand.positioning` is
still explicitly `NOT YET CONFIRMED` — the collections are organized by
the one thing that *is* certain (the product categories themselves), not
by a brand story that doesn't exist yet.

Raw sitemap.json

{
  "artifact_type": "site_architecture",
  "sitemap": {
    "nodes": [
      {
        "handle": "kitchen",
        "type": "collection"
      },
      {
        "handle": "stainless-steel-kitchen-knife-set",
        "parent": "kitchen",
        "type": "product"
      },
      {
        "handle": "electronics",
        "type": "collection"
      },
      {
        "handle": "portable-bluetooth-speaker",
        "parent": "electronics",
        "type": "product"
      },
      {
        "handle": "fitness-wellness",
        "type": "collection"
      },
      {
        "handle": "yoga-mat-with-carry-strap",
        "parent": "fitness-wellness",
        "type": "product"
      },
      {
        "handle": "home-office",
        "type": "collection"
      },
      {
        "handle": "led-desk-lamp",
        "parent": "home-office",
        "type": "product"
      },
      {
        "handle": "pet-supplies",
        "type": "collection"
      },
      {
        "handle": "dog-leash-reflective-stitching",
        "parent": "pet-supplies",
        "type": "product"
      },
      {
        "handle": "home-garden",
        "type": "collection"
      },
      {
        "handle": "ceramic-plant-pot-set",
        "parent": "home-garden",
        "type": "product"
      },
      {
        "handle": "about",
        "type": "page"
      },
      {
        "handle": "support",
        "type": "page"
      }
    ]
  },
  "status": "DRAFT"
}