Allow customizing the location for i18n content #1711
raisedadead
started this conversation in
Feature Requests
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What version of
starlightare you using?0.21.2
What is your idea?
Currently the folder structure for i18n supports requires the content to be like so:
content/docs/my-page.mdSo, then the i18n versions of the content can be at:
content/docs/es/my-page.mdcontent/docs/de/my-page.mdand so on...
This is not ideal.
When we have more nested docs, it would be great to have a dedicated location to wrap around all the languages like:
content/docs/i18n/es/my-page.mdcontent/docs/i18n/de/my-page.mdetc.
That way the root
docsfolder can have additional nesting without getting mixed with the 2-letter language folders.Additionally it makes it extremely simple to integrate with tools like Crowdin to define a source and a destination for translation work.
Why is this feature necessary?
This enables better organization for i18n content and straightforward integrations with tools like Crowdin.
Do you have examples of this feature in other projects?
No response
Participation
Beta Was this translation helpful? Give feedback.
All reactions