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

# Content

> Manage text, images, and links with Fimo’s real-time CMS.

The **Content** tab is your built-in CMS. Every piece of text, image, and link generated by Fimo is editable and stored here, making it easy to collaborate and manage content at scale.

<img src="https://mintcdn.com/strapi/sEJa54XWkngCzyif/public/images/fimo-content.png?fit=max&auto=format&n=sEJa54XWkngCzyif&q=85&s=85eb8cc7b0f854da3cd6bf92173e016c" alt="Fimo Collections Page" width="3144" height="2020" data-path="public/images/fimo-content.png" />

## Key features

* **Built-in CMS** — All site content is editable by default, no setup needed.
* **Real-time edits** — Changes appear instantly across teammates’ preview windows.
* **AI credits saved** — Fix typos or small edits directly in the CMS.
* **Scalable management** — Prepare for advanced workflows like translations or A/B testing.

## Why it matters?

<Tip>
  <strong>Real-time collaboration.</strong> If <strong>User A</strong> updates content, <strong>User B</strong> sees it instantly in their preview window. No refresh needed.
</Tip>

<Columns cols={2}>
  <Card title="Without a CMS" icon="ban">
    • Edits only via AI chat\
    • Credits wasted on small fixes\
    • No central hub for content
  </Card>

  <Card title="With Fimo CMS" icon="check">
    • <strong>All content</strong> stored in one place\
    • <strong>No credits</strong> needed for edits\
    • <strong>Instant updates</strong> across teammates
  </Card>
</Columns>

## Collections, Entries, and Translations

To keep content organized, the CMS uses three building blocks:

## <Icon icon="folder-open" /> Collections

Think of a Collection as a **container**. It defines the structure of content, such as *blog posts* or *team members*. Each Collection includes a set of fields (title, image, link, etc.).

## <Icon icon="list" /> Entries

An Entry is a **single item** within a Collection. For example, one blog article or one team member profile. Each Entry follows the structure defined by its Collection.

## <Icon icon="language" /> Translations

Translations store **small, reusable pieces of copy** used across the product, such as *Back*, *Return to*, or page-specific titles. They are ideal for static text that belongs to a single page or UI element and needs to be localized.

## Workflow at a glance

<Steps>
  <Step title="Generate your site with AI">
    Fimo creates pages with editable text, images, and links.
  </Step>

  <Step title="Manage content in the CMS">
    Update Entries directly in the Content tab, fix typos, or make bulk edits.
  </Step>

  <Step title="Collaborate in real time">
    Teammates see changes instantly in their preview window, no refresh needed.
  </Step>
</Steps>

## What’s next?

The Content section includes tools to organize and update your site:

<Columns cols={2}>
  <Card title="Manage collections" icon="folder-open" href="/content/manage-collections">
    Learn how to structure your content at scale.
  </Card>

  <Card title="Manage entries" icon="list" href="/content/manage-entries">
    Edit individual text blocks, images, and links stored in the CMS.
  </Card>
</Columns>