Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What base_path to use so that includes are -- well -- included? #312

Open
mgriff88 opened this issue Aug 19, 2024 · 0 comments
Open

What base_path to use so that includes are -- well -- included? #312

mgriff88 opened this issue Aug 19, 2024 · 0 comments

Comments

@mgriff88
Copy link

I have a mkdocs site available in both English and Japanese. It's structured like so:

- docs/
    - en/
           - file1.md
           - file2.md
           - includes/
                - include1.md
                - include2.md
     - ja/
           - file1.md
           - file2.md
           - includes/
                - include1.md
                - include2.md

I use the markdown-include plugin for placing those includes throughout my docs. Typically I just call upon it like [!./includes/include1.md!].

But, because you have to set a base_path for the includes, this is breaking mkdocs-static-i18n. Just setting the base_path as docs doesn't work -- it has to be docs/en or docs/ja. But, then you have to pick one language or the other, which defeats the purpose of the localized site.

image

Is there someway to tell another plugin that it should be using whatever two-letter i18n code in that base_path, relative to what site it's on? Something like docs/**?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant