> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fimo.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Version history

> Restore your project to an earlier state — code and content together.

Fimo keeps a full history of your project so you can go back if something goes wrong. Because a Fimo project is real git plus a versioned content plane, history covers **both code and content** together.

## What's tracked

* **Code** — your project is a genuine git repository with `fimo` as the remote. Every `fimo deploy` commits and pushes, so your code history is standard git history you can inspect, diff, and revert with git itself.
* **Releases** — each production release is tagged. `fimo publish --version <ver>` tags `main@HEAD` as `release/<version>`, giving you named, restorable points in time.
* **Content** — schemas, entries, labels, assets, and forms are versioned per environment alongside the code that renders them.

## Restore an earlier state

Point-in-time restore that rolls **content and code back together** lives in [Fimo Studio's version history](/docs/studio/version-history) — the safest way to recover a whole-project state without wrangling git and the content plane by hand.

<Tip>
  Want to explore a rollback without touching the live site? Create an isolated environment first (`fimo checkout -b restore-test`), verify it, then merge and publish. See [Environments](/docs/environments/overview).
</Tip>

## What's next

<Columns cols={3}>
  <Card title="Version history in Studio" icon="clock-rotate-left" href="/docs/studio/version-history">
    Restore a whole-project state visually.
  </Card>

  <Card title="Environments" icon="code-branch" href="/docs/environments/overview">
    Isolate risky changes on a branch.
  </Card>

  <Card title="Deploy & publish" icon="cloud-arrow-up" href="/docs/deploy/overview">
    How releases are cut.
  </Card>
</Columns>