fimo 2.7.1 → 2.8.0-staging.10

package/assets/skills/fimo-studio/references/command-palette.md

@@ -6,15 +6,16 @@ Press **Cmd+K** on macOS or **Ctrl+K** on Windows and Linux to open the command
 
 The palette includes the destinations you are allowed to use:
 
-- Organizations, projects, and the main Studio workspaces
+- Organizations, sites, and the main Studio workspaces
 - Preview pages
 - CMS Collections, Singles, Pages, Forms, Labels, and content types
 - Individual page templates and forms
 - Agent runs, definitions, and individual agents
-- Project settings sections, individual schedules and webhooks, connections, and MCP servers
-- Asset folders and code files
+- Site settings sections, individual schedules and webhooks, connections, and MCP servers
+- Asset folders
+- Chats, including archived ones, and **New chat** (use the **Chats** tab to search only chats)
 
-You can also open documentation, feedback, account actions, project history, invitations, and the Publish review flow. Use **Escape** to return from a searchable subpage to the main command list, then press it again to close the palette.
+You can also open documentation, feedback, account actions, site history, invitations, and the Publish review flow. Use **Escape** to return from a searchable subpage to the main command list, then press it again to close the palette.
 
 ## Actions for the Current Page
 
@@ -23,10 +24,8 @@ Studio adds commands that are relevant to the page you are viewing. Depending on
 - Refreshing Preview or opening it in a new tab
 - Creating a CMS entry or changing the content locale
 - Uploading an asset, creating a folder, or generating an image
-- Opening a code file or toggling the code sidebar
 - Running an agent, opening its Preview result, or resolving proposed changes
 - Editing or opening the current CMS page in Preview
-- Marking the current Inbox item read or unread, and archiving or restoring it
 - Running, pausing, resuming, or opening runs for the current schedule
 - Sending a test or opening deliveries for the current webhook
 - Inviting a member or buying a domain from the corresponding organization page

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

@@ -1,28 +1,27 @@
 # Connections
 
-Connections let a project use external services without exposing credentials to editors, chat, or agents. Studio, the
-CLI, and project agents all resolve the same project-scoped connection state.
+Connections let a site use external services without exposing credentials to editors, chat, or agents. Studio, the
+CLI, and site agents all resolve the same project-scoped connection state.
 
 ## See what is available
 
-1. Open the project.
-2. Open **More**, then **Settings**.
-3. Choose **Connections**.
+1. Open the site.
+2. Open **Settings** → **Advanced settings** → **Connections**.
 
 The page has two groups:
 
 - **Services** are integrations maintained by Fimo, such as Firecrawl, Fal, and Slack.
-- **MCP servers** are remote servers installed for this project. Choose **Add MCP server** beside this group to add one.
+- **MCP servers** are remote servers installed for this site. Choose **Add MCP server** beside this group to add one.
 
 Each row shows whether the connection is enabled, disabled, or needs attention. Open a row to enable or disable it for
-the current project, inspect its endpoint and live tools, or perform the repair appropriate to its authentication.
+the current site, inspect its endpoint and live tools, or perform the repair appropriate to its authentication.
 
 ## Add an MCP server
 
 Choose **Add MCP server** to open one setup flow:
 
 1. Pick a recommended server, choose **Custom MCP server**, or, if you are an organization owner or admin, choose
-   **Use from another project**.
+   **Use from another site**.
 2. Recommended servers fill their name and endpoint. A custom server asks for a name and Streamable HTTP HTTPS URL.
 3. **Connect with** offers the recommended sign-in path. Fimo checks the endpoint; public servers connect immediately,
    while OAuth servers open their provider sign-in page and return after approval.
@@ -33,8 +32,8 @@ For **Paste an access token**, enter only the token; Fimo adds the `Bearer` sche
 each complete value exactly as the server expects, including any prefix (`Authorization` with `Bearer abc123`). Fimo
 encrypts every saved grant and never shows its private value again.
 
