Your first success is a page whose content a teammate can change in Studio without editing application code.
New site
New sites use the Next.js App Router template by default:
If you want the canonical React Router template, use --framework react-router.
The bundled shells are intentionally minimal. Start the local dev script with the package manager selected during
setup:
Then ask your coding agent to load fimo-code and make one real page editable.
Another framework or a blank site
Create the site, then ask your coding agent to make the first page editable. The agent should load the code skill that matches the installed Fimo package:
The implementation depends on the framework. The durable flow is the same: declare a schema, push it with fimo schemas push, create an entry, read it through the generated client, and render tracked values with the framework’s Fimo components. Use the CLI reference for command details.
Existing codebase
Run this inside the application’s root directory:
Choose or create the Fimo site when prompted. Linking keeps your application code, framework, git history, and existing origin. It adds the site link, Fimo remote, package dependency when needed, and detected framework settings.
Install the updated site dependencies with the package manager already used by the application:
Then load fimo-code and convert one real page to use a schema-backed entry. Start with a page that a teammate already needs to update, such as the homepage or About page.
Keep the first slice small. One editable page proves the code, Studio, and Preview loop before you move the rest of
the site.
Review before publishing
Run fimo deploy when you want a hosted Preview. Publish only after you have reviewed it:
See Deploy and publish before using the publish command. 