Site
A site is one website with its code, content, media, settings, and Branches. Thefimo init, fimo clone, and fimo link commands connect a local directory to a site. See Sites and onboarding.
Site is the name shown in Fimo. The CLI and API still use the existing project commands, IDs, and configuration, including fimo projects, --project-id, and .fimo/project.json. Existing commands and links keep working.
CLI and Studio
You and your coding agent use thefimo CLI. Teammates can use Fimo Studio to edit content, manage media, review versions, and publish without changing code. Both work with the same site.
Editable content
Schemas define the content your team can edit. Entries hold structured page content, labels hold short interface copy, and the media library holds images, videos, and files. Your application renders those values with generated clients and Fimo components. See the CLI overview.Branches
Standalone Fimo sites start withmain. Additional Branches isolate code, content, assets, and Preview so you can work in parallel without changing production. CLI commands use the Fimo Branch that matches your current git branch. See Branches.
Preview and production
fimo deploy updates hosted Preview for review. fimo deploy --publish publishes from the site’s configured Production source Branch. New sites use main. Keeping those actions separate gives you a deliberate go-live step. See Preview vs production.
Site agents
A site agent is a Studio chat with a job. Its routines run by hand or on a schedule and report to it in its chat. Site agents are separate from the coding agent that edits your application. See Give an agent a job.What’s next
Choose your path
Start a site, link existing code, or set up a teammate.
Create an editable site
Put the first content-backed page in Studio.
Connect an agent
Give your coding agent Fimo skills and site rules.