How to use taxonomy in a multi-lingual environment?
ralph
Member ✭
We had recently some discussions on how organize a client list into different industries. There were two solutions on the table:
1. Create a content type called industries and apply an inventory item as a modular content to a client
2. Create a taxonomy group, called industries and tag the content item "client" with a tag
Our dev favored option 2, however, it seems not to be possible to localize a tag and it would therefor never be possible to display the tag in the UI.
What would the official recommendation for this?
Best Answer
-
@RalphSpandl thanks for an interesting use-case! Let me just add a few bits to what @MartinDanko said. To be honest, when designing multilingual support for Kentico Cloud, we designed localization of taxonomy groups as well. We plan to do it in the future, but as many other priorities arrive, we postponed it. Mind you, there's no need to be constrained by using taxonomy groups. I believe the best way, if it's possible would be to share the industries with us, so that we can see whether's it's a flat structure or a hierarchy etc. Then, I believe we can come up with a best practice for you. Thanks!
5
Answers
Hi Ralph,
could you please give us a little bit more information on this requirement?
1. When and how would you like to use the localization in relation to this?
2. What's the information architecture for client/industry
In general we recommend to use modular content in wide variety of cases, but better understanding of your scenario will help us to find the best solution for you
@TomasHruby , @MartinDanko we basically want to setup a similar navigation as shown here:
https://www.effekt.dk/work/
This is clearly best done by tagging projects. However, since the tags are exposed to the user, they need translation.
What we did now, I created a content model called categories create as many categories in the inventory that I need and drag and drop these content models into the project.