frontpage-host 0.1.3 → 0.1.4

package/AGENTS.md

@@ -92,6 +92,27 @@ Rules:
 7. Prefer reviewing the subdomain after push; only use `deploy wait` if you need to block until a build finishes.
 8. The **UI / canvas agent does not use this CLI** — it edits the live tip in-process. Only CLI checkouts need `pull`.
 
+## Site contract (Astro)
+
+Sites are Astro 6 + Tailwind v4. More detail: `frontpage help site-building` or https://frontpage.host/developers/site-building
+
+1. **Every page** wraps content in `<BaseLayout title="…" description="…">` (import from `src/layouts/BaseLayout.astro`).
+2. **`src/config/site.ts`** — keep `pages` (path registry) and `nav` in sync when adding/renaming/deleting page files. Tab title comes from BaseLayout, not the `pages` map label.
+3. **One file per URL** for similar page sets (services, guides, …). Do not default to `getStaticPaths()` over `src/data/*.ts`. Blog/news → `frontpage articles`, not a hand-rolled catalog.
+4. **No backends / databases / fake forms or checkout.** Real forms use `<form data-fp-form="slug">` + `frontpage modules`. Refuse or use modules for payments.
+5. **Tokens** in `src/config/tokens.ts` — keep required color/font/spacing/radii keys; style via CSS variables / token Tailwind. Setting a font token is not enough — apply `font-sans` / `font-serif` / `font-display`. No CLI font catalog yet; use existing tokens or `frontpage prompt`.
+6. **Shared chrome** — prefer `src/components/Header.astro` + `Footer.astro` (or `chrome: { managed: true }` in `site.ts`).
+7. **404** — customize `src/pages/404.astro` if needed; keep `frontpage:404` meta; never register `/404` in `nav`/`pages`.
+8. **Platform-owned paths** stay off-limits (BaseLayout overlay, module/extension shells, `package.json`, …). Customer layouts like `DocsLayout` / `GuideLayout` are OK.
+
+## Modules & articles
+
+- Forms: `data-fp-form` markup in pages + `frontpage modules` for enable/config. No submit JS / honeypot / `action`.
+- Articles: `frontpage articles …` for lifecycle; bodies via sync under `content/` or `articles content get|set`. Section landing is an owned `src/pages/<section>/index.astro`.
+- Migrate a folder into Articles: prefer `frontpage prompt "migrate … into articles"` — do not invent a mass delete+write migration.
+- Extensions: `frontpage extensions`; if LOCKED on plan, do not fake charts/etc.
+- Media in markup: `/__media/uploads/<slug>/…` from `frontpage media` (not raw blob URLs).
+
 ## Agent prompt loop
 
 ```bash
@@ -194,6 +215,7 @@ Safe default after finishing work: summarize what changed and give the staging U
 frontpage help
 frontpage help --json
 frontpage help sync
+frontpage help site-building
 frontpage help agent
 frontpage doctor --json
 ```

package/dist/completions/generate.js

@@ -14,7 +14,7 @@ _frontpage_completions() {
   fi
   local cmd="\${COMP_WORDS[1]}"
   case "\${cmd}" in
-    help) COMPREPLY=( $(compgen -W "\${cmds} quickstart auth sync agent content history isolation exit-codes" -- "\${cur}") ) ;;
+    help) COMPREPLY=( $(compgen -W "\${cmds} quickstart auth sync site-building agent content history isolation exit-codes" -- "\${cur}") ) ;;
     completion) COMPREPLY=( $(compgen -W "bash zsh fish" -- "\${cur}") ) ;;
     runs) COMPREPLY=( $(compgen -W "list current wait cancel retry get" -- "\${cur}") ) ;;
     deploy) COMPREPLY=( $(compgen -W "wait" -- "\${cur}") ) ;;

package/dist/registry.d.ts

@@ -14,6 +14,6 @@ export type CommandDef = {
     seeAlso?: string[];
 };
 export declare const COMMANDS: readonly CommandDef[];
-export declare const TOPIC_NAMES: readonly ["quickstart", "auth", "sync", "agent", "content", "history", "isolation", "exit-codes"];
+export declare const TOPIC_NAMES: readonly ["quickstart", "auth", "sync", "site-building", "agent", "content", "history", "isolation", "exit-codes"];
 export declare const TOPICS: Record<string, string>;
 export declare function findCommand(name: string): CommandDef | undefined;

package/dist/registry.js

