@drip-apex/apex-cli 0.14.1 → 0.15.0

package/README.md

@@ -177,7 +177,7 @@ including every subcommand, argument, option, and alias.
 - `apex triggers apply-recipe` — apply a server-owned trigger recipe.
 - `apex triggers enable-capture` — enable temporary setup capture.
 - `apex triggers disable-capture` — disable setup capture and clear its expiry.
-- `apex domains` — manage install domains.
+- `apex domains` — manage install domains, and landing-page domains (`claim`, `register`, `status`, `unclaim`; registering asks for a price confirmation).
 - `apex handover` — manage cross-domain identity handover.
 - `apex install` — generate storefront installation snippets.
 - `apex funnels` — manage analytics funnels.
@@ -215,7 +215,7 @@ including every subcommand, argument, option, and alias.
 
 - `apex external-pixels` — manage external pixel snippets.
 - `apex assets` — manage uploaded assets.
-- `apex landing-pages` — discover landing pages.
+- `apex landing-pages` — build landing pages with your own tools, then apply, preview, deploy and roll them back.
 - `apex brand` — manage brand context.
 - `apex shops` — manage shops and active-shop context.
 - `apex skills` — inspect agent skill guidance.
@@ -230,10 +230,47 @@ command inventory:
 | `apex admin shops archive <shopId>` | Archive a shop and disable Apex delivery; use `--force` in non-interactive environments. |
 | `apex admin shops restore <shopId>` | Restore an archived shop while leaving its runtime kill switch unchanged. |
 
+## Landing pages built outside Apex
+
+A landing page is built in a checkout folder by any tool (Claude Code, Codex,
+a static-site build); Apex keeps its versions, goals and deploys.
+
+```bash
+apex landing-pages create --name "Fall sale" --out ./fall-sale   # or: pull <id> --out ./fall-sale
+# edit ./fall-sale/index.html and its assets; context/ holds brand, catalog, offers and reviews
+apex landing-pages plan ./fall-sale             # what would change
+apex landing-pages apply ./fall-sale --yes      # new version + signed preview link (24 hours)
+apex landing-pages deploy ./fall-sale           # live on the claimed host in apex-landing-page.json
+apex landing-pages rollback ./fall-sale --version 1
+apex landing-pages experiment ./fall-sale --control 1 --variant 2   # draft split; start it in the dashboard
+```
+
+The folder holds the page files (index.html at the root, at most 300 files
+and 25 MB; html, css, js, json, svg, images, fonts, txt, xml, webmanifest),
+`apex-landing-page.json` and the `context/` folder (each pull replaces its JSON
+files with the server's current set). Build with relative asset
+URLs (Vite `base: "./"`). `apex-landing-page.json` sets the name, slug, an
+claimed `host` (deploy needs one, or `--host`: claim it with
+`apex domains claim <host>`; Apex has no shared pages host yet), the `path`, whether Apex injects the shop snippet
+(`snippet`, on by default), the `shop_hosts` that receive the visitor's identity
+on outbound links (default: the shop's install domains), the `goals`
+(key, name, type click, pageview or custom) and an optional `experiment`
+(control and variant version numbers). Apply refuses to run without `--yes`
+when no terminal can confirm, and refuses with exit 5 when the page changed
+since the pull (`--force` replaces it anyway). Pull refuses to overwrite a
+checkout with changes that are not applied, or a folder's own files that are not a
+checkout (exit 5; `--force` discards or replaces them). A deploy makes the page's goals match
+`apex-landing-page.json`, so a goal edited in the dashboard is reset. A deploy or rollback while an
+experiment splits the page keeps serving the experiment's two arms and
+leaves its goals as they are (new manifest goals are added); the deployed
+version serves when the experiment ends, and its goal changes apply at the
+next deploy after that.
+
 ## Which local format am I in?
 
 Inspect the marker under `.apex/`: `experiment-filesystem.json` means the
-folder belongs to `apex experiments pull/plan/apply`, while `session.json`
+folder belongs to `apex experiments pull/plan/apply`, `landing-page.json` means
+an `apex landing-pages` checkout, while `session.json`
 means it is an `apex workspace checkout/status/publish` workspace. Keep the two
 formats in different folders; when the wrong command is run, Apex points to the
 matching status command.