Hi @Marina P - the feature that you are describing is intended, for now, to simply localize the platform phrases.  That means, that if you already have some categories created for other languages, that members visiting those categories can have a better multi-language experience if they use the language selector (as the interface will be localized too).  There won’t be a connection between the two, though - all members will see all the categories.

What I think you’re looking for is what’s coming next in our multi-language roadmap and which you’ll find described in the ‘coming soon’ section in this update under ‘Dedicated Categories for Different Languages’:

Yes, probably. Ideally, if for each homepage element (at least), we also had a language toggle to set how it should look like for each localization. 

Thank you, @Kenneth R!

Do you by any chance know if it is possible to enable the language, but not publish it for the end users? I’d love to enable it, do some phrases translations, and only make it visible when we are all set. I think I saw two different toggles somewhere, but this is different in our backend:

You raise a good point @Marina P - it does appear to me as well that we need to enable the language before we can adjust any of the localised text strings.  Let me flag this with our Product team to confirm.

Hey @Marina P - I just checked with our Product Manager and he confirmed that it works as we both thought right now.  We need to first enable the language before editing the phrases.  This is going to change in an upcoming multi-language release, however. It will then be a matter of first enabling and then publishing, allowing us to edit the phrases before they’re visible to visitors.