Skip to content

site_description translation (i18n) #5359

Discussion options

You must be logged in to vote

Using the recommended way to implement i18n into your docs, with separate mkdocs.yml files would easily allow you to use separate site_description for each of the language versions.

If you're using the i18n plugin for that then it's currently not available. I'll be adding it this month if the plugin's author won't finish the refactor sooner.

Replies: 2 comments 6 replies

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
6 replies
@why-not-try-calmer
Comment options

@kamilkrzyskow
Comment options

@why-not-try-calmer
Comment options

@why-not-try-calmer
Comment options

@kamilkrzyskow
Comment options

Answer selected by why-not-try-calmer
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants