# Thailand commerce preview deployment notes

Prepared: 2026-05-08 11:48 UTC

## Current repo state

- Git root: `/home/agent/.openclaw/workspace`
- Site directory: `side-ventures/thailand-commerce-site/`
- Current branch: `preview/thailand-commerce-site`
- Preview content baseline before this note update: `eea6613` — `Polish Thailand commerce preview UX`
- Recent site commits before this note update:
  - `eea6613` — Polish Thailand commerce preview UX
  - `b7337b2` — Add bundle colourway vote video to Thailand preview site
  - `e0d878c` — Add Thailand commerce preview deployment notes
  - `926b8fa` — Add Thailand commerce product vote pages
  - `f53c32a` — Add quality-check video to Thailand preview site
  - `e1d2c09` — Add Thailand commerce content plan preview
  - `92b2d97` — Add what-fits product video to Thailand preview site
  - `1f05894` — Add Thailand commerce media preview section
  - `101099b` — Add Thailand commerce preview site and content loop assets
- Remote configured on workspace repo: `origin https://github.com/gpe-openclaw/gpe-openclaw-workspace.git`
- Site working tree check at preparation time: no uncommitted changes inside `side-ventures/thailand-commerce-site/` before this documentation update. The wider workspace has unrelated dirty/untracked files, so only site files should ever be staged/committed for this preview.
- Exact final documentation commit should be read from `git log -1 --oneline -- side-ventures/thailand-commerce-site` after committing this file.

## What can be previewed locally now

Static site root:

```text
side-ventures/thailand-commerce-site/
```

Entry pages:
- `index.html` — landing page, first-drop thesis, media previews and internal waitlist placeholder
- `products.html` — product-vote/shop placeholder, no checkout
- `content.html` — content plan and short-form scripts
- `REVIEW_CHECKLIST.md` — internal acceptance checklist before any external preview/public launch

Run locally from the workspace:

```bash
cd /home/agent/.openclaw/workspace/side-ventures/thailand-commerce-site
python3 -m http.server 8088
```

Open:

```text
http://localhost:8088
```

A lightweight reference check found no missing local `href`/`src` files across `index.html`, `products.html`, and `content.html`.

## Public-action guardrails

- This is an internal preview site only until Alex approves publishing.
- No checkout is connected.
- No waitlist form is connected.
- Product materials, prices, dimensions, care notes and availability are placeholders.
- Generated model/product visuals are placeholders, not real wife/family/source footage.
- No supplier/origin/handmade/sustainability claims should be public until evidenced.

## What would be needed to deploy

### Option A — Cloudflare Pages preview

Best if Alex wants a private-ish branch preview workflow connected to GitHub.

Needed:
1. Alex approval to push branch `preview/thailand-commerce-site` to GitHub.
2. A Cloudflare Pages project connected to the GitHub repo.
3. Build command: empty/none.
4. Output/root directory: `side-ventures/thailand-commerce-site` if Cloudflare supports that for the connected repo setup.
5. If Cloudflare root-directory support is awkward, create a dedicated static-site repo later and put this site at repo root.
6. Use the Cloudflare branch preview URL for Alex/internal review.

### Option B — GitHub Pages preview

Simplest if Alex wants a low-moving-parts static preview and is happy with a GitHub Pages URL.

Needed:
1. Alex approval to create/use a dedicated repo or Pages branch.
2. Put contents of `side-ventures/thailand-commerce-site/` at repo root, or configure Pages from an appropriate branch/folder.
3. Enable GitHub Pages.
4. Share the generated static URL for internal review only.

### Option C — local-only review

Safest current option. No external action needed.

Needed:
1. Run the local server command above.
2. Review pages and checklist.
3. Add real sample/product/source assets before public deployment.

## Approval-gated steps

Ask Alex before any of these:

- pushing this branch externally
- creating or changing GitHub repositories/settings
- creating or changing Cloudflare Pages projects/settings
- publishing any URL publicly or sending it to others
- connecting checkout, payment, forms, email capture, analytics or pixels
- using real family/wife/source footage publicly
- making product, material, origin, handmade, sustainability, care or availability claims

## Recommended next action

Keep this local for one more review pass. Add real sample data/assets for the hero lane — product photos/video, measured dimensions, landed-cost estimate, packaging/postage assumption and evidence-backed material/origin notes — then ask Alex for one explicit approval: **push `preview/thailand-commerce-site` and create a Cloudflare Pages branch preview**.