ironng
ironng
Language selector added in #158. Additional work is required to grey out locales that have no translations available.
This is for the giant sand dollar on the home page hero section on the website.
@Gluzman mixing typefaces within lines or paragraphs is a bit trickier - it would require us to use special html to designate exceptions. For instance, any non-translatable text would have...
@Gluzman having both fonts for the site would be definitely heavier. Noto would just be for the Japanese/Korean/Chinese versions of the site, correct? I think based on how it's built...
@Gluzman do you intend the breadcrumbs to be present for mobile, or should they be hidden then?
@Gluzman I think that works, would we just leave the same amount of space below it as the other sections? Another thing that could be cute would be to have...
@Gluzman I think we can make these optional. Making the annotations unselectable might be tricky, but I'll look into it when I start work on this.
Thinking about this more. This solves the first issue of disabling these pages from being translated, but since the markdown files exist for each locale (i.e. src/pages/privacy-policy/index.ru.md), they either need...
>don't we already copy files that don't exist in a given localization when the build happens? We do! Not entirely sure if I understand your question here and there, but...