@zappie/theme-base 0.1.0 → 0.1.1

package/CHANGELOG.md

@@ -0,0 +1,30 @@
+# @zappie/theme-base
+
+## 0.1.1
+
+### Patch Changes
+
+- 1e6f420: Each package now has a README written for people installing it from npm: what it does, how to install and use it, its entry points, and links to docs.zappie.ai. `@zappie/kit` gains its first README.
+- Updated dependencies [38f23ac]
+- Updated dependencies [1e6f420]
+  - @zappie/sdk@0.1.1
+  - @zappie/foundations@0.1.1
+  - @zappie/tokens@0.1.1
+
+## 0.1.0
+
+### Minor Changes
+
+- - `@zappie/tokens`: Publish the semantic storefront token contract, CSS aliases, validation and compilation tools.
+  - `@zappie/sdk`: Publish the framework-agnostic storefront client and its React, server, checkout, customer, places, visits and URL entries.
+  - `@zappie/foundations`: Publish accessible, unstyled React primitives for storefront catalogue, item, fulfilment and cart experiences.
+  - `@zappie/theme-base`: Publish the reusable base storefront theme and its catalogue, item and cart surfaces.
+  - `@zappie/kit`: Publish the built component registry consumed by the Zappie CLI.
+  - `zappie`: Publish the component CLI with `add`, `list` and `diff`.
+
+### Patch Changes
+
+- Updated dependencies
+  - @zappie/tokens@0.1.0
+  - @zappie/sdk@0.1.0
+  - @zappie/foundations@0.1.0

package/README.md

@@ -1,65 +1,38 @@
-# Base storefront theme
+# @zappie/theme-base
 
-Workstream 06, Stage A, PR 3: the cart now supports configured lines, quantity
-changes, editing, removal, issue fixes, server-quoted totals and the existing
-host payment flow. Empty and loading states use the same foundations overlay.
+The base storefront theme that Zappie's own storefront app renders: the catalogue, item sheets, cart and checkout steps. It's built only from Zappie's public packages, `@zappie/sdk`, `@zappie/foundations` and `@zappie/tokens`, so it also shows how far those packages go on their own.
 
-The adapter seeds the existing host pickup/delivery choice. Fulfilment, address,
-schedule and promo editors follow in PR 4; a new delivery address cannot yet be
-entered in this cart. Pickup provides the end-to-end payment test path.
+```sh
+npm install @zappie/theme-base
+```
 
-The host basket owns initial lines during migration. `connectBasketBridge`
-reconciles complete snapshots into the SDK and mirrors subsequent SDK edits
-back into the same legacy storage bucket. Line identities, choices, notes and
-unavailable-item issues survive. A private SDK import seam makes this atomic;
-no backend API or public cart method changes. Scope changes detach the bridge.
+React 19.2 is a peer dependency.
 
-`@zappie/theme-base/host-bridge` exposes the temporary provider contract for
-payment, sign-in, customer details and address suggestions. The host checks a
-current quote and synchronized basket, closes the cart through foundations,
-waits for the URL change and cart unmount, and only then starts the existing
-payment flow. Sign-in similarly releases the foundations modal before invoking
-the host auth callback, which restores the cart after authentication.
-Address lookup uses the existing host Places endpoint. Fulfilment must match
-the current host branch and pickup/delivery bucket before checkout.
+## Who it's for
 
-Use `pnpm dev` and open an existing test store with
-`?template=base-next&modal_id=review-menu`. Below 1024px the cart is a full-height
-swipeable drawer; from 1024px it is a centred dialog. Deep-link close retains
-the store URL. All other storefront templates retain their existing cart.
+Zappie's storefront app mounts this theme and supplies payment, sign-in, rewards and delivery regions through `@zappie/theme-base/host-bridge`. That bridge is a temporary contract with Zappie's own app. It will be replaced, so it isn't a stable way to run the theme in your own project.
 