-**Use from another project** does not make other projects' servers generally visible. It is an explicit admin-only
-picker that attaches an existing organization Connection to this project without revealing or copying its credential.
+**Use from another site** does not make other sites' servers generally visible. It is an explicit admin-only
+picker that attaches an existing organization Connection to this site without revealing or copying its credential.
 
 Each authentication method has one repair:
 
@@ -47,6 +46,6 @@ Only organization owners and admins can replace a shared credential. OAuth and m
 together.
 
 After the server is added, its detail shows the endpoint and the tools Fimo discovered. Only enabled servers become
-available to Studio chat, autonomous agents, and the Fimo CLI for this project. Agents should discover them with
+available to Studio chat, autonomous agents, and the Fimo CLI for this site. Agents should discover them with
 `fimo integrations list`, inspect them with `fimo integrations info <integration>`, and run an allowed tool with
 `fimo integrations run <integration> <tool>`.

package/assets/skills/fimo-studio/references/custom-domains.md

@@ -5,14 +5,14 @@ If you're driving Fimo from the terminal, the equivalent commands are `fimo doma
 ## Before You Start
 
 - You need a **premium plan**. Without it, the Domains option shows an "Upgrade" label.
-- Your project must be **published at least once**. An alert appears if it has not been published yet.
+- Your site must be **published at least once**. An alert appears if it has not been published yet.
 - You need access to your **domain registrar** (GoDaddy, Namecheap, Cloudflare, etc.).
 - Both **subdomains** (e.g., `blog.example.com`) and **apex/root domains** (e.g., `example.com`) are supported. A subdomain uses a single CNAME record; an apex domain uses two A records, with an optional automatic redirect to its `www` subdomain. The redirect direction can be reversed later without changing DNS.
 
 ## Adding a Custom Domain
 
-1. Open **Settings** from the top navigation bar (gear icon), alongside Preview, Content, Assets, Agents, and Analytics.
-2. In the Settings menu on the left, select **Domains** (globe icon) — listed with General and SEO.
+1. Open **Settings**.
+2. Select **Domains** (globe icon).
 3. Click the **Add domain** button (+ icon) in the top-right of the panel. (When domain purchase is enabled, a **Buy domain** button with a shopping-cart icon sits next to it.)
 4. A drawer opens. Type or select a domain — you can enter a subdomain or an apex domain. Domains your organization already owns appear in an autocomplete dropdown, and Fimo checks availability live as you type. For an apex domain, a checkbox lets you also redirect it to the `www` subdomain (on by default). Confirm to add it.
 5. A DNS table appears showing the record(s) you need to add. For a **subdomain** it's a single CNAME record:

package/assets/skills/fimo-studio/references/drawing-and-wireframing.md

@@ -1,8 +1,6 @@
 ## Opening the Drawing Tool
 
-Inside an existing project, open the wireframe canvas from the chat attachment dropdown: click the add-attachments (**+**) button next to the chat input, then choose **Draw**. (This option is hidden on mobile.)
-
-<!-- TODO(audit 2026-06-03): The previously documented "pen icon in the project creation form" entry point could not be confirmed in apps/ui. The drawing dialog there is only opened from the chat attachment dropdown. If a creation-form pen icon exists on the landing/home surface, document it here. -->
+Inside an existing site, open the wireframe canvas from the chat attachment dropdown: click the add-attachments (**+**) button next to the chat input, then choose **Draw**. (This option is hidden on mobile.)
 
 Selecting **Draw** opens a large drawing canvas powered by Excalidraw, displayed in a centered dialog.
 
@@ -54,7 +52,7 @@ When you are happy with your sketch:
 
 Click the **clear canvas** button to start fresh. A confirmation dialog appears before clearing to prevent accidental loss.
 
-Your work is retained while you close and reopen the canvas within the same session, so you can step away and come back to it. It is cleared once you attach the drawing, and it is not persisted across page reloads or navigating away from the project.
+Your work is retained while you close and reopen the canvas within the same session, so you can step away and come back to it. It is cleared once you attach the drawing, and it is not persisted across page reloads or navigating away from the site.
 
 ## Getting the Best Results
 

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

