Files
zeekay 1d88fac03f Load hanzo.agency's tags from cloud, after consent, under its own key
The page now mounts the docs.hanzo.ai wiring: @hanzo/event's stream posts
under project agency's publishable key, startTags loads the GA4 and Meta
tags cloud holds for that project once the visitor consents, and
@hanzo/ui/consent is the banner, a lazy chunk under its own GuiProvider.

The raw gtag in index.html goes, with the GA id in hanzo.yml and the vite
step that wrote it in: it loaded for every visitor without asking, and
beside the tag manager would count each visit twice. The stream carried
the hanzo org's key; it carries the project's now. Checkout helpers ask
analytics() for the provider's client rather than holding one of their
own.

vite resolves react-native to react-native-web and prefers .web.*
extensions, as gui needs. Overrides keep one gui and one event client.
2026-10-25 20:30:14 -07:00

49 lines
861 B
YAML

name: agency
slug: agency
version: 0.1.7
type: site
framework:
name: vite
preset: react
buildCommand: pnpm build
outputDir: dist
singlePageApp: true
routing:
domain: hanzo.agency
aliases:
- www.hanzo.agency
- agency.hanzo.ai
deploy:
plane: sites
publishScript: https://git.hanzo.ai/hanzoai/ci/.github/actions/site@v1
image: ghcr.io/hanzoai/agency
kubernetes:
namespace: hanzo
service: agency
port: 3000
commerce:
org: hanzo
checkoutUrl: https://pay.hanzo.ai
commerceApi: https://api.hanzo.ai/v1/commerce
providers:
- square
- crypto
- wire
disallowed:
- stripe
iam:
issuer: https://hanzo.id
clientId: hanzo-agency
billingPortal: https://billing.hanzo.ai
calendar:
bookingUrl: https://calendar.app.google/z1YsZQrqR4s6jQqD8
analytics:
insightsUrl: https://api.hanzo.ai/v1/event