-`theme.json` copies the approved default-template tokens. Regenerate the scoped
-CSS with `pnpm base-next:tokens`. Explicit `.dark` / `data-theme="dark"` choices
-use dark tokens; the default ignores the operating-system preference.
+Building your own storefront or template? Start from `@zappie/sdk`, `@zappie/foundations` and the kit's copy-in components (`npx zappie add <name>`). Use this theme as a reference for how the parts fit together.
 
-The host adapters in `lib/templates/base-next` reuse the default catalogue,
-manifest and SEO. This package imports only public commerce packages. The
-host-side seam owns its provider and legacy template contract.
+## Entry points
 
-Registration is build-time gated: production serves base-next only with
-`ZAPPIE_ENABLE_BASE_NEXT=1`. The generated registry contains static gated entries;
-builds do not rewrite tracked files. Workspace themes never enter artifact
-admission. The external-template development host keeps its existing cart.
+| Import                                                 | For                                                 |
+| ------------------------------------------------------ | --------------------------------------------------- |
+| `@zappie/theme-base/catalogue`, `/item`, `/item-frame` | The menu and item views                             |
+| `@zappie/theme-base/cart` and `/checkout`              | The cart and checkout steps                         |
+| `@zappie/theme-base/address` and `/navigation`         | Address entry and in-page navigation                |
+| `@zappie/theme-base/styles.css`                        | The theme's styles, scoped to its own root          |
+| `@zappie/theme-base/host-bridge`                       | The temporary contract with Zappie's storefront app |
 
-`pnpm base-next:metrics` updates `docs/base-next-metrics.json`, preserving the
-pre-migration baseline. Counts cover the explicit PRD legacy paths and all
-non-test cart source. CSS totals include compiled tokens; legacy shared CSS
-cannot be attributed to cart alone. These incremental metrics are not a claim of
-full cart parity or a completed Stage A reduction.
+## Docs
 
-The catalogue is exported from `@zappie/theme-base/catalogue`. A template wraps
-it in `CatalogueNavigationProvider` from `@zappie/theme-base/navigation`, using
-its own router implementation or the framework-independent
-`createUrlNavigation()` default. Item links and URL state come from that
-navigation context. `initialMenu` contains menus/categories and no items;
-the supplied policy chooses eager or progressive reads. `orderAction` supplies
-the Place/Schedule/View label. Search's controlled source performs bounded
-reads, and themeClass reaches mobile overlay portals.
+- [Open Storefronts](https://docs.zappie.ai/open-storefronts)
+- [Build a storefront](https://docs.zappie.ai/guides/build-a-storefront)
 
-## Visit counting
+## Status
 
-A template app calls `countPage` from `@zappie/sdk/visits` after each route
-change, with `enabled: false` in editors and previews. The base screens then
-count successful item adds and cart opens, and attach the visit's source and
-campaign to SDK checkout. The current Next app does not call `countPage`, so
-these events remain disabled there.
+The theme is at `0.x`. It changes with Zappie's storefront app, and any release can change its entry points. Each change is listed in `CHANGELOG.md`.
+
+## License
+
+MIT

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@zappie/theme-base",
-  "version": "0.1.0",
-  "description": "The base Zappie storefront theme, built only from public packages (template id base-next).",
+  "version": "0.1.1",
+  "description": "The base storefront theme Zappie's own storefront app renders, built only from Zappie's public packages.",
   "type": "module",
   "sideEffects": [
     "**/*.css"
@@ -50,12 +50,13 @@
     "provenance": false
   },
   "files": [
-    "dist"
+    "dist",
+    "CHANGELOG.md"
   ],
   "dependencies": {
-    "@zappie/foundations": "^0.1.0",
-    "@zappie/sdk": "^0.1.0",
-    "@zappie/tokens": "^0.1.0"
+    "@zappie/foundations": "^0.1.1",
+    "@zappie/sdk": "^0.1.1",
+    "@zappie/tokens": "^0.1.1"
   },
   "peerDependencies": {
     "react": "^19.2.0"