Open GuidaGG opened 5 days ago
@bj-Bas-und-Aer @ah-bas-und-aer can you clarify the last point? -Popover EN: "Overlay" instead of "Gesamt" ????
Besides, the rest of the changes are implemented in the nomis site. I added some test urls for some of the partner logos in the german site. The correct structure for adding this data you can find in data/de/studio.json. After you add the references content structure, I can finish adding the translation structures. I also provided there a simple explanation on how to add these translations.
After you add the references content structure, I can finish adding the translation structures. I also provided there a simple explanation on how to add these translations. Okay, we do it right now.
-Popover EN: "Overlay" instead of "Gesamt" ????
If you go to the english version of the page. In the pop over we have the german word „gesamt“ this should be translated into english
aaah, you mean in the design page? in the categories.
After you add the references content structure, I can finish adding the translation structures. I also provided there a simple explanation on how to add these translations. Okay, we do it right now.
We started to add the references content but we dont know if it is the json or html data? We think the json structure for this is not exsisting yet?
So the structure in json depends on what content you need. Therefore I suggest you build the page as you want in the html. and then later we add the corresponding json structure for the translations.
You can also do it yourself. (if this is too complex, just add the content in the html and tell me when it is done :)
for each content you add in the html, you need to add the data-i18n
key, which will correspond to the key in the .json files.
for example you have 2 divs with 2 titles. Each title will have something like data-i18n="references_title_1
and data-i18n="references_title_2
.
<h3 data-i18n="reference_title_1" class="header paragraph">Column 1</h3>
<h3 data-i18n="reference_title_1" class="header paragraph">Column 1</h3>
In the studio.json
file you can then add the keys
"references_title_1" = "my title column 1"
"references_title_2" = "my title column 2"