fimo 2.8.0-staging.8 → 2.8.0

package/assets/skills/fimo-studio/references/preview-and-responsive.md

@@ -1,8 +1,8 @@
 ## Using the Preview
 
-Click the **Preview** tab (the cursor/pointer icon) to see a live version of your site right inside the editor. You can also press **Alt+1** to jump to the preview tab.
+Open **Preview** (the cursor icon) or press **Alt+1** to see a live version of your site.
 
-- For Fimo-integrated sites, use the **route selector** dropdown at the top to navigate between different pages.
+- For Fimo-integrated sites, use the **route selector** dropdown at the top to navigate between different pages. The selected page is in the Studio address, so a reload or a shared link opens the same page and Branch.
 - Click the **refresh** button to reload the preview.
 - Click the **external link** icon to open your site in a new browser tab for a full-screen view.
 
@@ -10,7 +10,7 @@ The preview updates in real-time as you make changes, so you always see the late
 
 ## Responsive Testing
 
-Click the device-toolbar toggle (the monitor/smartphone icon) in the preview toolbar to open the device toolbar. This lets you see how your site looks on different screen sizes.
+On desktop, click the device-toolbar toggle (the monitor/smartphone icon) in the preview toolbar to open the device toolbar. This lets you see how your site looks on different screen sizes.
 
 ### Preset Devices
 
@@ -43,11 +43,6 @@ You may see different overlays depending on what is happening:
 
 ## Switching Workspaces
 
-The preview is one of several workspaces, and only one is shown at a time. Switch between them from the header navigation or with keyboard shortcuts:
-
-- **Alt+1** -- Preview
-- **Alt+2** -- Content (CMS)
-- **Alt+3** -- Assets
-- **Alt+5** -- Settings
+The preview is one of several workspaces, and only one is shown at a time. Switch from the header (or **More**), the bottom tabs on a phone, or the shortcuts in the Studio layout section of SKILL.md.
 
 When the Preview workspace is open, the visual editor can appear alongside it as a preview side panel.

package/assets/skills/fimo-studio/references/project-creation.md

@@ -1,16 +1,34 @@
 ## Create a Site
 
 1. Open **Sites** in Fimo Studio.
