The marketing Deployment is a SPA server over this repo's dist and nothing else:
no SPA_* config, no API of its own (that is api.hanzo.ai). So the export is
published to the Sites plane as `marketing`, s3://hanzo-sites/hanzo/marketing, for the
edge to serve with no pod. The build gate already produces dist in the same
job, so the lane names no build of its own.
Checked in headless Chromium: the export on marketing.hanzo.ai renders what the pod
renders.
Co-authored-by: Hanzo Dev <[email protected]>
The web app for /v1/marketing on api.hanzo.ai (audiences, drip sequences and
their steps, enrollments, campaigns, the send calendar, promos and opt-outs)
and the small Go service beside it. Earlier history is kept privately in
hanzoai/marketing-v1.
Co-authored-by: Hanzo Dev <[email protected]>
zeekay
