> For the complete documentation index, see [llms.txt](https://docs.intersectmbo.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intersectmbo.org/intersect-knowledge-base/archive/cardano-budget-archive/intersect-operational-services/2024-intersect-cdh-and-grant-contracts/2024-cdh-grants/closed-grants/inclusion-and-accessibility-phase-2/a-grant-to-implement-the-translation-tool.md).

# A Grant to implement the translation tool

{% hint style="danger" %}
**ARCHIVED**

This page has been archived. It's content might be outdated.
{% endhint %}

{% hint style="info" %}
This grant Part 1 is now closed
{% endhint %}

## Context

Govtool and Constitutional Committee Portal frontend are built on top of NextJS stack which has full I18n support since version 10. The i18n routing support is currently meant to complement existing i18n library solutions like react-intl, react-i18next, lingui, rosetta, next-intl, next-translate, next-multilingual, tolgee, inlang and others by streamlining the routes and locale parsing.\
\
The internationalization (and translations) work by providing the list of locales, the default locale and domain-specific locales, and the tech stack will automatically handle the routing.

The frontend stack itself is already configured as explained above. Now we need the community contributors to work on the translations and internationalization files holding key-value pairs of strings used across the interface. The default en-UK version will be provided.\
\
In order to provide the right tooling to community contributors to work on the translations, we need to implement a Translation Management system. Translized, Smartling, Localize or similar OR we can leverage from newer AI tooling.\
\
Solutions like Poedit offer online translations tools which can be integrated into our frontends so that users themselves can suggest better translations maintaining the context of written word in different languages.

## Functional Requirements

The successful applicant will be required to deploy Poedit, the localisation management system, and configure it to support GovTool translations and localisations to selected languages. The successful applicant will integrate Poedit with the Intersect GitHub account to more easily manage the localization of language files hosted on GitHub. Initially, the successful applicant will be required to use Automatic Translation feature which will allow us to use machine translation engines from Google, Microsoft and DeepL.\
\
Once configured, the tool will be used by contributors to work on the translations in selected languages.

## Budget

This grant is for 5,000 ADA.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.intersectmbo.org/intersect-knowledge-base/archive/cardano-budget-archive/intersect-operational-services/2024-intersect-cdh-and-grant-contracts/2024-cdh-grants/closed-grants/inclusion-and-accessibility-phase-2/a-grant-to-implement-the-translation-tool.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.