# Localize Translate v0.2.0 - Table of Contents

> Embedded translations for Ecto schemas

## Pages

- [Localize Translate](readme.md)
- [License](license.md)
- [Changelog](changelog.md)

- Guides
  - [Building Translatable Database Systems](translatable_database_systems.md)

## Modules

- [Localize.Translate](Localize.Translate.md): Manage translations embedded into translation structs.
- [Localize.Translate.JSON](Localize.Translate.JSON.md): Adapter that exposes the Erlang `:json` module under the bang-suffixed API
(`encode!/1`, `decode!/1`, `encode_to_iodata!/1`) expected by Ecto and Postgrex.
- [Localize.Translate.QueryBuilder](Localize.Translate.QueryBuilder.md): Provides helpers for filtering translations in `Ecto.Queries`.
- [Localize.Translate.Store](Localize.Translate.Store.md): Behaviour for translation storage backends.
- [Localize.Translate.Store.Embedded](Localize.Translate.Store.Embedded.md): The default translation store, keeping translations on the subject itself.
- [Localize.Translate.Store.SiblingResource](Localize.Translate.Store.SiblingResource.md): A translation store keeping translations in a sibling table, one row per
`(subject, locale)`.

## Mix Tasks

- [mix localize.translate.gen.translate_function](Mix.Tasks.Localize.Translate.Gen.TranslateFunction.md): Generates a migration to add a database function `translate_field` that uses the
`Localize.Translate` structured translation schema to resolve a translation for a field.

