# Localess


- **Introduction**
- [Overview](/docs): Open-source headless CMS with translation management, a Visual Editor, and a REST API — schema-driven, Firebase-hosted, and ready for any frontend.
- [Getting Started](/docs/getting-started): Getting started with Localess; deploy, create a space, define content, and connect to your frontend.

- **Setup and Integrations**
- Setup
  - [Local Run](/docs/setup/local): Run Localess locally for development or to try it out without any cloud infrastructure.
  - [Firebase](/docs/setup/firebase): Deploy Localess to production on Firebase.
  - [Docker](/docs/setup/docker): Run Localess locally using Docker Compose — no cloud account required.
- SDK
  - [TypeScript](/docs/sdk/typescript): Package: @localess/client — v3.0.0
  - [React](/docs/sdk/react): Package: @localess/react — v3.0.0
  - [Angular](/docs/sdk/angular): Angular SDK for Localess — content delivery, rich text rendering, asset management, and Visual Editor integration for client-side and server-side rendered Angular applications.
  - [Vue](/docs/sdk/vue): A dedicated @localess/vue package is on the roadmap. Until it ships, integrate Vue with Localess in two pieces: fetch content with the framework-agnostic JavaScript client, and wire up the Visual Editor with the browser sync script.
  - [Svelte](/docs/sdk/svelt): A dedicated @localess/svelte package is on the roadmap. Until it ships, integrate Svelte with Localess by combining the framework-agnostic JavaScript client (server-side fetch) with the browser sync script (Visual Editor).
  - [Astro](/docs/sdk/astro): A dedicated @localess/astro package is on the roadmap. Until it ships, integrate Astro with Localess by fetching content with the framework-agnostic JavaScript client and (optionally) injecting the Visual Editor sync script.
- CLI
  - [Get Started](/docs/cli): Package: @localess/cli — v3.0.6
  - [Login](/docs/cli/login): Authenticate with your Localess instance and store credentials securely.
  - [Logout](/docs/cli/logout): Clear stored credentials from your local Localess configuration.
  - [Translations](/docs/cli/translations): Push and pull translation files between your local project and Localess.
  - [Types](/docs/cli/types): Generate TypeScript type definitions from your Localess content schemas.

- **Features**
- [Localization](/docs/localization): Localess provides two distinct localization capabilities — Translation Manager for UI strings and Content Translation for structured multilingual content.
- [Translations](/docs/translations): Manage all your application's translation strings in one place — across every locale, with team collaboration and auto-translation support.
- [Draft & Publish](/docs/draft-publish): Nothing goes live until you say so. Localess keeps every change in Draft until you explicitly promote it to Published — giving your team a safe staging buffer built into the CMS.
- [Webhooks](/docs/webhooks): Receive real-time HTTP notifications when content, translations, or assets change in Localess — and trigger downstream systems automatically.
- [Assets](/docs/assets): Upload and organise images, videos, and other files — then reference them from your content schemas.
- [Image Transforms](/docs/image-transforms): Resize, reformat, and optimize images on demand by appending URL parameters to any Localess asset URL — no extra service required.
- [Content](/docs/content): Author and manage structured content documents organised in folders — each document follows a Schema and is available via the API in one or more locales.
- [Visual Editor](/docs/visual-editor): Preview and edit content in real time — see every change reflected instantly in your running application without leaving the Localess UI.
- Schemas
  - [Overview](/docs/schemas): Schemas define the structure of your content — the fields editors fill in and the shape of the data returned by the API.
  - [Text](/docs/schemas/text): Stores a single-line string. Use it for titles, headlines, or any short text that fits on one line.
  - [Text Area](/docs/schemas/text-area): Stores a multi-line plain text string. Use it for summaries, descriptions, or any content that spans multiple lines but does not need formatting.
  - [Number](/docs/schemas/number): Stores an integer or decimal number. Use it for quantities, prices, ratings, or any numeric value.
  - [Boolean](/docs/schemas/boolean): Stores true or false.
  - [Color](/docs/schemas/color): Stores a color as a hex string in
  - [Date](/docs/schemas/date): Stores a calendar date as an ISO-8601 string in YYYY-MM-DD format.
  - [Date Time](/docs/schemas/date-time): Stores a date and time as an ISO-8601 string in YYYY-MM-DDThh:mm format.
  - [Link](/docs/schemas/link): Stores either an external URL or an internal content reference, with optional target.
  - [Markdown](/docs/schemas/markdown): Stores a multi-line Markdown string. Use it for articles, long descriptions, and any content where editors need basic formatting via Markdown syntax. For one...
  - [Rich Text](/docs/schemas/rich-text): Stores structured formatted text as a Tiptap JSON document. Supports headings, bold, italic, lists, links, and code blocks.
  - [Asset (One)](/docs/schemas/asset): References a single asset (image, file, etc.) uploaded to the space.
  - [Assets (Multiple)](/docs/schemas/assets): References a list of assets uploaded to the space.
  - [Option (One)](/docs/schemas/option): Stores a single selected value from a predefined list. The list can be defined inline or sourced from an Enum schema.
  - [Options (Multiple)](/docs/schemas/options): Stores multiple selected values from a predefined list. The list can be defined inline or sourced from an Enum schema.
  - [Reference (One)](/docs/schemas/reference): Stores a reference to a single content document in the space. Resolved to the full document when fetched with resolveReference enabled.
  - [References (Multiple)](/docs/schemas/references): Stores references to multiple content documents in the space. Resolved to full document objects when fetched with resolveReference enabled.
  - [Schema (One)](/docs/schemas/schema): Embeds a single Node schema block inline. Use it for optional or singular nested components such as a CTA, a banner, or an author card.
  - [Schemas (Multiple)](/docs/schemas/schemas): Embeds a list of Node schema blocks inline. Use it for repeatable components such as page sections, button groups, or feature lists.