Components
Components
This project makes use of a modular service based architecture. This allows for components to be re-used in a modular fashion meaning that if there's a need for multiple components of the ecosystem that need to use the translator, it makes more sense to have a separate translation service.
For example, there is no need for i18nr to be making calls to the readr backend to translate text so it's better to take the translations out of the scope of readr into translatr. This means that there's no muddying the waters when it comes to storing translations for readr users, readr doesn't need to be concerned with users that may not even be using the bulk of readr functionality and if anything were to cause readr to crash, other user's that aren't using readr would be able to continue using translatr.
For this reason, the different moving parts of this project will be in different repos throughout the decyhpr organisation in Github.
Services that have a UI will generally have a backend service, and UI, likely using React, like in the case of readr which has the backend service and the UI written in React. This will mean that products may be split across repos.