fimo 0.21.0-staging.3 → 0.21.0-staging.4
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/assets/skills/fimo-code/references/content/schema.md +23 -0
- package/assets/skills/fimo-studio/references/cms.md +2 -0
- package/dist/cli/bundle.json +1 -1
- package/dist/cli/index.js +11 -11
- package/dist/scripts/sync-schemas.js +3 -0
- package/dist/scripts/validate-schemas.js +63 -2
- package/package.json +1 -1
- package/templates/react-router/package.json +1 -1
|
@@ -23,6 +23,29 @@ Write one schema per `src/schemas/<Uid>.json`. The PascalCase filename must matc
|
|
|
23
23
|
|
|
24
24
|
Required root keys: `uid`, `name`, and `fields`.
|
|
25
25
|
|
|
26
|
+
## Group fields in Studio
|
|
27
|
+
|
|
28
|
+
Use optional top-level `groups` when an entry has meaningful editing areas, such as Overview, Tickets, SEO, or Scheduling. They work best for longer forms where editors regularly work on one area at a time. Usually skip groups for short forms, one-field groups, or vague buckets such as General and Other. Prefer two to five groups organized around editor tasks. This is guidance, not a schema limit.
|
|
29
|
+
|
|
30
|
+
Assign each top-level field with `group`; one field may appear in more than one group. This changes only the Studio layout, not stored content, generated types, validation, permissions, or what agents can edit.
|
|
31
|
+
|
|
32
|
+
```json
|
|
33
|
+
{
|
|
34
|
+
"uid": "Event",
|
|
35
|
+
"name": "Events",
|
|
36
|
+
"groups": [
|
|
37
|
+
{ "id": "overview", "label": "Overview", "default": true },
|
|
38
|
+
{ "id": "tickets", "label": "Tickets" }
|
|
39
|
+
],
|
|
40
|
+
"fields": {
|
|
41
|
+
"title": { "type": "string", "group": "overview" },
|
|
42
|
+
"price": { "type": "number", "group": ["overview", "tickets"] }
|
|
43
|
+
}
|
|
44
|
+
}
|
|
45
|
+
```
|
|
46
|
+
|
|
47
|
+
Group IDs must be unique, at most one group may be the default, and memberships must reference a declared group. Only top-level fields can be grouped; fields inside blocks cannot declare `group`.
|
|
48
|
+
|
|
26
49
|
Use `"isSingleton": true` whenever the site has exactly one logical document: a homepage, site settings, an About page, or one campaign landing page. Do not turn it into a one-entry collection just to seed content; keep the Single and load `fimo-cli/references/content.md` for the `fimo singles update` workflow.
|
|
27
50
|
|
|
28
51
|
```json
|
|
@@ -83,6 +83,8 @@ Press **Alt+J** to move to the next entry or **Alt+K** to move to the previous o
|
|
|
83
83
|
|
|
84
84
|
If a field is invalid, the editor keeps the change unsaved and pins a status bar below the header. Choose **Review issues** to jump to the first invalid field, then **Next issue** to move through the remaining fields. Collapsed blocks open automatically. Once every issue is fixed, the editor confirms that all fields are valid and resumes saving.
|
|
85
85
|
|
|
86
|
+
Longer entry forms may have quiet field-group tabs below the header. Choose a group to focus on that part of the entry, or choose **All fields** for the complete form. Studio remembers the selected group for that content type during the browser session, and copied entry links preserve the active group. If validation finds a problem elsewhere, **Review issues** opens All fields before focusing it. Groups only change the editor view; they do not hide content from the API or restrict what the AI can edit.
|
|
87
|
+
|
|
86
88
|
A field labelled with a padlocked globe is shared across languages: it holds one value for the whole entry, so editing it in any language changes it in all of them. Fields without that marker are per language and only affect the language you are editing. Hover the icon for the same explanation in context.
|
|
87
89
|
|
|
88
90
|
## Editing Text
|