In some resources, the text content, GOAL: It is essential to display text elements such as field labellabels, descriptions, description and button label, must be displayed with their respective translation according to the language chosen by the user.
There is no specific rule to implement the content by Lokalize or Sanity. This should be analyzed and then decided with RBIberia.
In case the content will be translated by Lokalize, labels in accordance with the user's selected language translation.
PROBLEM: The method for implementing this requirement does not have a fixed standard and should be assessed and determined in consultation with RBIberia. Lokalize or Sanity can be considered for this purpose.
As Sanity…. the main challange is in the Lokalize process as the development team is responsible for creating a key for each content.
For this moment the development team must:
...
LOKALIZE DEVELOPMENT TEAM TASKS:
Creating distinct keys for each content item and inputting them in English.
...
Establishing a new page
...
...
that features a table structure.
...
Populating the content exclusively in English
...
, the only language we are familiar with and Google Translate is not allowed.
Send the completed page via email to our Product Owner
...
once all the necessary components are in place for implementation.
LOKALIZE PRODUCT OWNER TASK:
After we have done this, our Product Owner will be able to access Lokalize and add the content for other languages directly.
N.B.: If there is any impediment or impossibility for RBIberia to add the content, the Product Owner needs to request that we add it by providing the content for other languages.