Sébastien Lorber

Yes, this is somehow expected, as the drop-down need to be able to know all the localized urls 😅 you would also need to create your own drop-down of hard-coded...

Thanks I'll tell you when I have a version to test with these features Is your site open-source so that I can test on your site directly?

Not exactly the same, this issue is about i18n locale configuration, not docs version configuration (both should allow to configure the path) Still in my todo list, which unfortunately is...

It's hard for me to understand the desired UX, is it possible to have a screenshot/mockup or something showing what you are building in a more concrete way?

So what I understand is that, now when using the undocumented `:::important` then you have the wrong label but the right level/color? Expected: Actual: --- It would be quite easy...

Hmmm yes we can see that on our own deploy previews: https://deploy-preview-7644--docusaurus-2.netlify.app/blog/rss.xml > Interesting—yes, we need to normalize trailing slashes when generating metadata as well. I wanted trailing slashes to...

> Looks correct to me? Do you mean [docusaurus.io/tests/blog/rss.xml](https://docusaurus.io/tests/blog/rss.xml)? Yes I'm wrong 👍 `link: normalizeUrl([siteUrl, permalink])` => forgot permalink contains the baseUrl already

yes, apparently we have a larger problem 😅 we'll look into it

Probably not a regression, this is what we had before: https://deploy-preview-5000--docusaurus-2.netlify.app/ 

Hey We definitively want to support that, and we've discussed it in a few issues already. This is not the navbar, but we'd also want custom items in other places...