@@ -0,0 +1,9 @@
+# Site knowledge
+
+Open **Settings → Knowledge**. This is shared guidance for the whole site: brand, audience, goals, rules, tone of voice, and design preferences.
+
+Managers can write Markdown directly, or click **Draft from website**. The AI action runs in the background and fills the same text field. Read or edit the result, then click **Save knowledge**. Only Save changes the shared setting; Cancel restores the saved text. An empty setting is valid.
+
+Viewers and ordinary editors can read knowledge. Managers and explicitly authorized agents can save it. Agent writes require an explicit user request. Each save replaces the current text; there is no knowledge version history or conflict workflow.
+
+Agents use saved guidance when proposing, planning, designing, coding, or writing for the site. Changes apply on the next context refresh. Do not ask users to fill an empty setting unless their current task needs missing information.

package/assets/skills/fimo-studio/references/media-library.md

@@ -1,6 +1,6 @@
 ## Uploading Files
 
-1. Click the **Assets tab** (image icon) in the top navigation.
+1. Open **Assets** (image icon).
 2. You see a grid view of your files with a folder sidebar on the left.
 3. Click the **Plus (+) dropdown** at the top. It offers three options:
    - **Upload File** -- select files from your computer.
@@ -28,6 +28,10 @@ Click any file to open a preview dialog:
 
 The preview shows file metadata (size, dimensions, upload date) and editable fields for **name**, **alt text**, and **caption**. Alt text and captions are generated automatically by AI after upload -- you'll see a **Generating with AI** indicator, then an **AI generated** badge once they're ready, and you can edit the suggested text inline. From here you can also **copy the link** or **send the file to chat**. To **move**, **rename**, or **delete** a file, use its right-click menu in the grid instead.
 
+## Replacing a File in Content
+
+In a file's details, choose **Replace file**, pick a replacement, then select **Continue** to review the Current Branch reference count. **Back** or **Escape** returns to the picker with the choice preserved; closing the picker returns to the file's details. Only confirming the replacement changes references. Main, the live site, other Branches, and the original file stay unchanged.
+
 ## AI Image Generation
 
 1. Click the **Plus (+) dropdown** in the media library and select **Generate Image**.
@@ -54,7 +58,6 @@ There are several ways to share files with the AI or reference them in conversat
 - Click the **+** button in the chat and choose **Attach Assets** to browse your media library.
 - Choose **Upload from Computer** to add a new file directly from the chat.
 - Type **@** to reference a specific file inline.
-- **Drag a file** from the media library into the chat.
 - Ask the AI to use a specific image by name (for example, "Use the hero-banner image on the home page").
 
 ## Bulk Actions

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
 
@@ -38,17 +38,11 @@ You may see different overlays depending on what is happening:
 - **"Recovering preview…"** -- The visible preview is reloading after a refresh or a recoverable development-server failure.
 - **"Editing unavailable"** -- The site remains visible, but its Fimo integration did not connect in time. Visual editing and the route selector stay unavailable; preview and refresh still work.
 - **Error overlay** -- Something went wrong. The overlay shows details about the issue, and the AI can often auto-fix it for you.
-- **"Some installed packages need approval"** -- Choose **Fix with Fimo** to send the complete repair context to the coding agent, or **Copy details** to handle it elsewhere. Review every named package, commit only trusted package-specific approvals, and retry Preview. Never replace the project policy with a blanket allow-all setting.
-- **First generation progress** -- When your project is being built for the first time, a progress overlay shows the current status.
+- **"Some installed packages need approval"** -- Choose **Fix with Fimo** to send the complete repair context to the coding agent, or **Copy details** to handle it elsewhere. Review every named package, commit only trusted package-specific approvals, and retry Preview. Never replace the site policy with a blanket allow-all setting.
+- **First generation progress** -- When your site is being built for the first time, a progress overlay shows the current status.
 
 ## 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+4** -- Code
