Taxonomy translations

support
,
3

EDIT 2025-02-10

Do not set lang, path, or kind in front matter.

These fields should only be used with the AddPage method within a content adaptor.

There’s a clever way to do this in the next release (v0.123.0), where content becomes multi-dimensional. To give you an idea…

themes/mytheme/content/
├── bar.md
└── foo.md

Yeah, so, how does that have any relationship to the section titles that are automatically generated for taxonomy pages?

themes/mytheme/content/bar.md

title = 'Tags (en)'
path = '/tags'
lang = 'en'
kind = 'taxonomy'

themes/mytheme/content/baz.md

title = 'Tags (de)'
path = '/tags'
lang = 'de'
kind = 'taxonomy'

I’m still trying to wrap my head around this a bit, but where you place content and how you name it are now a bit more flexible.

And, of course, since this content is in the theme’s content directory, if/when a site owner creates taxonomy section pages of their own, those pages take precedence over what I’ve done above. And that’s true regardless of whether they translate by directory or by file.

1 Like