You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 15, 2024. It is now read-only.
This is something we're trying to do (define the navigation in the front matter) but the 'name' keys here aren't being translated (just shows up as a literal string).
The text was updated successfully, but these errors were encountered:
Hi @pklada, I didn't understand exactly what you want to achieve.
If you want to provide translations on the front matter, then currently this is not possible, the translation tag provided on the plugin only searches on YAML files in the _i18n folder.
So if you use {% t page.subnav[2]["name"] %} it wont return subtitle.builder.
A use case for this would be to translate key-value attributes in a web-shop site:
---name: Pineapplesprice: 50
As the owner of that hypothetical site, I would like to present my product names in two different languages. The easiest way for me to do that would be to translate the name string in the front matter and that string only (I want to keep things DRY, so duplicating the price attribute would be an anti-pattern)
This is something we're trying to do (define the navigation in the front matter) but the 'name' keys here aren't being translated (just shows up as a literal string).
The text was updated successfully, but these errors were encountered: