I18n for people

• without conflict
• editing directly on the site
• doesn't need developers for editing
• always in the context of the page

In our company, we often write web solutions with support for many languages, and for the correct translation it is very important to see the context of the content, so after a long search for the right and handy solution, we’ve come to TRS:

1. Editing on the page of real content
2. Easy control of locals and the creation of new ones
3. The components for diffefent frameworks

TRS structure consists of:

• Administrative part
• Server API
• Plugins

The administrative part allows you to create users and projects. For each project, you could create a variety of localization files. Frontend part created using ember.js, backend uses phoenix framework and postgresql database, localization files are stored in couchdb.

API part provides an opportunity to interact with the localization files through the api and the token authentication:

http://api.translations.api-hogs.io/api/v1/languages?project=${ID}

  {"en": {"index": {"title": "Index Page"}}, "de": {"index": {"title": "Index page de"}}}

For Ember.js applications there is a plugin that makes it easy to integrate TRS into your project - ember.

TRS can be used as self hosted application. To do this, you need to deploy TRS on your server.

Repo: TRS

Love example? Try it