Skip to main content
Your application remains code in your repository. Fimo adds editable content, isolated Branches, agent workflows, Studio, and hosting around it.

Project

A project is one website with its code, content, media, settings, and Branches. The fimo init, fimo clone, and fimo link commands connect a local directory to a project. See Projects and onboarding.

CLI and Studio

You and your coding agent use the fimo CLI. Teammates can use Fimo Studio to edit content, manage media, review versions, and publish without changing code. Both work with the same project.

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 projects start with main. 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 project’s configured Production source Branch. New projects use main. Keeping those actions separate gives you a deliberate go-live step. See Preview vs production.

Project agents

Project agents live as files in your repository. You can start them manually or schedule them for recurring work. They are separate from the coding agent that edits your application. See Project agents.

What’s next

Choose your path

Start a project, 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 project rules.