fimo 2.10.2-staging.1 → 2.10.2-staging.3
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-cli/SKILL.md +1 -1
- package/assets/skills/fimo-cli/references/content.md +1 -1
- package/assets/skills/fimo-studio/SKILL.md +1 -1
- package/dist/cli/bundle.json +1 -1
- package/dist/cli/index.js +14 -14
- package/package.json +8 -8
- package/templates/astro/package.json +3 -3
- package/templates/nextjs/package.json +4 -4
- package/templates/react-router/package.json +5 -5
- package/templates/sveltekit/package.json +3 -3
- package/templates/vite/package.json +5 -5
|
@@ -64,7 +64,7 @@ Load a reference with `fimo skills get fimo-cli --ref <name>`. "+ fimo-code `<re
|
|
|
64
64
|
- Restore points and recovery → `history`
|
|
65
65
|
- Environment variables and secrets → `project-vars-and-secrets`
|
|
66
66
|
- Send form submissions, publishes, or other events to Slack, Resend, GitHub, Zapier, or a URL → `webhooks`
|
|
67
|
-
- Connected
|
|
67
|
+
- Connected integrations, Search Console, Google Analytics, MCP servers → `integrations`; Firecrawl web research → also `integrations/firecrawl`
|
|
68
68
|
- Visitors, page views, top pages, chart annotations → `analytics`
|
|
69
69
|
- Site URL: rename the free `*.fimo.site` slug (`fimo domains rename-default <slug>`), add a domain the user owns, buy a domain → `domains`
|
|
70
70
|
- Invite people. After the first deploy, suggest it when other people work on the site → `invite`
|
|
@@ -31,7 +31,7 @@ fimo singles update <Type> [--locale es] (--body '<json>' | --file <path> | --st
|
|
|
31
31
|
```
|
|
32
32
|
|
|
33
33
|
- `--body` is always a `{"data":{...}}` envelope, also for `singles update`. Put `slug` inside `data`.
|
|
34
|
-
- `entries create` and `entries update`
|
|
34
|
+
- `entries create` and `entries update` require exactly one of `--body '<json>'`, `--file <path>`, or `--stdin`. Files and stdin use the same `{"data":{...}}` envelope.
|
|
35
35
|
- Before you write a body, load fimo-code `content/richtext`. Rich text is Tiptap JSON (`{"type":"doc","content":[...]}`), a reference is `{"id":"<id>"}`, and media has its own shape.
|
|
36
36
|
- `get`, `update`, and `delete` take the `id` (a UUID) that `create` and `list` return. Never pass a slug as the id.
|
|
37
37
|
- `update` and `singles update` change only the top-level fields in `data`; each field you send replaces its old value. The first `singles update` for a locale creates the Single, so it needs every required field.
|
|
@@ -77,7 +77,7 @@ Read the relevant reference file when the user's question matches a topic.
|
|
|
77
77
|
| Adding images | Media Library, AI Chat, Edit Mode |
|
|
78
78
|
| Content/CMS | AI Chat, Media Library |
|
|
79
79
|
| Webhooks | Site secrets, Forms, Publishing |
|
|
80
|
-
|
|
|
80
|
+
| Integrations | AI Chat, Site secrets |
|
|
81
81
|
| Schedules | Site secrets, Environments |
|
|
82
82
|
| API keys | Variables (private), Site secrets |
|
|
83
83
|
| Visual changes | Edit Mode (CMS content), AI Chat (layout, styling, and code changes) |
|