-- **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,32 @@
-## Create a Project
+## Create a Site
 
-1. Open **Projects** in Fimo Studio.
-2. Select **Create project**. If the button is unavailable, ask an organization admin for project creation permission.
-3. Enter a project name and select **Create**.
-4. Studio opens the new project's **Getting started** view.
+1. Open **Sites** in Fimo Studio.
+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 Project
+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 project, 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 project 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, then asks three questions in a short chat: what the business does, who its competitors are, and what sets it apart. The answers are saved as the site's knowledge.
+3. The report 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 **Clone & fix your homepage**. The site opens on its **Getting started** chat, where Fimo rebuilds the homepage with the report's problems fixed. Fimo covers the cost of the analysis, the questions and the rebuild; credits are not used.
+
+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 project. 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

@@ -2,15 +2,15 @@
 
 1. Look for the **Publish** button in the top-right of the header bar.
 2. Click it to open the publish panel. This shows your current status, your live URL (once you have one), any custom domains, and a **SEO Settings** shortcut.
-3. Click **Publish** inside the panel to start the deploy. A toast notification says "Publishing project..." and the panel's status badge switches to **Publishing** with a spinner.
+3. Click **Publish** inside the panel to start the deploy. A toast notification says "Publishing site..." and the panel's status badge switches to **Publishing** with a spinner.
 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 project 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
 
-Every change you make is automatically saved to your project, but saved changes are not live yet. Think of it like writing a draft: it is saved, but nobody sees it until you publish.
+Every change you make is automatically saved to your site, but saved changes are not live yet. Think of it like writing a draft: it is saved, but nobody sees it until you publish.
 
 To push your latest changes live, open the publish panel from the header **Publish** button and click **Publish** inside it again. It redeploys with your latest code and content.
 
@@ -27,21 +27,21 @@ When the AI requested publication, the review dialog offers **Merge and publish*
 The header **Publish** button itself only shows the label "Publish" (or a spinner while a deploy is running). Open the panel to see the current state:
 
 - **"Not published yet"** — Your site has never been published. Use **Publish** inside the panel when it is enabled.
-- **"This project uses an older version of Fimo"** — Upgrade the project's Production source before publishing new changes. **Upgrade project** opens its Preview, where you can request the migration in the existing chat. Your previously published site stays online.
+- **"This site uses an older version of Fimo"** — Upgrade the site's Production source before publishing new changes. **Upgrade site** opens its Preview, where you can request the migration in the existing chat. Your previously published site stays online.
 - **"Publishing"** — Publishing is in progress. A spinner and a **Publishing** status badge show while it builds, and the button is disabled.
 - **"Published"** — Your site is live. A **Published** status badge appears, your live URL is listed under a **Published site** heading as a clickable link, and a **Last published** date and time is shown.
-- **"Couldn't publish · N issues"** — Project validation found issues that must be fixed first. Choose **Fix with Fimo** to send the safe issue list to the project chat and ask Fimo to repair it.
-- **"Latest update failed"** — The newest publication did not finish. The panel says what went wrong and, for a site that was published before, that the previous version remains the active release — so it can appear beside **Published**. It stays until a newer publication finishes. **View details** opens the reader's Inbox item about the failure, which offers **Open publishing** and **Contact support**. Studio never shows the build output; read it with `fimo publish logs <id>`, taking the id from `fimo publish list`. The person who published and the project's managers get that Inbox item, plus an email unless they turned off **Publication failures** in Account settings → Notifications.
+- **"Couldn't publish · N issues"** — Site validation found issues that must be fixed first. Choose **Fix with Fimo** to send the safe issue list to the site chat and ask Fimo to repair it.
+- **"Latest update failed"** — The newest publication did not finish. The panel says what went wrong and, for a site that was published before, that the previous version remains the active release — so it can appear beside **Published**. It stays until a newer publication finishes. Studio never shows the build output; read it with `fimo publish logs <id>`, taking the id from `fimo publish list`. The person who published and the site's managers get an email that opens this panel, unless they turned off **Publication failures** in Account settings → Notifications.
 
 ## 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.
 
 ## Troubleshooting
 
 - **Changes not showing on the live site**: Try clearing your browser cache or opening the site in an incognito/private window.
