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

# Introduction

> What TextSetu is, who it's for, and how the platform fits together.

## What is TextSetu?

TextSetu is a **translation management platform** (TMS). It is the single place
where a team manages all the text in their product across every language they
ship in.

Instead of emailing spreadsheets back and forth, juggling JSON files, or copy-
pasting strings into a dozen `.po` files, your whole team works in one shared,
structured workspace:

* **Developers** define translation *keys* and pull finished translations back
  out in whatever file format their app expects.
* **Translators** fill in those keys language-by-language in a fast, spreadsheet-
  like grid, with glossary and translation-memory suggestions guiding them.
* **Reviewers / managers** approve or reject proposed translations, track
  progress, and keep terminology consistent.

## The problem it solves

Localization breaks down in predictable ways:

| Without a TMS                                   | With TextSetu                                                 |
| ----------------------------------------------- | ------------------------------------------------------------- |
| Strings live in code, scattered across files    | Every string is a key with a value per language, in one place |
| Translators edit raw files and break syntax     | Translators edit values in a guided grid; syntax never breaks |
| No record of who changed what                   | Full history and rollback on every value                      |
| Terminology drifts ("Cart" vs "Bag")            | A shared **glossary** enforces approved terms                 |
| The same sentence gets re-translated repeatedly | **Translation memory** suggests prior translations            |
| Bad translations ship silently                  | An **approval workflow** gates changes before they go live    |
| Importing/exporting is a manual chore           | 40+ file formats import and export with one click             |

## Who it's for

* **Localization / product managers** who own the process, track completion, and
  manage who can do what.
* **Translators** (in-house or external) who do the actual translating.
* **Reviewers / approvers** who sign off on quality.
* **Developers** who integrate the translations into the product.

## What you can do with it

* Organize work into **organizations**, **projects**, and **teams**.
* Manage translation **keys** and their **values** across unlimited languages.
* Gate changes behind an **approval workflow** (proposals → review → publish).
* Work on isolated **branches** and merge them, just like code.
* Maintain a **glossary** of do-not-translate, forbidden, and preferred terms.
* Reuse past work via **translation memory** (TM).
* Catch mistakes automatically with **quality checks (QA)**.
* See **history** on every value and **roll back** to any prior version.
* **Import and export** in 40+ formats (JSON, XLIFF, CSV, Android XML, Apple
  `.strings`, Gettext PO, ARB, `.xcstrings`, YAML, RESX, and many more).
* Track progress and contributor activity with built-in **analytics**.

## How it's structured

TextSetu is organized as a hierarchy. The next page,
[Core Concepts](/docs/concepts), explains each level in detail, but in short:

```
Organization                ← your company / workspace
├── Projects                ← an app, site, or product surface to translate
│   └── Translation keys    ← each with one value per language
├── Glossaries              ← shared terminology, attachable to projects
├── Translation Memories    ← reusable translated segments
└── Teams                   ← groups of people you assign to work
```

Ready to dive in? Head to [Getting Started](/docs/getting-started).