fimo 2.12.0 → 2.14.0
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.studio.md +1 -1
- package/assets/skills/fimo-cli/references/domains.md +1 -1
- package/assets/skills/fimo-cli/references/preview.md +7 -0
- package/assets/skills/fimo-code/references/content/richtext.md +2 -0
- package/assets/skills/fimo-code/references/frameworks/seo-head.md +3 -2
- package/assets/skills/fimo-studio/SKILL.md +25 -24
- package/assets/skills/fimo-studio/references/ai-chat/default-agents.md +1 -1
- package/assets/skills/fimo-studio/references/ai-chat.md +2 -1
- package/assets/skills/fimo-studio/references/billing-and-credits.md +1 -1
- package/assets/skills/fimo-studio/references/code-sync.md +19 -0
- package/dist/cli/bundle.json +2 -2
- package/dist/cli/index.js +21 -20
- package/dist/runtime/seo/resolver.d.ts +4 -3
- package/dist/runtime/seo/resolver.js +7 -3
- 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
|
@@ -29,7 +29,7 @@ Load a reference with `skillLoad` (`fimo-cli`, reference `<name>`). "+ fimo-code
|
|
|
29
29
|
- Generate or edit an image or video with AI → `media` (+ fimo-code `assets` to show it on the site)
|
|
30
30
|
- Labels, static copy, missing `t()` values → `labels` + fimo-code `labels`
|
|
31
31
|
- Locales → `locales` + fimo-code `locales`
|
|
32
|
-
- Preview URL → `preview`;
|
|
32
|
+
- Current Branch or main Preview URL → `preview`; failed builds and logs → `deploy`
|
|
33
33
|
- Redirects, security headers, clean URLs, trailing slash → `hosting`
|
|
34
34
|
- Broken links, SEO, alt text, accessibility, Web Vitals, console errors in a browser → `site-checks`
|
|
35
35
|
- Restore points → `history`
|
|
@@ -46,7 +46,7 @@ fimo domains remove <hostname> --yes
|
|
|
46
46
|
- `add` returns the DNS records (usually a CNAME and a TXT) that the user sets at their registrar; with `--json` they are in the domain record. Give them to the user exactly.
|
|
47
47
|
- After the user sets DNS, run `refresh` once; it polls until SSL is active or the wait ends (`--no-wait` prints one status). Read the returned status: the end of a wait does not prove the domain works. Do not run `refresh` in a loop. DNS can take from minutes to 48 hours.
|
|
48
48
|
- In an interactive setup, omit `--wait` on `add` so the user gets the records at once. In CI, `--wait` polls until the domain is verified or the wait ends.
|
|
49
|
-
- The primary domain is the canonical host of the published site. Fimo picks the oldest serving domain until the user chooses one with `primary`; the domain must be active with its certificate issued, else `DOMAIN_NOT_SERVING`. The canonical links change only on the next publish, so tell the user to publish again.
|
|
49
|
+
- The primary domain is the canonical host of the published site. Fimo picks the oldest serving domain until the user chooses one with `primary`; the domain must be active with its certificate issued, else `DOMAIN_NOT_SERVING`. The canonical links change only on the next publish, so tell the user to publish again. Change the site's address this way. A `seo.url` in `.fimo/config.json` overrides the primary domain and stops the site from following it: set it only when the user asks for an address Fimo does not serve, such as one behind their own proxy, and say that a later primary change will not move it.
|
|
50
50
|
- Each custom domain serves the site or redirects to another domain of the same site. `redirect` defaults to 307 (temporary); use 308 or 301 only when the user says the move is permanent. `list` shows each destination (`-> 308 www.acme.com` or `serves`). The target must serve and have its certificate issued, and redirects never chain: a refusal comes back with its code (`REDIRECT_TARGET_REDIRECTS`, `REDIRECT_SOURCE_IS_TARGET`, `REDIRECT_TARGET_NOT_ACTIVE`, `REDIRECT_TARGET_NOT_IN_PROJECT`, `INVALID_REDIRECT_STATUS`), and `add --redirect-www` gets `REDIRECT_TARGET_REDIRECTS` when the site's `www` already redirects elsewhere. Tell the user what it says; never point other domains elsewhere on your own.
|
|
51
51
|
- `remove` also removes every domain that redirects to the one removed. Run it once without `--yes`: in a run without prompts it refuses with `NON_INTERACTIVE_REFUSAL`, and its hint names those domains. Show that list to the user, and pass `--yes` only after they agree to remove them all.
|
|
52
52
|
- A redirect on the primary domain, `serve` on a domain that becomes primary, or removing the primary domain moves the primary domain; the result's hint says so. Tell the user to publish again so canonical links use it.
|
|
@@ -2,6 +2,10 @@
|
|
|
2
2
|
|
|
3
3
|
Use `fimo preview url` to get the current Branch's hosted preview without committing or pushing.
|
|
4
4
|
|
|
5
|
+
In Studio, unflagged `preview url` stays on the task or tab Branch. Only `preview url --branch main` or
|
|
6
|
+
`preview url --branch=main` may select another Branch, with one selector per call. Local CLI use can select any
|
|
7
|
+
accessible Branch, as in the `feat/redesign` example below.
|
|
8
|
+
|
|
5
9
|
```bash
|
|
6
10
|
fimo preview url
|
|
7
11
|
fimo --branch feat/redesign preview url
|
|
@@ -11,6 +15,9 @@ curl -L "$(fimo preview url)"
|
|
|
11
15
|
|
|
12
16
|
The command returns the hosted deployment URL in every output mode: every live Branch except production owns a hosted build.
|
|
13
17
|
|
|
18
|
+
Main's Preview can contain unpublished changes. For what visitors receive, use the published address from
|
|
19
|
+
`domains list` and verify it answers.
|
|
20
|
+
|
|
14
21
|
If the current generation is queued or building, the command waits up to five minutes, polling with a backoff. It stops at once — without waiting — on a state waiting cannot change: a build that failed, and a Branch with no hosted preview (production, or a Branch nothing has changed yet). Every failure returns `PREVIEW_URL_FAILED`; read `error.message` for which one it was and `error.hint` for the next step. Only the timeout is worth retrying.
|
|
15
22
|
|
|
16
23
|
JSON output contains only the Branch identity and hosted URL:
|
|
@@ -24,6 +24,8 @@ Nodes: `doc`, `paragraph`, `heading`, `bulletList`, `orderedList`, `listItem`, `
|
|
|
24
24
|
|
|
25
25
|
Marks: `bold`, `italic`, `underline`, `strike`, `code`, and `link`.
|
|
26
26
|
|
|
27
|
+
Link to a page of the same site by its path (`/pricing`), even when older content uses full addresses. A full address always opens the published site: from a draft or preview it leaves what the reader is reviewing, it cannot reach a page that is not published yet, and it breaks when the primary domain changes. Use a full address only for another site.
|
|
28
|
+
|
|
27
29
|
Use semantic nodes instead of flattening long content into paragraphs. Render the returned value with the framework's `<RichText>` primitive so source metadata survives.
|
|
28
30
|
|
|
29
31
|
Richtext and other API values may carry class-backed tracking metadata. Values
|
|
@@ -57,8 +57,9 @@ explicit `undefined` in a spread removes a field; use conditional spreads to
|
|
|
57
57
|
retain defaults for missing optional overrides. Resolve once, then compose;
|
|
58
58
|
do not resolve again after applying policy.
|
|
59
59
|
|
|
60
|
-
A resolved `seo.url` is the site's address:
|
|
61
|
-
set, otherwise the
|
|
60
|
+
A resolved `seo.url` is the site's address: `seo.url` in `.fimo/config.json`
|
|
61
|
+
when the owner set it, otherwise the platform's `FIMO_SITE_URL` (the primary
|
|
62
|
+
domain, else the built-in address).
|
|
62
63
|
Read it from the resolved SEO, not from the imported config.
|
|
63
64
|
|
|
64
65
|
Pass a final absolute canonical URL from the app's production URL policy.
|
|
@@ -43,30 +43,31 @@ When a reference says "open X", X can be inside **More** on a narrow window.
|
|
|
43
43
|
|
|
44
44
|
Read the relevant reference file when the user's question matches a topic.
|
|
45
45
|
|
|
46
|
-
| Topic | Reference | When to read
|
|
47
|
-
| ------------------------ | --------------------------------------- |
|
|
48
|
-
| Command Palette | references/command-palette.md | "What can I open with Cmd+K?", "Quick actions"
|
|
49
|
-
| Publish & Deploy | references/publish-and-deploy.md | "How do I publish?", "How do I make my site live?"
|
|
50
|
-
| Analytics | references/analytics.md | "Is tracking working?", "Why are analytics empty?"
|
|
51
|
-
| Custom Domains | references/custom-domains.md | "How do I use my own domain?", "DNS setup"
|
|
52
|
-
| Content Management (CMS) | references/cms.md | "How does the CMS work?", "How do I add blog posts?"
|
|
53
|
-
| Media Library | references/media-library.md | "How do I upload images?", "Where are my files?"
|
|
54
|
-
| AI Chat | references/ai-chat.md | "What can the AI do?", "How do I give context?"
|
|
55
|
-
| Agents | references/ai-chat/agents.md | "Which plan has which agents?", "New agent", "Why is my agent paused?"
|
|
56
|
-
| Default agents | references/ai-chat/default-agents.md | "What does the SEO agent check?", "Which routines run on Monday?"
|
|
57
|
-
| Routines | references/ai-chat/routines.md | "When does a routine run?", "Routines paused", "Watch a price page"
|
|
58
|
-
| Site Knowledge | references/knowledge.md | "Set brand guidance", "Website goals", "Draft knowledge from the site"
|
|
59
|
-
| SEO Settings | references/seo-settings.md | "How do I set up SEO?", "Favicon, title, share image"
|
|
60
|
-
| Variables & Secrets | references/variables-and-secrets.md | "Where do I put an API key?", "Public or private variable?"
|
|
61
|
-
| Schedules | references/schedules.md | "Recurring commands", "Run history", "Run now"
|
|
62
|
-
| Webhooks | references/webhooks.md | "React to forms", "Send events to another service"
|
|
63
|
-
|
|
|
64
|
-
|
|
|
65
|
-
|
|
|
66
|
-
|
|
|
67
|
-
|
|
|
68
|
-
|
|
|
69
|
-
|
|
|
46
|
+
| Topic | Reference | When to read |
|
|
47
|
+
| ------------------------ | --------------------------------------- | ------------------------------------------------------------------------ |
|
|
48
|
+
| Command Palette | references/command-palette.md | "What can I open with Cmd+K?", "Quick actions" |
|
|
49
|
+
| Publish & Deploy | references/publish-and-deploy.md | "How do I publish?", "How do I make my site live?" |
|
|
50
|
+
| Analytics | references/analytics.md | "Is tracking working?", "Why are analytics empty?" |
|
|
51
|
+
| Custom Domains | references/custom-domains.md | "How do I use my own domain?", "DNS setup" |
|
|
52
|
+
| Content Management (CMS) | references/cms.md | "How does the CMS work?", "How do I add blog posts?" |
|
|
53
|
+
| Media Library | references/media-library.md | "How do I upload images?", "Where are my files?" |
|
|
54
|
+
| AI Chat | references/ai-chat.md | "What can the AI do?", "How do I give context?" |
|
|
55
|
+
| Agents | references/ai-chat/agents.md | "Which plan has which agents?", "New agent", "Why is my agent paused?" |
|
|
56
|
+
| Default agents | references/ai-chat/default-agents.md | "What does the SEO agent check?", "Which routines run on Monday?" |
|
|
57
|
+
| Routines | references/ai-chat/routines.md | "When does a routine run?", "Routines paused", "Watch a price page" |
|
|
58
|
+
| Site Knowledge | references/knowledge.md | "Set brand guidance", "Website goals", "Draft knowledge from the site" |
|
|
59
|
+
| SEO Settings | references/seo-settings.md | "How do I set up SEO?", "Favicon, title, share image" |
|
|
60
|
+
| Variables & Secrets | references/variables-and-secrets.md | "Where do I put an API key?", "Public or private variable?" |
|
|
61
|
+
| Schedules | references/schedules.md | "Recurring commands", "Run history", "Run now" |
|
|
62
|
+
| Webhooks | references/webhooks.md | "React to forms", "Send events to another service" |
|
|
63
|
+
| Code Sync | references/code-sync.md | "Sync code to GitHub", "Connect a repository", "Resolve a sync conflict" |
|
|
64
|
+
| Integrations | references/integrations.md | "Connect a service", "Add an MCP server", "Slack channels" |
|
|
65
|
+
| Preview & Responsive | references/preview-and-responsive.md | "How does it look on mobile?", "How do I test sizes?" |
|
|
66
|
+
| Visual Editing | references/visual-editing.md | "Can I edit visually?", "How do I change colors?" |
|
|
67
|
+
| Version History | references/version-history.md | "How do I undo?", "How do I go back?" |
|
|
68
|
+
| Sharing & Collaboration | references/sharing-and-collaboration.md | "How do I share?", "How do I invite someone?" |
|
|
69
|
+
| Site Creation | references/project-creation.md | "How do I start a new site?" |
|
|
70
|
+
| Billing & Credits | references/billing-and-credits.md | "What are credits?", "How do I upgrade?", "How do referrals work?" |
|
|
70
71
|
|
|
71
72
|
## Cross-feature references
|
|
72
73
|
|
|
@@ -15,7 +15,7 @@ Plans, setup and the rules every default agent follows are in `ai-chat/agents`.
|
|
|
15
15
|
|
|
16
16
|
The Monday runs of Technical SEO, Meta tags and Internal linking read every page of main's hosted preview, for what no single change shows (pages out of the sitemap, shared titles, title shape, orphan and deep pages). A run that a change started checks only the pages it touches, its first run too.
|
|
17
17
|
|
|
18
|
-
Alone, it points a link at a new address only after it checked that the address shows the same content in the same language, and otherwise removes a dead link and keeps its words; it adds a link on words the text already uses to name another page, keeps the 8 most useful links on a page with too many, shortens a title or description Google cuts from the same words (in a field only search reads, added to the type when needed, when the title is also the page's heading), sets the public address when the canonicals and sitemap agree on it,
|
|
18
|
+
Alone, it points a link at a new address only after it checked that the address shows the same content in the same language, and otherwise removes a dead link and keeps its words; it adds a link on words the text already uses to name another page, keeps the 8 most useful links on a page with too many, shortens a title or description Google cuts from the same words (in a field only search reads, added to the type when needed, when the title is also the page's heading), sets the public address when the canonicals and sitemap agree on it, adds a 301 from an old address Google still shows once one live page clearly covers the same subject (none: the address stays gone; several: it asks), and gives a page whose address says nothing (`/blog/blog-post-9a32c70f0f`) a readable one from its title, with a 301 from the old one. A title, description, heading or link that any agent or person changed is not changed again for 8 weeks (Google needs 8 to 12 weeks to show the effect), unless it is a fault, and words a person rewrote after an agent changed them stay. Keyword research never changes the site alone.
|
|
19
19
|
|
|
20
20
|
## GEO (4 routines)
|
|
21
21
|
|
|
@@ -52,7 +52,8 @@ Hover over a message. Your messages have **Copy** and **Edit** (change and resen
|
|
|
52
52
|
## Proposals, reviews and merges
|
|
53
53
|
|
|
54
54
|
- Ask chat to keep alternatives as named proposals. Open the Branch picker and choose one under **Proposals** to preview it; each has its own changes. Internal work stays hidden there, even when saved or kept longer. Exploring or merging one keeps the others unless you ask to discard them. Delete a proposal from the Branch picker. Pull is not available for a proposal: ask chat to update it. **New Branch** starts from the proposal's upstream; merge the proposal first to branch from its changes.
|
|
55
|
-
- A
|
|
55
|
+
- A request is made at once. When a decision is still yours, such as ideas you asked to pick from or a change a routine found, chat proposes instead: a block with one line per proposal (spinner: still being written, arrow: ready, check: approved, crossed out: discarded). A line opens the proposal beside the chat, or as its own page on a phone: new or changed content as a page of text you can edit (your edits stay in the proposal, nothing is live), and a change to how a page looks or works as that page's preview. **Approve** sends `Approve "<title>"` to the chat, and the agent writes it to your preview, or first makes a change you asked for there; if someone changed the same field since, nothing is overwritten and the agent says what changed. **Discard** removes it at once.
|
|
56
|
+
- A session proposal saves the session's current work and makes that same session visible and durable. It shows in a strip above the message box (**View changes**, **Open preview**), and the conversation keeps a line with **View changes** where it was proposed. Opening it approves nothing. The Preview and Changes links, also in Slack or an agent report, open the Branch in Studio and need site access.
|
|
56
57
|
- Chat prepares changes separately and merges them into the environment you view; most merge automatically. If the site changed in the same place, a banner above the message box (**Your last changes need attention**) offers **Auto fix** (chat continues in the retained proposal, resolves the conflict and retries the merge; keep chatting has the same effect) and **Review manually**. Discarding leaves the environment unchanged and removes the proposal for good.
|
|
57
58
|
- **Merging does not publish the site.**
|
|
58
59
|
|
|
@@ -25,7 +25,7 @@ Open **Earn free credits** from the site header (or the site menu on mobile), th
|
|
|
25
25
|
- **Published** counts people who published their first site, not the number of sites they publish.
|
|
26
26
|
- **AI credits earned** shows inviter rewards already credited to you. It excludes your own bonus for joining through someone else's link; a publication can appear before its reward is credited.
|
|
27
27
|
|
|
28
|
-
Each signup uses one of the five referral slots.
|
|
28
|
+
Each signup uses one of the five referral slots. The reward unlocks when that person publishes a site at least a day after signing up, and is credited to the referrer's personal organization; publishing does not reopen a slot. Someone who joined through a referral can't refer others, so their dialog shows a notice instead of a link. The dialog shows signups used and how many people have not published yet. **Terms and Conditions** opens the program terms; **Close** dismisses the dialog.
|
|
29
29
|
|
|
30
30
|
## Buying More Credits
|
|
31
31
|
|
|
@@ -0,0 +1,19 @@
|
|
|
1
|
+
# Code Sync
|
|
2
|
+
|
|
3
|
+
Code Sync appears only when available for the organization. If access is disabled, connections and checkpoints are kept;
|
|
4
|
+
eligible syncs resume when access returns, while conflicts still need **Check and resume**.
|
|
5
|
+
|
|
6
|
+
In a site's **Settings**, open **Code Sync** under **Advanced**, then **Add connection** → **Connect GitHub**.
|
|
7
|
+
A site manager connects an account and selects a repository or creates one. New repositories default to private;
|
|
8
|
+
public requires an explicit choice. Each connection automatically syncs current and future persistent Fimo branches
|
|
9
|
+
under the same names. Temporary agent branches and internal deployment refs are excluded. A public repository exposes
|
|
10
|
+
all synced branches. Code and Git history are copied; content, media and databases are not.
|
|
11
|
+
|
|
12
|
+
An occupied branch or external changes block only that branch; healthy branches keep syncing. Fimo never overwrites
|
|
13
|
+
unknown history. For an initial collision, preserve the existing branch under another name before **Check and resume**.
|
|
14
|
+
For a previously synced branch, manually restore its acknowledged checkpoint, then **Check and resume**.
|
|
15
|
+
Source deletion preserves the external branch. Recreating a source branch requires a manual check.
|
|
16
|
+
Use **Check access** or **Reconnect** to repair provider access; this does not clear branch conflicts.
|
|
17
|
+
**Remove connection** stops future syncs after any accepted write finishes, preserving the external repository.
|
|
18
|
+
Re-adding the same repository to the same site restores its checkpoints after fresh authorization; conflicts remain blocked.
|
|
19
|
+
Remove all connections before transferring the site. Manage Code Sync in Studio; it does not expose integration tools.
|
package/dist/cli/bundle.json
CHANGED