-- **Publish button is disabled or missing**: Check the upgrade explanation and your publish permissions. If the button shows a tooltip about permissions, ask the project owner to check your role.
+- **Publish button is disabled or missing**: Check the upgrade explanation and your publish permissions. If the button shows a tooltip about permissions, ask the site owner to check your role.
 - **On mobile**: The header **Publish** button opens a drawer with the same status and confirmation action as the desktop panel.

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

@@ -1,12 +1,11 @@
 # Schedules
 
-Schedules run recurring project commands in one environment. Use the Studio surface to review configuration, pause or resume automatic runs, start work now, and inspect what happened afterward.
+Schedules run recurring site commands in one environment. Use the Studio surface to review configuration, pause or resume automatic runs, start work now, and inspect what happened afterward.
 
 ## Open schedules
 
-1. Open the project 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.
 
@@ -16,10 +15,10 @@ Choose **New schedule** to set:
 
 - A human-readable name
 - A standard five-field cron expression
-- The command to run from the project root
-- The project secret keys the command is allowed to use
+- The command to run from the site root
+- The site secret keys the command is allowed to use
 
-A schedule with no selected secret keys receives no project secrets. Studio displays key names only and never reveals secret values.
+A schedule with no selected secret keys receives no site secrets. Studio displays key names only and never reveals secret values.
 
 Open a schedule to change its configuration. Use **Pause** to prevent future cron runs without deleting its history, and **Resume** to make the cron active again.
 

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,19 +1,18 @@
-## Inviting People to Your Project
+## Inviting People to Your Site
 
-1. Click the **Invite** button in the project 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 project, including settings and member management.
-   - **Can edit** -- can edit code, content, and assets, and use the AI chat. Cannot change project settings.
-   - **Can comment** -- can view the project and leave comments but cannot make edits.
-   - **Can view** -- can see the project but cannot make any changes or comments.
+   - **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 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.
 
 ## Managing Members
 
-Open the sharing panel to see everyone who has access to your project. Each member appears with their avatar, name, and current access level.
+Open the sharing panel to see everyone who has access to your site. Each member appears with their avatar, name, and current access level.
 
 - **Change access**: Click the role dropdown next to a member's name and pick a new level.
 - **Remove someone**: Open the role dropdown next to their name and choose **Delete** to revoke access.
@@ -21,16 +20,15 @@ Open the sharing panel to see everyone who has access to your project. Each memb
 
 ## Real-Time Collaboration
 
-When multiple people are working on the same project at the same time, you can see each other's activity:
+When multiple people are working on the same site at the same time, you can see each other's activity:
 
-- Each person's cursor is labeled with their name in the code editor and the preview, so you can tell who is who.
-- In the code editor, each person also gets a distinct color for their cursor and selection. (Preview cursors all share a single color, but the name label still identifies each person.)
-- Edits appear in real time -- no need to refresh or save manually.
+- Each person's cursor is labeled with their name in the preview, so you can tell who is who.
+- CMS content changes appear in real time.
 
 ## Organization Access
 
-If your project belongs to an organization, some members may already have access based on their organization role.
+If your site belongs to an organization, some members may already have access based on their organization role.
 
 - At the bottom of the sharing panel, below the invite field and the member list, an **Everyone in <your organization>** row lets you set the default access level for all org members. This control also offers **No access** to turn org-wide access off.
-- When org-wide access is set, all organization members can see the project at that level.
+- When org-wide access is set, all organization members can see the site at that level.
 - You can still invite people individually for more specific access.

