> ## 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. # Glossary > Plain-language definitions of the terms used across Fimo. Use this page when a Fimo command or guide introduces an unfamiliar term. Follow the linked task guides when you need to complete a workflow. ## Core ### Project One website and its code, content, media, and settings. Every project belongs to an organization. ### Organization The workspace that contains projects and teammates. The CLI uses an active organization when a command needs an organization and you do not pass one. ### Fimo CLI The command-line tool that you and your coding agent use to work with Fimo. See the [CLI reference](/docs/reference/cli) for its commands. ### Fimo Studio The visual app for editing and managing a Fimo project. See the [Studio overview](/docs/studio/overview) for its available tools. ### Branch An isolated place for project work, associated with a git branch. Branches let you change and review a project before merging it into another Branch. ### Environment A project setting that groups Branches for deployment. Fimo provides built-in Environments and supports custom Environments through the CLI. ### Preview A hosted, shareable version of a Branch. Run `fimo deploy` to push changes to it, or `fimo preview url` to get its address without deploying. ### Production Your live public website. Publishing updates it from `main`. ## Content & media ### CMS (Content Management System) The built-in store that keeps your site's structured content in one place, editable without touching code. Fimo's core rule: content lives in the CMS, never hardcoded in JSX. ### Schema A content model that defines the fields in a content type. For example, a `BlogPost` schema might have title, image, and body fields. Push schemas with `fimo schemas push`. ### Entry One record of a schema, such as a blog post or product. Create and query entries with `fimo entries`. ### Single One set of content for a schema, such as a homepage or site settings. Singles are read and updated with `fimo singles`, without an entry ID, and edited by non-developers in Studio. ### Media library The project area for uploaded images, videos, and files. Manage it with `fimo assets` or in Studio. ### AI media generation Creating or transforming images and video with commands such as `fimo image generate`, `fimo image edit`, and `fimo video generate`. ### Form A form registered with Fimo through `fimo forms push`. Read its visitor submissions with `fimo forms submissions`. ## Localization ### Label A piece of static UI copy (headings, buttons, nav, placeholders) wrapped in `t('key')` in code, with its value stored in Fimo so editors can reword it without a code change. ### Locale A language or regional variant of your site, such as `en`, `es`, or `pt-BR`. A project has one default locale and can add others. ## AI & agents ### Coding agent An AI coding tool that builds or changes your site and can operate Fimo through the CLI. ### Skills Instructions that teach a coding agent how to use Fimo. `fimo skills install` installs the global Fimo skill, and `fimo skills get ` reads a skill supplied by your installed CLI. ### Rule files Project instructions for coding agents, such as `AGENTS.md` and tool-specific rule files. ### Scheduled agent An agent bundle stored in your repository that can run on demand or from a schedule. ### MCP (Model Context Protocol) A standard for connecting AI tools to external context and tools. See [MCP](/docs/ai/mcp) for Fimo setup. ### Markdown for agents Markdown output intended for agents, including page content and an `llms.txt` index when your published site supports it. ## Deploy & hosting ### Deploy Sending project changes to Fimo hosting. Use `fimo deploy` for a hosted preview and follow the [deploy guide](/docs/deploy/overview) when you are ready to publish. ### Publish Making the configured Production source Branch live. `fimo deploy --publish` pushes and publishes, while `fimo publish` publishes the revision already on the Fimo remote without pushing. New projects use `main` as their source. ### Default URL (subdomain) The `.fimo.site` address assigned to a project. Rename its slug with `fimo domains rename-default`. ### Custom domain A hostname you control, such as `blog.example.com`, attached to a Fimo project. See [Custom domains](/docs/deploy/custom-domains). ### SEO The titles, meta descriptions, alt text, and structured metadata that help search engines and people find and understand your site. ## Collaboration & billing ### Roles and permissions Access levels that control what a teammate can do in a project or organization. ### Invitation An email invitation to an organization or project. Create one with `fimo invite`. ### Version history A record of project restore points. Use Studio or `fimo history` to inspect available history. ### AI credits A usage meter for AI actions in Fimo. Check your organization's balance with `fimo credits`. See [Billing and credits](/docs/collaboration/billing-and-credits). ### Bandwidth A measure of traffic served by your published site. ### Overages Usage above the amount included in a plan. See [fimo.ai/pricing](https://fimo.ai/pricing) for current plan details. For current plans and prices, see [fimo.ai/pricing](https://fimo.ai/pricing), the source of truth since pricing changes over time.