fimo 0.10.1-staging.1 → 0.10.1-staging.3

package/assets/skills/fimo-cli/references/content.md

@@ -1,17 +1,17 @@
-# Content workflow (schemas + entries)
+# Content workflow (schemas + Singles + entries)
 
 > **Run via `npx fimo@latest <command>`** — always the latest CLI, no install needed.
 
 > For the JSON shape, field types, Tiptap node spec, slug rules, and generated React Query hooks — these are package surface (version-locked to the project's `fimo`). See **`fimo/references/content.md`**.
 
-This file covers the **CLI workflow** for content. Use it when the user wants to add a content type (blog, products, pages) or create/manage entries.
+This file covers the **CLI workflow** for content. Use it when the user wants to add a content type (blog, products, pages) or manage Singles and entries.
 
 ## Flow
 
 1. Write `src/schemas/{Uid}.json` — PascalCase filename (e.g. `BlogPost.json`). For the JSON shape and field types, load `fimo/references/content.md`.
 2. Run `fimo schemas push {Uid}`. It generates `src/schemas/{Uid}.types.ts` and `src/schemas/{Uid}.ts`, then registers the schema with Fimo. It does not run whole-project validation.
 3. App code imports the generated client from `@/schemas/{Uid}`, not from `.types.ts` directly. See `fimo/references/content.md` for the hook API.
-4. Seed entries via `fimo entries create`. Generate cover images first with `fimo image generate` if needed (see `media.md` / `assets.md`).
+4. Seed collections via `fimo entries create`, or update one-off content via `fimo singles update`. Generate cover images first with `fimo image generate` if needed (see `media.md` / `assets.md`).
 5. Write React pages that import from `@/schemas/{Uid}` and render with `fimo/ui` components.
 
 Steps 1, 3, and 5 reference the `fimo-code` skill (`npx fimo@latest skills get fimo-code`) for shape and React API. Steps 2 and 4 are CLI commands documented here.
@@ -34,7 +34,26 @@ The command is `fimo schemas` (plural). There is no singular `fimo schema` alias
 
 All commands accept `-C, --cwd <dir>` to point at a different project directory.
 
-Schema transitions are automatic. Adding optional fields and changing labels preserve content. A new required field backfills its `default` only where existing values need it; the push fails safely when no default can satisfy existing content. Removing a nested field or block variant removes only those values. `string` and `text` preserve values in both directions. Other primitive changes convert safe values and reject unsafe ones without changing the schema or entries. Lowering block `max` trims from the end; raising `min` fills from the blocks `default` templates. A reference target change clears its connections. Use repeatable `--rename old.path=new.path` arguments when a field moved by name so the one-time migration preserves its values; the operation is not stored in schema JSON. Collection-to-singleton removes that type's entries and cleans inbound references; singleton-to-collection preserves its entry. Run `fimo validate` after pushing.
+Schema transitions are automatic. Adding optional fields and changing labels preserve content. A new required field backfills its `default` only where existing values need it; the push fails safely when no default can satisfy existing content. Removing a nested field or block variant removes only those values. `string` and `text` preserve values in both directions. Other primitive changes convert safe values and reject unsafe ones without changing the schema or entries. Lowering block `max` trims from the end; raising `min` fills from the blocks `default` templates. A reference target change clears its connections. Use repeatable `--rename old.path=new.path` arguments when a field moved by name so the one-time migration preserves its values; the operation is not stored in schema JSON. Collection-to-Single removes that type's entries and cleans inbound references; Single-to-collection preserves its entry. Run `fimo validate` after pushing.
+
+## Singles CLI commands
+
+Use Singles for one-off content such as a homepage, site settings, or an About story. The type name identifies the content, so these commands do not take an entry ID.
+
+```bash
+fimo singles get <TypeName> [--locale es] [--populate FIELDS]
+fimo singles update <TypeName> [--locale es] (--body '<json>' | --file <path> | --stdin)
+```
+
+The update payload uses the regular `{ "data": { ... } }` content body. Pass exactly one input source:
+
+```bash
+fimo singles update Story --body '{"data":{"title":"Our story"}}'
+fimo singles update Story --file story-body.json
+cat story-body.json | fimo singles update Story --stdin
+```
+
+The first update creates the Single's content; later updates change it. Use `--locale` for localized variants.
 
 ## Entries CLI commands
 
@@ -232,7 +251,7 @@ Rules:
 
 Turning an existing field shared is destructive when the languages currently hold different values. The push collapses each document to its default-locale value and discards the others; there is no prompt and no undo. Most documents already agree, so most collapses change nothing — but tell the user what will happen before adding `"i18n": false` to a field that already holds content, and check whether the languages differ if you are unsure.
 
-Use `"isSingleton": true` for a type with exactly one logical document. Generated singleton clients expose `get`/`update` and their React Query hooks, not collection create/remove APIs.
+Use `"isSingleton": true` for a Single with exactly one set of content. Generated Single clients expose `get`/`update` and their React Query hooks, not collection create/remove APIs.
 
 ## "Add a blog" recipe
 
@@ -261,4 +280,4 @@ fimo scripts sync-schemas      # regenerate src/schemas/*.types.ts and src/schem
 
 ## Non-interactive use
 
-All `fimo schemas *` and `fimo entries *` commands run non-interactively without extra flags (they don't prompt). Just pass the arguments documented above.
+All `fimo schemas *`, `fimo singles *`, and `fimo entries *` commands run non-interactively without extra flags (they don't prompt). Just pass the arguments documented above.

package/assets/skills/fimo-code/references/content.md

@@ -226,7 +226,7 @@ After editing schema JSON, run `fimo schemas push {Uid}` and then `fimo validate
 - Changing a reference target clears those connections. Renaming a relation field with the same target preserves them.
 - Preserve top-level or nested renames with repeatable one-time operations: `fimo schemas push Page --rename sections.hero.heading=sections.hero.title`. Renames are command intent, not schema JSON.
 - A many-to-one change or scalar/reference change clears only the changed field.
-- Collection-to-singleton removes that type's entries and cleans references to those documents.
+- Collection-to-Single removes that type's entries and cleans references to them.
 - Singleton-to-collection preserves the existing entry.
 - Blocks migrations are surgical: unaffected nested fields, block keys, and block order survive every supported change.
 

package/assets/skills/fimo-studio/references/cms.md

@@ -1,12 +1,12 @@
 ## How the CMS Works
 
-The CMS is where you manage your site's structured content. It separates content by how many documents each schema holds:
+The CMS is where you manage your site's structured content. It separates content by whether a schema is repeatable:
 
 - **Collections** hold multiple entries of the same kind, such as Blog posts, Team members, or Testimonials.
-- **Singles** hold one document, such as Site settings, a Homepage, or an About page.
-- **Entries** are the individual documents inside a collection.
+- **Singles** hold one set of content, such as Site settings, a Homepage, or an About page.
+- **Entries** are the individual records inside a Collection.
 
-Both use schemas to define their fields. The difference is whether you edit one document or manage a repeatable list.
+Both use schemas to define their fields. The difference is whether you edit one set of content or manage a repeatable list.
 
 ## Browsing Your Content
 
@@ -15,9 +15,9 @@ Both use schemas to define their fields. The difference is whether you edit one
 3. Hover over or focus the info icon beside any item for a short explanation.
 4. Each destination shows cards for the schemas in that group.
 5. Click a Collection to see its entries, then click an entry to edit it.
-6. Click a Single to open its one document directly.
+6. Click a Single to edit it directly.
 
-Collection cards show their entry count. Single cards are labeled **Single** instead because they always represent one document.
+Collection cards show their entry count. Single cards are labeled **Single** instead because they always represent one set of content.
 
 ## Editing a Single
 
@@ -25,7 +25,7 @@ Collection cards show their entry count. Single cards are labeled **Single** ins
 2. Select the Single you want, such as Site settings.
 3. Update its fields.
 
-Changes save automatically. A Single has no entry list, create action, bulk actions, or delete action because it always represents the same document.
+Changes save automatically. A Single has no entry list, create action, bulk actions, or delete action because it always represents the same set of content.
 
 ## Navigating the Entry List
 
@@ -96,7 +96,7 @@ The AI chat can help you manage content without navigating through menus:
 ## Key Concepts
 
 - **Collections** are best for repeatable content. Open one to search, sort, create, and manage its entries.
-- **Singles** are best for one-off documents. Open one and edit it directly.
+- **Singles** are best for one-off content. Open one and edit it directly.
 - **Content appears automatically** if its schema is connected (wired) to a page on your site. You do not need to manually link each entry.
 - **Forms tab**: View and manage form submissions collected from your site's forms.
 - **Labels & Text tab**: Edit your site's UI labels and static text strings as key-and-value rows. This is for your site's interface copy, not for translated copies of collection entries.

package/dist/build/vite/plugins/translations.js

@@ -9,6 +9,7 @@ const VIRTUAL_ID = 'virtual:translations';
 const RESOLVED_ID = '\0' + VIRTUAL_ID;
 const EVENT_RECONNECT_DELAY_MS = 2000;
 const FALLBACK_POLL_INTERVAL_MS = 30_000;
+const LABEL_FETCH_TIMEOUT_MS = 30_000;
 export default function translationsPlugin() {
     let rootDir = process.cwd();
     let bundle = {
@@ -423,7 +424,7 @@ export async function loadLabelBundle(rootDir) {
 async function fetchLabelDictionary(apiUrl, locale) {
     const url = new URL('/labels', apiUrl);
     url.searchParams.set('locale', locale);
-    const response = await fetchWithTimeout(url, 4000);
+    const response = await fetchWithTimeout(url, LABEL_FETCH_TIMEOUT_MS);
     if (!response.ok) {
         return { locale, labels: {}, updatedAt: null };
     }

package/dist/cli/bundle.json

@@ -1,7 +1,7 @@
 {
   "bundled": true,
   "bundler": "esbuild",
-  "bundledAt": "2026-07-27T14:30:59.819Z",
+  "bundledAt": "2026-07-28T15:26:45.077Z",
   "cliVersion": "0.10.0",
   "external": [
     "oxc-parser",