package/assets/skills/fimo-studio/references/version-history.md

@@ -1,10 +1,10 @@
 ## Where to Find Version History
 
-Click your **project name** in the top bar to open the project dropdown menu, then select **History**. This opens the version history panel showing all your saved versions.
+Click your **site name** in the top bar to open the site dropdown menu, then select **History**. This opens the version history panel showing all your saved versions.
 
 ## How Versions Are Created
 
-Versions are created automatically as you work — you don't create them by hand. Whenever the AI makes meaningful changes to your project, it captures a restore point for the current environment that you can browse, rename, and restore. A restore point includes the project code and CMS data, including schemas, entries, translations, and forms. There is no "create version" button in the panel; the history list only shows the restore points that already exist.
+Versions are created automatically as you work — you don't create them by hand. Whenever the AI makes meaningful changes to your site, it captures a restore point for the current environment that you can browse, rename, and restore. A restore point includes the site code and CMS data, including schemas, entries, translations, and forms. There is no "create version" button in the panel; the history list only shows the restore points that already exist.
 
 ## Browsing Versions
 
@@ -25,7 +25,7 @@ Find the version you want to update, click the **three-dot menu**, select **Edit
 
 ## Key Concepts
 
-- **Automatic versions** -- The AI creates these whenever it makes significant changes to your project. You do not need to do anything for these to appear.
+- **Automatic versions** -- The AI creates these whenever it makes significant changes to your site. You do not need to do anything for these to appear.
 - **Studio is browse and restore** -- Studio does not create restore points manually. Developers can use `fimo history create "Name"` from the CLI.
 - **Environment-scoped history** -- Each environment has its own restore points. Restoring one environment does not change another.
 - **Safe restore** -- Fimo records the current code and CMS data as a safety point before replacing them.
@@ -33,7 +33,7 @@ Find the version you want to update, click the **three-dot menu**, select **Edit
 
 ## Quick Restore from Chat
 
-Each AI message in the chat that made changes to your project shows an **undo button** (↩ icon) on the right side. Click it and a **"Restore version?"** prompt appears; confirm it to restore the current environment to the state it was in at that message. Fimo saves a safety point first, so CMS work completed after that message remains recoverable. This is the fastest way to undo a recent change without opening the full version history panel.
+Each AI message in the chat that made changes to your site shows an **undo button** (↩ icon) on the right side. Click it and a **"Restore version?"** prompt appears; confirm it to restore the current environment to the state it was in at that message. Fimo saves a safety point first, so CMS work completed after that message remains recoverable. This is the fastest way to undo a recent change without opening the full version history panel.
 
 The undo button is disabled on the most recent change (you can't restore the version you're already on) and is only available to members with permission to manage history.
 

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

@@ -1,20 +1,22 @@
 ## Entering Edit Mode
 
-Click the **Edit mode** toggle (the mouse pointer icon) in the chat input area at the bottom, next to the attach button and model selector. You can also press **Alt+E** (⌥+E on Mac). The preview must be visible and your project fully loaded before edit mode is available. Note: edit mode is not available on mobile.
+Click the **Edit mode** icon in the preview header, next to Share, or press **Alt+E** (⌥+E on Mac). You can also hold **Alt** (**Option** on Mac); the icon stays active without opening a panel. Select an element, release the key, and continue editing. Releasing without a selection leaves temporary edit mode. Shortcuts are inactive while typing in a field. The preview must be visible and your site fully loaded before edit mode is available. Note: edit mode is not available on mobile.
 
 ## Selecting and Editing Elements
 
-Once in edit mode, click on any element in the preview -- text, buttons, images, containers, anything. The selected element highlights, and a side editor panel opens on the right.
+Once in edit mode, click an element in the preview. An orange outline highlights it. CMS-managed text, images, rich text, and structured fields open the side editor.
 
 ### Editing Content
 
