all languages and their appropriate translations are linked within the i18n repository, which is initialized as a sub-module in site: ..src/lib/i18n.
ideally, we keep the format as lang.json and not lang.ts/lang.js for translations as i'm not sure on how well crowdin's support is for those files and i don't want to break the current setup
preferred locale should be saved as a cookie, and should not have a route for lang e.g site.com/en/asset/asdf = bad
in other words: need to find a good i18n library or just write a custom one kek
all languages and their appropriate translations are linked within the
i18n
repository, which is initialized as a sub-module in site:..src/lib/i18n
.ideally, we keep the format as
lang.json
and notlang.ts/lang.js
for translations as i'm not sure on how well crowdin's support is for those files and i don't want to break the current setuppreferred locale should be saved as a cookie, and should not have a route for lang e.g
site.com/en/asset/asdf
= badin other words: need to find a good i18n library or just write a custom one kek