-2. Select **Create site**. If the button is unavailable, ask an organization admin for site creation permission.
-3. Enter a site name and select **Create**.
-4. Studio opens the new site's **Getting started** view.
+2. Select **Create site**. If the button is unavailable, ask an organization admin for site creation permission. When the organization is at its plan's site limit, Studio offers an upgrade instead.
+3. Enter the address of the website you already have. See [Start From a Website](#start-from-a-website).
 
-## Set Up the Site
+Someone who signs up without a website address lands on the same address page.
 
-The **For agents** tab is the default. Copy its prompt into your coding agent, or use one of the available agent shortcuts. The prompt identifies this as a newly created Fimo site, gives the agent the exact `fimo init` command, pins the selected CLI channel for every `fimo` command in the setup, and links to the coding-agent guide. Following that guide, the agent initializes the site and creates its first hosted preview with one plain preview deploy — unless you tell it not to deploy.
+To build with your own AI instead, select **Build with ChatGPT, Claude or a coding agent** below the address field. See [Build With Your Own AI](#build-with-your-own-ai).
+
+## Start From a Website
+
+1. Enter the website address. Fimo checks that it can read the site; if it cannot, it says why and nothing is created.
+2. Fimo creates the site, reads its homepage, works out what kind of site it is (business, non-profit, portfolio, hobby or personal site), and asks three questions that fit it in a short chat. It always starts by confirming what it understood. A business then keeps or adds its competitors and says how it stands out and how it is priced; other sites say what visitors should do and what to put forward, picking suggestions or typing their own. The answers are saved as the site's knowledge. If Fimo cannot read the site for the questions, select **Try again**.
+3. The report opens as soon as the last question is answered. It shows how ready the site is for search engines (SEO) and AI answers (GEO), with every check and how to fix it. Leaving and coming back resumes where you left off.
+4. Select **Copy & optimize my homepage**, at the top of the report. The site opens on its **Getting started** chat, where Fimo rebuilds the homepage with the report's problems fixed, then shows the scores before the rebuild and the checks it fixed. Only the homepage is rebuilt; links to other pages still go to the current site. Fimo covers the cost of the analysis, the questions and the first two rebuilds; credits are not used for them.
+
+Fimo does not rebuild a site that breaks its terms of use: the onboarding stops with a message to contact support.
+
+The report and the homepage copy Fimo read are deleted after 7 days.
+
+Once the homepage is rebuilt, a banner offers to bring over the other pages: copy a prompt into an AI, or book a call or write to the Fimo team. Website migration is in alpha, so review every result. Dismissing the banner hides it for good.
+
+## Build With Your Own AI
+
+The **Build with your own AI** dialog covers every starting point: existing code, a website to rebuild or redesign, or a new idea. Its prompt asks which one to start from.
+
+The **For agents** tab is the default. Copy its prompt into your coding agent, or open it in ChatGPT or Claude. The coding-agent prompt gives the agent the exact `fimo init` command, pins the selected CLI channel for every `fimo` command in the setup, and links to the coding-agent guide. Following that guide, the agent creates the site, builds it, and creates its first hosted preview with one plain preview deploy — unless you tell it not to deploy. In ChatGPT or Claude, the prompt uses the Fimo connector and its `fimo-site` skill instead of the CLI.
 
 Use **Manual setup** when you want to run the steps yourself. It provides the exact `fimo init` command, coding-agent shortcuts, and the final `fimo deploy` command.
 
-The first deploy completes onboarding and removes **Getting started** from the site. You can also select **Dismiss getting started** to hide it without deploying.
+Nothing is created until the AI creates the site; it then appears in Studio.
 
 Deploying creates a preview. It does not publish the site. Publishing is a separate action in Fimo Studio; see **Publish & Deploy** when the site is ready to go live.

package/assets/skills/fimo-studio/references/publish-and-deploy.md

@@ -6,7 +6,7 @@
 4. Once done, the panel shows a **Published** status, your live URL under a **Published site** heading, and a **Last published** date and time.
 5. Click the URL to open your live site in a new tab.
 
-> **Next step:** After publishing, consider inviting teammates to collaborate using the **Invite** button in the site header. You can grant them Full, Edit, Comment, or View access.
+> **Next step:** After publishing, consider inviting teammates to collaborate with **Invite**. You can grant Full access, Can edit, or Can view.
 
 ## Re-publishing After Changes
 
@@ -36,7 +36,7 @@ The header **Publish** button itself only shows the label "Publish" (or a spinne
 ## Key Concepts
 
 - **Saving vs. publishing**: Edits save automatically as you work (like a draft). Publishing sends those changes to your live site. Visitors only see published changes.
-- **SEO before publishing**: Go to Settings > SEO to set your page title, description, and share image before going live. After changing SEO settings, a yellow banner reminds you to publish to apply the changes.
+- **SEO before publishing**: Go to Settings > SEO to set your page title, description, and share image before going live. After changing SEO settings, a reminder asks you to publish to apply the changes.
 - **Custom domains**: If you are on a premium plan, set up a custom domain in Settings > Domains. Your domain works once your site is published.
 - **Unpublishing**: To take your site offline, go to Settings > General and click Unpublish. A confirmation dialog appears before proceeding.
 

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

@@ -4,9 +4,8 @@ Schedules run recurring site commands in one environment. Use the Studio surface
 
 ## Open schedules
 
-1. Open the site and choose **Settings**.
-2. Select **Schedules**.
-3. Choose the environment whose schedules you want to manage.
+1. Open **Settings** → **Advanced settings** → **Schedules**.
+2. Choose the environment whose schedules you want to manage.
 
 The list shows each schedule's name, cron, command, enabled state, and latest status. Usage and retention policy are shown for the selected environment.
 

package/assets/skills/fimo-studio/references/seo-settings.md

@@ -1,6 +1,6 @@
 ## Where to Find SEO Settings
 
-Open **Settings** (gear icon in the top toolbar) and select **SEO** from the settings menu on the left.
+Open **Settings** and select **SEO** in the settings menu.
 
 ## Setting Things Up
 
@@ -22,7 +22,7 @@ This is the image that shows up when someone shares your link on social media (F
 
 ## Saving and Publishing
 
-All SEO changes auto-save as you make them. However, a small amber reminder appears in the top-right corner: "Publish your website to apply your changes." Click Publish to push the changes to your live site.
+All SEO changes auto-save as you make them. A reminder above the fields asks you to publish. Click Publish to push the changes to your live site.
 
 Current templates include SEO wiring. For older Next.js, Astro or SvelteKit sites, ask the coding agent to update Fimo and connect these values to the app's existing SEO flow. Route-specific content must reach that flow too. Load the matching recipe: `fimo skills get fimo-code --ref frameworks/next`, `fimo skills get fimo-code --ref frameworks/astro`, or `fimo skills get fimo-code --ref frameworks/sveltekit`.
 

package/assets/skills/fimo-studio/references/sharing-and-collaboration.md

@@ -1,13 +1,12 @@
 ## Inviting People to Your Site
 
-1. Click the **Invite** button in the site header.
+1. Click **Invite** in the site header (on a phone, it is in the site menu).
 2. A sharing panel opens showing your current team. On desktop this appears as a popover; on mobile it opens as a drawer.
 3. Type the email address of the person you want to invite.
 4. Choose an access level for them:
    - **Full access** -- complete control over the site, including settings and member management.
    - **Can edit** -- can edit content and assets, and use the AI chat to change code. Cannot change site settings.
-   - **Can comment** -- can view the site and leave comments but cannot make edits.
-   - **Can view** -- can see the site but cannot make any changes or comments.
+   - **Can view** -- can see the site but cannot make changes.
 5. Click **Invite**.
 6. The invite appears in the member list marked **Pending invitation** until the person accepts it.
 

package/assets/skills/fimo-studio/references/visual-editing.md

@@ -16,7 +16,7 @@ Incomplete JSON drafts stay local. Leaving an empty JSON field saves `null` and
 
 ### References and Components
 
-Selecting a field rendered from a referenced entry edits that entry. For example, selecting an author's name opens the Author entry, not the Post relation that links to it. The header shows the relation path. Select the owning entry in that path to return to its complete form with the relation field focused; use that relation field to open, replace, or clear the linked entry.
+Selecting a field rendered from a referenced entry edits that entry. For example, selecting an author's name opens the Author entry, not the Post relation that links to it. Use the back arrow beside the entry title to return to its complete form with the relation field focused; use that relation field to open, replace, or clear the linked entry.
 
 Selecting a field inside a component focuses that nested field. Choose **All fields** to see it in the complete entry form without moving it out of schema order. The shared CMS form provides the existing add, duplicate, remove, and reorder controls for repeatable components and blocks.
 

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

@@ -2,20 +2,19 @@
 
 > Test each destination and review its delivery history before depending on it in production.
 
-Webhooks send site activity to an external HTTPS endpoint. Use them for focused reactions such as adding a waitlist submission to an email tool, notifying Slack after a publish, or starting a GitHub workflow after an agent review.
+Webhooks send site activity to an external HTTPS endpoint. Use them for focused reactions such as adding a waitlist submission to an email tool, notifying Slack after a publish, or starting a GitHub workflow after a publish.
 
 Only site members with Full Access can see Webhooks in Settings or manage its destinations and delivery history.
 
 ## Create one
 
-1. Open the site and choose **Settings**.
-2. Select **Webhooks**.
-3. Choose **New webhook**.
-4. Name it, select one event, and enter the destination URL.
-5. Optionally narrow form, agent, media, or entry events with the filter shown for that event.
-6. Review the request and select **Save**.
+1. Open **Settings** → **Advanced settings** → **Webhooks**.
+2. Choose **New webhook**.
+3. Name it, select one event, and enter the destination URL.
+4. Optionally narrow form, media, or entry events with the filter shown for that event.
+5. Review the request and select **Save**.
 
-The event groups are Entries, Forms, Publish, Agents, Analytics, Media, Domains, Labels, Locales, and Environments. Webhooks belong to the site, with up to 20 configurations. Choose the Main Branch, All Branches, Production, Preview, or one custom Environment. Main Branch is the default.
+The event groups are Entries, Forms, Publish, Analytics, Media, Domains, Labels, Locales, and Environments. Webhooks belong to the site, with up to 20 configurations. Choose the Main Branch, All Branches, Production, Preview, or one custom Environment. Main Branch is the default.
 
 Entry webhooks send one delivery per committed write. A bulk edit or environment merge may contain a bounded batch, and wider changes split into separately delivered batches.
 

package/dist/cli/bundle.json

@@ -1,8 +1,8 @@
 {
   "bundled": true,
   "bundler": "esbuild",
-  "bundledAt": "2026-10-08T08:47:47.864Z",
-  "cliVersion": "2.7.1",
+  "bundledAt": "2026-10-16T13:06:20.413Z",
+  "cliVersion": "2.8.0",
   "external": [
     "oxc-parser",
     "fsevents",