-For text elements, the side panel opens the selected field immediately with its current value. This covers CMS-managed content, hardcoded text, and hardcoded images. Changes save automatically, and the preview updates as you type.
+Update the selected field in the sidebar. Changes save automatically and appear in the preview. Failed saves keep the draft available for correction or retry. Use AI chat to change text and images written directly in the site code.
 
-For CMS content, choose **All fields** to open the complete entry form. Studio keeps the content type's field order, scrolls to the field you selected, and focuses it in place. Loading appears only while Studio fetches this additional entry data or moves to another entry.
+The link icon beside the field in the sidebar opens its label or CMS entry. Choose **All fields** in the side editor to open the complete entry form. Studio keeps the content type's field order, scrolls to the field you selected, and focuses it in place. Loading appears only while Studio fetches this additional entry data or moves to another entry.
+
+Incomplete JSON drafts stay local. Leaving an empty JSON field saves `null` and updates the preview without reloading the page.
 
 ### 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.
 
@@ -26,9 +28,9 @@ Selecting an element with nothing editable (a container, a spacer, a decorative
 
 ## Exiting Edit Mode
 
-Click the **Edit mode** toggle again or close the side panel. The side editor closes and you return to preview mode.
+Click the **Edit mode** icon again to return to preview mode. Closing the side panel dismisses its selected field.
 
 ## When to Use Edit Mode vs. Chat
 
-- **Edit mode** is for content -- updating a headline, swapping an image, fixing a paragraph.
+- **Edit mode** is for CMS content -- updating a headline, swapping an image, fixing a paragraph.
 - **Chat** handles everything else -- visual changes (colors, spacing, typography), new sections, page layout, and new functionality.

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

@@ -2,26 +2,25 @@
 
 > Test each destination and review its delivery history before depending on it in production.
 
-Webhooks send project 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 an agent review.
 
-Only project members with Full Access can see Webhooks in Settings or manage its destinations and delivery history.
+Only site members with Full Access can see Webhooks in Settings or manage its destinations and delivery history.
 
 ## Create one
 
-1. Open the project 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, agent, 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 project, 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, 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.
 
 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.
 
 ## Configure the request
 
-The default payload is the complete Fimo event, including its type, project, scalar Environment and Branch context, timestamp, and event-specific data. The legacy `env.name` Branch field remains available. Keep the complete payload when the destination can accept it.
+The default payload is the complete Fimo event, including its type, site, scalar Environment and Branch context, timestamp, and event-specific data. The legacy `env.name` Branch field remains available. Keep the complete payload when the destination can accept it.
 
 Choose **Custom template** when a service expects a specific JSON shape. Use **Insert variable** to pick fields for the selected event. Variables use paths such as `{{ event.data.submission.data.email }}`. The preview catches invalid JSON and missing variables before save.
 
@@ -29,7 +28,7 @@ When Studio recognizes a Resend, Slack, or GitHub URL, it offers a request setup
 
 ## Add authentication
 
-Under **Headers**, add a header name and type any non-secret prefix, such as `Bearer `. Choose **Insert secret** to select an existing project secret or create one without leaving the webhook editor. Creating a secret never replaces an existing secret with the same name; select the existing secret instead. Fixed values are suitable only for non-sensitive headers.
+Under **Headers**, add a header name and type any non-secret prefix, such as `Bearer `. Choose **Insert secret** to select an existing site secret or create one without leaving the webhook editor. Creating a secret never replaces an existing secret with the same name; select the existing secret instead. Fixed values are suitable only for non-sensitive headers.
 
 Fimo signs requests by default. Save the signing secret shown after creation so a custom receiver can verify `X-Fimo-Signature`. Rotate it from the webhook configuration if it is exposed.
 

package/dist/cli/bundle.json

@@ -1,7 +1,7 @@
 {
   "bundled": true,
   "bundler": "esbuild",
-  "bundledAt": "2026-09-16T13:43:08.740Z",
+  "bundledAt": "2026-10-12T08:45:36.990Z",
   "cliVersion": "2.7.1",
   "external": [
     "oxc-parser",