fimo 0.7.0 → 0.8.0-staging.1

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

@@ -183,7 +183,7 @@ For `media` fields, prefer `source: "local"` with assets uploaded via `fimo asse
 After pre-build (or `fimo deploy`), each schema generates two files:
 
 - `src/schemas/{Uid}.types.ts` — pure TypeScript types such as `BlogPost`, `BlogPostInput`, `BlogPostQuery`, and `BlogPostResult`.
-- `src/schemas/{Uid}.ts` — runtime helpers, React Query hooks, default export, and re-exported public types.
+- `src/schemas/{Uid}.ts` — exposes runtime helpers, React Query hooks, and public types.
 
 Import from the public schema module, e.g. `import BlogPost from '@/schemas/BlogPost'` and `import type { BlogPostResult } from '@/schemas/BlogPost'`. Do not import from `.types.ts` directly in app code. There is no generated `src/schemas/index.ts` barrel.
 

package/assets/skills/fimo-studio/SKILL.md

@@ -5,10 +5,11 @@ description: >-
   Fimo Studio / the dashboard UI — never for CLI commands or code work.
   Triggers: "in Fimo Studio", "in the dashboard", "in the web app",
   "how do I X in the UI", or screenshots of the dashboard. Topics
-  covered: publishing from the dashboard, dashboard SEO/domain settings,
-  visual editing, version history UI, dashboard sharing/billing,
-  dashboard chat. Never describe UI locations, buttons, or panels from
-  memory — always read the relevant reference file first.
+  covered: dashboard content and CMS, publishing from the dashboard,
+  dashboard SEO/domain settings, visual editing, version history UI,
+  dashboard sharing/billing, and dashboard chat. Never describe UI
+  locations, buttons, or panels from memory — always read the relevant
+  reference file first.
 ---
 
 # Fimo Studio

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

@@ -1,23 +1,35 @@
 ## How the CMS Works
 
-The CMS is where you manage your site's content. It is built around two ideas:
+The CMS is where you manage your site's structured content. It separates content by how many documents each schema holds:
 
-- **Collections** are the structure or template for a type of content. Think of a collection as a blueprint. For example, a "Blog Post" collection defines that every blog post has a title, body, author, and cover image.
-- **Entries** are the actual pieces of content. Each individual blog post is an entry inside the Blog Post collection.
+- **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.
 
-If your site has a blog, a team page, and a FAQ, you would have three collections. Each one holds its own entries.
+Both use schemas to define their fields. The difference is whether you edit one document or manage a repeatable list.
 
 ## Browsing Your Content
 
 1. Click the **Content tab** (the database icon) in the top navigation bar.
-2. The left sidebar shows three sub-tabs: **Collections**, **Forms**, and **Labels & Text**.
-3. Collection cards display the collection name and how many entries it has.
-4. Click a collection to see a table of all its entries.
-5. Click any entry to open it for editing.
+2. Choose **Collections** or **Singles** in the left sidebar. **Forms** and **Labels & Text** follow them in the same list.
+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.
+
+Collection cards show their entry count. Single cards are labeled **Single** instead because they always represent one document.
+
+## Editing a Single
+
+1. Open **Content → Singles**.
+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.
 
 ## Navigating the Entry List
 
-When you open a collection, the entry list provides several tools:
+When you open a Collection, the entry list provides several tools:
 
 - **Search bar** at the top to filter entries by text content.
 - **Sort** via the sort dropdown button next to the search bar: sort by Creation date, Update date, or Slug, and toggle between Ascending and Descending. Clicking column headers does not sort.
@@ -26,11 +38,11 @@ When you open a collection, the entry list provides several tools:
 
 ## Creating a New Entry
 
-1. Navigate to the collection you want to add content to.
-2. Click the **+** (plus) icon button at the top of the collection (labeled **New entry** on hover). If the collection is empty, use the **Create entry** button in the center of the empty state instead.
+1. Navigate to the Collection you want to add content to.
+2. Click the **+** (plus) icon button at the top of the Collection (labeled **New entry** on hover). If the Collection is empty, use the **Create entry** button in the center of the empty state instead.
 3. Fill in the form fields (text, images, dates, whatever the collection defines).
 
-Changes save automatically as you fill in each field (the save is debounced), so there is no Save button. The save status appears in the top bar (Saving / Saved). The entry is now part of your collection. If the collection is wired to a page on your site, the new content shows up automatically.
+Changes save automatically as you fill in each field (the save is debounced), so there is no Save button. The save status appears in the top bar (Saving / Saved). The entry is now part of your Collection. If the Collection is wired to a page on your site, the new content shows up automatically.
 
 ## Editing an Entry
 
@@ -49,18 +61,22 @@ Need to update or remove several entries at once?
 4. For bulk edit, you select which field to update, then provide the new value for all selected entries.
 5. Confirm in the dialog that appears.
 
+Bulk operations are available for Collections, not Singles.
+
 ## Working with AI
 
 The AI chat can help you manage content without navigating through menus:
 
-- Ask the AI to **create a new content type** (for example, "Create a Testimonials collection with name, quote, and photo fields").
+- Ask the AI to **create a Single or Collection** (for example, "Create a Site settings Single" or "Create a Testimonials Collection with name, quote, and photo fields").
 - Ask it to **populate entries** (for example, "Add 5 sample blog posts about web design").
 - Use **@** in the chat to reference specific content when discussing changes.
 - Ask the AI to **wire content to a page** so entries display on your site automatically.
 
 ## Key Concepts
 
-- **Content appears automatically** if the collection is connected (wired) to a page on your site. You do not need to manually link each entry.
+- **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.
+- **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.
 - **Search and sort**: Use the search bar to filter entries and the sort dropdown to order them quickly.

package/dist/cli/bundle.json

@@ -1,7 +1,7 @@
 {
   "bundled": true,
   "bundler": "esbuild",
-  "bundledAt": "2026-07-21T11:42:21.521Z",
+  "bundledAt": "2026-07-22T13:43:06.930Z",
   "cliVersion": "0.7.0",
   "external": [
     "oxc-parser",