@@ -7,8 +7,24 @@ export const COMMANDS = [
         name: "help",
         summary: "Show available commands",
         usage: "frontpage help [command|topic] [--json]",
-        topics: ["auth", "sync", "agent", "content", "history", "isolation", "exit-codes", "quickstart"],
-        examples: ["frontpage help", "frontpage help sync", "frontpage help push", "frontpage help --json"],
+        topics: [
+            "auth",
+            "sync",
+            "site-building",
+            "agent",
+            "content",
+            "history",
+            "isolation",
+            "exit-codes",
+            "quickstart",
+        ],
+        examples: [
+            "frontpage help",
+            "frontpage help sync",
+            "frontpage help site-building",
+            "frontpage help push",
+            "frontpage help --json",
+        ],
     },
     {
         name: "login",
@@ -291,6 +307,7 @@ export const TOPIC_NAMES = [
     "quickstart",
     "auth",
     "sync",
+    "site-building",
     "agent",
     "content",
     "history",
@@ -315,8 +332,8 @@ export const TOPICS = {
 
   Staging is the subdomain. There is no separate staging-deploy step for agents.
   Never publish/unpublish unless the user explicitly asks.
-  Agents: read AGENTS.md in the npm package; use --json for structured I/O.
-  More: frontpage help auth | sync | agent | content | history | isolation | exit-codes`,
+  Agents: read AGENTS.md + frontpage help site-building; use --json for structured I/O.
+  More: frontpage help auth | sync | site-building | agent | content | history | isolation | exit-codes`,
     auth: `Authentication
   1. Create a key in the Frontpage editor: profile menu → Developers
   2. frontpage login
@@ -353,6 +370,39 @@ export const TOPICS = {
   - No separate "deploy to staging" step for agents — review the subdomain after the build.
   - frontpage deploy wait only waits for an in-flight build; it is NOT go-live.
   - frontpage publish promotes staging → production (custom domain). Never publish unless asked.`,
+    "site-building": `Site building (Astro contract)
+  Stack: Astro 6 + Tailwind v4. Pages in src/pages/. Every page wraps <BaseLayout title description>.
+  Control files: src/config/tokens.ts (design tokens), src/config/site.ts (title, nav, pages map, seo).
+
+  Pages map:
+  - Add/rename/delete a page file ⇒ update pages (+ nav if needed) in the SAME change set.
+  - Real title/description live on <BaseLayout>, not as authority in the pages map.
+  - One discrete .astro file per URL for similar sets (services, guides…). Do NOT default to
+    getStaticPaths() over src/data/*.ts. Blog/news → frontpage articles.
+
+  Hard fences:
+  - No API routes, serverless backends, or databases.
+  - No fake lead forms / checkout / card fields — use data-fp-* modules + frontpage modules, or refuse.
+  - Platform-owned paths are not syncable (BaseLayout overlay, module/extension shells, package.json…).
+  - Customer layouts (DocsLayout, GuideLayout, …) are fine when site-owned.
+
+  Tokens & fonts:
+  - Keep required colors/fonts/spacing/radii keys; style via CSS variables / token Tailwind.
+  - Setting fonts.sans is not enough — apply font-sans / font-serif / font-display on elements.
+  - No frontpage fonts catalog command yet; read tokens.ts or frontpage prompt.
+
+  Chrome / SEO / 404:
+  - Prefer src/components/Header.astro + Footer.astro (or chrome: { managed: true } in site.ts).
+  - seo block in site.ts + frontpage seo get|set; customize 404.astro but keep frontpage:404 meta;
+    never put /404 in nav or pages. robots/sitemap are platform-managed.
+
+  Modules & articles (short):
+  - Forms: <form data-fp-form="slug"> with named inputs; no action/onsubmit/honeypot.
+  - Articles: frontpage articles …; migrate folders via frontpage prompt (don't invent mass delete+write).
+  - Media in markup: /__media/uploads/<slug>/… from frontpage media (not raw blob URLs).
+
+  Full guide: https://frontpage.host/developers/site-building
+  See also: frontpage help sync | content | AGENTS.md`,
     agent: `Agent + publish
   frontpage prompt "make the hero shorter"
   frontpage runs                 # latest + active
@@ -381,8 +431,12 @@ export const TOPICS = {
   frontpage settings get|set
   frontpage edit --path / --old "…" --new "…"
 
+  Real forms (file sync): <form data-fp-form="slug"> + named inputs — no action/onsubmit/honeypot.
+  Do not fake payments/checkout. LOCKED extensions → do not fake; say plan required.
+  Migrate pages → articles: prefer frontpage prompt "migrate …" over mass delete+write.
   edit uses click-edit (exact single occurrence), not push / gated-write.
   Module OAuth and secret values are not exposed via the CLI.
+  Site contract: frontpage help site-building · https://frontpage.host/developers/site-building
   Domains, billing, members, and site delete are out of v1.`,
     history: `History
   frontpage history [--limit 20] [--page 1]

package/llms.txt

@@ -3,7 +3,8 @@
 - Package: frontpage-host (npm). Binary: frontpage. Do NOT install npm package "frontpage".
 - Docs in this package: README.md, AGENTS.md (agent operating manual).
 - Introspect: frontpage help | frontpage help --json | frontpage help <topic|command>
-- Topics: quickstart, auth, sync, agent, content, history, isolation, exit-codes
+- Topics: quickstart, auth, sync, site-building, agent, content, history, isolation, exit-codes
+- Site building: frontpage help site-building — Astro pages map, BaseLayout, tokens, no backends/fake forms
 - Auth: mint fp_live_ key in Frontpage UI (Developers); frontpage login KEY or FRONTPAGE_API_KEY
 - Site id: subdomain only (frontpage use <subdomain>). Not custom domains.
 - Staging: https://<subdomain>.frontpage.host — push/prompt/edit update staging; no separate staging deploy step for agents

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "frontpage-host",
-  "version": "0.1.3",
+  "version": "0.1.4",
   "description": "Frontpage CLI — manage your site from the terminal",
   "type": "module",
   "bin": {