frontpage-host 0.1.11 → 0.1.12

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/AGENTS.md CHANGED
@@ -101,7 +101,7 @@ Sites are Astro 6 + Tailwind v4. More detail: `frontpage help site-building` or
101
101
  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.
102
102
  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.
103
103
  4. **No backends / databases / fake forms or checkout.** Real forms use `<form data-fp-form="slug">` + `frontpage modules`. Refuse or use modules for payments.
104
- 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`. Browse fonts with `frontpage fonts`; set one token with `frontpage tokens set --group … --key … --value …` (CAS like push). Module how-tos: `frontpage modules docs <key>` / `frontpage extensions docs <key>`.
104
+ 5. **Tokens** in `src/config/tokens.ts` — keep required color/font/spacing/radii keys; style via CSS variables / token Tailwind. **Fonts load rule:** the build bundles catalog faces when the family string appears in `tokens.ts` and/or in a real CSS `font-family` / `fontFamily` / `font-['…']` context under `src/pages|components|styles` — not from prose alone. Preferred path: `frontpage fonts` → exact `value` → `frontpage tokens set --group fonts --key <role> --value "…"` → **APPLY** `font-sans` / `font-serif` / `font-mono` / `font-display` (or `var(--font-*)`) on elements. Inline catalog `font-family` accents can bundle after rebuild, but brand roles still prefer tokens + utilities. Off-catalog families silently fall back to system fonts (push may warn). Module how-tos: `frontpage modules docs <key>` / `frontpage extensions docs <key>`.
105
105
  6. **Shared chrome** — prefer `src/components/Header.astro` + `Footer.astro` (or `chrome: { managed: true }` in `site.ts`).
106
106
  7. **404** — customize `src/pages/404.astro` if needed; keep `frontpage:404` meta; never register `/404` in `nav`/`pages`.
107
107
  8. **Platform-owned paths** stay off-limits (BaseLayout overlay, module/extension shells, `package.json`, …). Customer layouts like `DocsLayout` / `GuideLayout` are OK.
@@ -115,6 +115,7 @@ export async function runPush(args) {
115
115
  commitSha: data.commitSha,
116
116
  baseCommitSha: data.baseCommitSha,
117
117
  filesChanged: data.filesChanged,
118
+ ...(data.warnings?.length ? { warnings: data.warnings } : {}),
118
119
  };
119
120
  if (!wait) {
120
121
  if (isJson()) {
@@ -123,12 +124,16 @@ export async function runPush(args) {
123
124
  }
124
125
  if (!data.changed) {
125
126
  console.log("Nothing to commit (remote already matches).");
127
+ for (const w of data.warnings ?? [])
128
+ console.error(`Warning: ${w}`);
126
129
  return EXIT_OK;
127
130
  }
128
131
  console.log(`Pushed ${data.filesChanged.length} file(s) → ${data.commitSha}`);
129
132
  console.log("Updated .frontpage/state.json baseCommitSha");
130
133
  console.log("Note: module markup may auto-activate modules (same as the editor agent).");
131
134
  console.log("tokens.ts may be auto-repaired at commit if it would break the build.");
135
+ for (const w of data.warnings ?? [])
136
+ console.error(`Warning: ${w}`);
132
137
  return EXIT_OK;
133
138
  }
134
139
  // --wait: after push, wait for agent-run busy to clear (same statuses as deploy wait).
@@ -141,6 +146,8 @@ export async function runPush(args) {
141
146
  console.log(`Pushed ${data.filesChanged.length} file(s) → ${data.commitSha}`);
142
147
  console.log("Updated .frontpage/state.json baseCommitSha");
143
148
  }
149
+ for (const w of data.warnings ?? [])
150
+ console.error(`Warning: ${w}`);
144
151
  console.error("Waiting for agent run / deploy idle…");
145
152
  }
146
153
  const result = await waitForAgentIdle({
package/dist/registry.js CHANGED
@@ -168,7 +168,8 @@ export const COMMANDS = [
168
168
  "frontpage fonts --query Cinzel --json",
169
169
  ],
170
170
  flags: [
171
- "Use the exact `value` string in tokens.fonts.* (via frontpage tokens set or push)",
171
+ "Use the exact `value` string in tokens.fonts.* (via frontpage tokens set or push), then APPLY font-* utilities",
172
+ "Build bundles catalog faces from tokens.ts and/or CSS font-family contexts (not prose mentions)",
172
173
  "No --site required — catalog is account/platform scoped",
173
174
  ],
174
175
  },
@@ -517,8 +518,10 @@ export const TOPICS = {
517
518
 
518
519
  Tokens & fonts:
519
520
  - Keep required colors/fonts/spacing/radii keys; style via CSS variables / token Tailwind.
520
- - Setting fonts.sans is not enough — apply font-sans / font-serif / font-display on elements.
521
- - Browse fonts: frontpage fonts [--slot serif] [--query elegant] — use the exact value string.
521
+ - Load rule: catalog faces bundle when the family string is in tokens.ts and/or a real CSS font-family / fontFamily / font-['…'] context under src/pages|components|styles — not from prose alone.
522
+ - Preferred path: frontpage fonts → exact value → tokens set fonts.<role> → APPLY font-sans|serif|mono|display (or var(--font-*)).
523
+ - Inline catalog font-family accents can load after rebuild; brand roles still prefer tokens + utilities.
524
+ - Setting fonts.sans alone is not enough — apply the utility on elements.
522
525
  - Surgical token edit: frontpage tokens set --group fonts --key sans --value "…" (CAS like push).
523
526
 
524
527
  Chrome / SEO / 404:
package/llms.txt CHANGED
@@ -5,7 +5,7 @@
5
5
  - Introspect: frontpage help | frontpage help --json | frontpage help <topic|command>
6
6
  - Topics: quickstart, auth, sync, site-building, agent, content, history, isolation, exit-codes
7
7
  - Site building: frontpage help site-building — Astro pages map, BaseLayout, tokens, no backends/fake forms
8
- - Fonts: frontpage fonts [--slot] [--query] — use exact value; tokens: frontpage tokens set --group --key --value (CAS)
8
+ - Fonts: frontpage fonts [--slot] [--query] → exact value → tokens set fonts.<role> → APPLY font-sans|serif|mono|display. Build bundles catalog faces from tokens.ts and/or CSS font-family contexts (not prose). Inline-only without tokens works for catalog faces after rebuild; prefer tokens+utilities for brand roles.
9
9
  - Module/extension docs: frontpage modules docs <key> | frontpage extensions docs <key>
10
10
  - Search flags: --regex --case-sensitive --whole-word --files-only --context-lines --max-results
11
11
  - Modules setup: frontpage modules request-setup <key> --reason "…" (owner status bar; CLI cannot show it)
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "frontpage-host",
3
- "version": "0.1.11",
3
+ "version": "0.1.12",
4
4
  "description": "Frontpage CLI — manage your site from the terminal",
5
5
  "type": "module",
6
6
  "bin": {