# Thailand commerce public-preview prep pack Prepared: 2026-05-08 12:19 UTC Scope: **public-preview preparation only**. Do not push, deploy, connect forms, connect checkout, collect data, post publicly, or share a URL without Alex's explicit approval. ## Strongest recommendation Keep the site local until the hero woven-bag lane has real sourcing evidence and all generated/product placeholders are clearly replaced or labelled. The safest next public step, once those checks are complete, is a **Cloudflare Pages branch preview** from `preview/thailand-commerce-site` with no custom domain, no checkout, no analytics/pixels, and no form backend. ## Current public-preview readiness Status: **not public-ready yet**. The local preview is useful for internal review, but public preview should wait until these risks are controlled: - The name **Thai Market Finds** is still a temporary MVP name and has not had trademark/domain/social-handle checks. - Product photos/videos are generated/concept placeholders, not verified real source/product media. - Product specs, prices, materials, dimensions, weights, care notes, origin details and availability are indicative only. - Policies are planning copy, not legal advice. - Waitlist/product-vote form is static and does not submit data. - No privacy/data-processing setup exists for a live form. - No evidence pack exists yet for supplier, material, handmade, sustainability or repeat-supply claims. ## What must change before any public preview ### 1. Replace or clearly label generated placeholders Minimum public-preview rule: - If the asset is generated or concept art, label it near the asset as **"Concept preview image/video — final product may differ"**. - If the page implies real product/source footage, replace it with real approved media before publishing. - Do not use generated wife/family/model/source imagery in a way that implies a real person, real supplier, real market visit, or real product proof. Preferred public-preview standard: - Replace the hero woven-bag images/videos with real phone photos/videos from wife/family/source sample review. - Keep generated visuals only in a clearly marked internal/documentation section or remove them from public pages. ### 2. Turn all placeholder commercial claims into evidence-backed copy Before publishing, verify or remove: - Materials: rattan/straw/water hyacinth/cotton/silk/other. - Dimensions and weights. - Unit price and landed-cost assumptions. - Delivery timing and UK dispatch assumptions. - Care instructions. - Handmade/artisan/family-sourced/local-market/origin claims. - Sustainability, natural, ethical, recycled, fair, eco or similar claims. - Availability, colourways and repeat-supply likelihood. ### 3. Make the data collection position explicit For a public preview, choose one: - **No data collection:** keep the waitlist CTA as "coming soon" or mailto only; remove any language implying sign-up capture. - **Approved waitlist collection:** connect a form only after privacy copy, storage owner, export process, deletion process and consent wording are approved. Do not connect Tally, Google Forms, Shopify, Klaviyo, Mailchimp, analytics, pixels or external databases without explicit approval. ### 4. Add legal/compliance guardrails to public pages Before public preview: - Add a short footer note: "Preview site only. Products, prices and availability are subject to change. No checkout is live." - Ensure policies avoid promising delivery/returns terms that are not operationally approved. - Keep categories limited to low-compliance adult accessories/gifts only. - Avoid food, cosmetics, balms, medicines, toys/children's goods, electricals, batteries, branded/lookalike goods, sharp objects, fragile/bulky items and health/spiritual claim products. ### 5. Confirm branch and deployment hygiene - Confirm `preview/thailand-commerce-site` only contains intended site docs/assets. - Run link/asset checks locally. - Confirm no secrets, private family details, phone numbers, addresses, supplier private information or unapproved personal images are in public files. - Confirm media file sizes are acceptable for a static preview. ## Generated-media disclosure notes Use these notes wherever generated/concept media remains visible: Short page label: > Concept preview image/video — final product, materials and styling may differ. Product detail disclosure: > This preview uses concept/generated media while we validate real sourcing options. Public product claims will be updated only after sample photos, measurements, materials and supplier evidence are confirmed. Footer disclosure: > Preview site: some visuals are concept/generated placeholders. No checkout is live. Products, prices, materials, availability and delivery details are subject to confirmation. Social/content disclosure if a generated clip is ever used externally: > Concept preview, not final stock footage. We are testing which Thai market finds people want us to source first. Do **not** use generated imagery to imply: - a real named supplier; - real wife/family footage; - real customer/model endorsement; - confirmed product material/origin; - guaranteed handmade/sustainable/ethical status. ## Placeholder removal checklist Use this as the final pre-public checklist. ### Pages - [ ] `index.html`: replace or label all concept/generated hero, product and lifestyle visuals. - [ ] `index.html`: verify first-drop claims and remove unsupported origin/handmade/sustainability wording. - [ ] `products.html`: replace sample product specs with real dimensions, weights, materials and price assumptions, or mark them clearly as examples. - [ ] `products.html`: keep checkout disabled and remove any wording that implies live purchase availability. - [ ] `waitlist-form.html`: either keep static/no-submit with clear language, or connect only after approved data/privacy setup. - [ ] `content.html`: mark generated clips as concepts; remove any copy implying real source footage if not true. - [ ] `policies.html`: make policy wording preview-safe and remove operational promises not approved. ### Assets - [ ] Replace generated/concept hero bag visual with real product photo/video if available. - [ ] Replace generated lifestyle/model imagery with approved real wife/model footage, or remove. - [ ] Replace floating-market/source-story imagery with approved real sourcing footage, or label as illustrative. - [ ] Keep only media that Alex is comfortable publishing publicly. - [ ] Confirm file names and metadata do not reveal private information. ### Docs/data - [ ] Do not publish private sourcing notes, supplier details, family contact details, raw cost sheets or internal margin assumptions unless intentionally included. - [ ] Review `database/*.csv` before publishing; remove private supplier/waitlist rows if any are added later. - [ ] Keep internal docs local if they include strategy, margins, supplier risks or private workflow. ## Domain/name check TODOs Temporary MVP name: **Thai Market Finds**. Backup candidate: **Market Kin**. Before custom domain or public brand launch: - [ ] Search UK IPO trademarks for exact and similar names. - [ ] Search Companies House for similar trading names. - [ ] Search Google/Bing for exact phrase conflicts. - [ ] Check `.co.uk`, `.uk`, `.com` domain availability. - [ ] Check Instagram, TikTok, YouTube, Pinterest and Facebook handle availability. - [ ] Check Etsy/eBay/Amazon/Shopify-style marketplace name conflicts. - [ ] Check obvious negative meanings or cultural issues in Thai/English. - [ ] Decide whether the public preview uses the temporary name or a neutral project label. - [ ] Do not buy a domain or create accounts without Alex approval. Suggested low-risk preview naming if checks are not complete: > Thai Market Finds — preview concept Avoid presenting the name as final until checks are done. ## Cloudflare Pages branch preview steps Do not execute these without Alex approval. Recommended route because it keeps preview deployment separate from production/custom-domain decisions. 1. Confirm local working tree for site files only: ```bash git -C /home/agent/.openclaw/workspace status --short -- side-ventures/thailand-commerce-site memory/side-ventures/thailand-commerce-assets/public-preview-prep-pack.md ``` 2. Push the preview branch after approval: ```bash git -C /home/agent/.openclaw/workspace push origin preview/thailand-commerce-site ``` 3. In Cloudflare Pages, create/connect a Pages project to the GitHub repo. 4. Select branch preview support for `preview/thailand-commerce-site`. 5. Use static settings: - Framework preset: none/static. - Build command: empty/none. - Output directory: `side-ventures/thailand-commerce-site` if supported. 6. If monorepo output directory is awkward, create a dedicated static-site repo later and copy the site to repo root after approval. 7. Keep custom domains disabled for first preview. 8. Keep analytics/pixels disabled unless separately approved. 9. Share the generated branch-preview URL only with Alex/internal reviewers. 10. After review, either keep the branch preview private-ish/unlinked, password/protection if available, or delete/disable it. ## GitHub Pages branch preview steps Do not execute these without Alex approval. Use this if Cloudflare Pages is too much setup for a first static preview. 1. Create/use a dedicated preview repo or branch after approval. 2. Copy `side-ventures/thailand-commerce-site/` contents to the repo root, or configure Pages to serve a suitable branch/folder. 3. Ensure internal-only docs/private CSVs are excluded if not intended for public view. 4. Enable GitHub Pages from the selected branch/folder. 5. Use the generated `github.io` URL for internal review only. 6. Do not add custom domain until name/domain checks are complete. 7. Disable/remove the Pages site after review if Alex does not want it live. ## Rollback plan If a public/branch preview goes live by mistake or needs to be withdrawn: ### Fast rollback 1. Remove or disable the Cloudflare/GitHub Pages deployment/project. 2. If pushed branch should not remain public, delete the remote preview branch: ```bash git -C /home/agent/.openclaw/workspace push origin --delete preview/thailand-commerce-site ``` 3. If a custom domain was connected, remove DNS/CNAME records and disconnect the domain from Pages. 4. Confirm the preview URL returns 404/disabled. 5. Remove any shared links from public posts/messages where possible. ### Content rollback without deleting preview 1. Revert the problematic commit locally: ```bash git -C /home/agent/.openclaw/workspace revert ``` 2. Push the rollback commit after approval. 3. Confirm the deployment rebuilt and the issue is gone. ### Data/privacy incident check If private data was exposed: - Identify the exact files/commits/URLs. - Remove the content from live deployment immediately. - Assume Git history may still contain it if pushed; decide whether history rewrite is required. - Do not continue sharing links until Alex has reviewed the exposure. ## Exact approval wording Alex could give ### Approval to push branch only, no deployment > I approve pushing branch `preview/thailand-commerce-site` to GitHub for backup/review only. Do not deploy it, do not create a public URL, do not connect forms, checkout, analytics, pixels or domains, and do not share it outside our internal review. ### Approval to create Cloudflare Pages branch preview > I approve pushing branch `preview/thailand-commerce-site` to GitHub and creating a Cloudflare Pages branch preview for `side-ventures/thailand-commerce-site`. Keep it as a preview URL only: no custom domain, no checkout, no live form/data collection, no analytics or pixels, no public posting, and share the URL only with me/internal reviewers. ### Approval to create GitHub Pages preview > I approve creating a GitHub Pages static preview from `side-ventures/thailand-commerce-site`. Keep it preview-only with no custom domain, no checkout, no live form/data collection, no analytics or pixels, and share the URL only with me/internal reviewers. ### Approval to connect a waitlist form later > I approve connecting a waitlist/product-vote form for the Thailand commerce preview after the privacy wording, storage location, export process, deletion process and consent wording are documented. Do not connect checkout or payment. ### Approval to publish with real media later > I approve using the selected real wife/family/product/source media in the Thailand commerce public preview. Do not use private contact details, private supplier details or unsupported product/origin/material/handmade/sustainability claims. ## Final go/no-go gate before public preview Public preview is a **go** only when all are true: - [ ] Alex has approved push/deploy in exact terms. - [ ] Generated/concept media is replaced or clearly disclosed. - [ ] Placeholder product claims are removed or evidence-backed. - [ ] No checkout/payment is active. - [ ] Form/data collection is either disabled or explicitly approved with privacy wording. - [ ] Name/domain checks are complete or the preview name is clearly temporary. - [ ] Private sourcing/family/supplier/margin data is not public. - [ ] Link/asset check passes locally. - [ ] Rollback path is understood. If any item is uncertain, keep the preview local.