Reading this I had the impression that I get to choose the method, but after reading the guide It seems this isn't the case, or is it? How can we make that clear? Plus I think it's misleading having outside links in the same pattern of navigation TOC right after on "Usage"

It depends on the use case, but you don't have to stick with only one method. You can create a window by configuring tauri.conf.json and then use JS or Rust API to dynamically set up the window later at runtime.

Since I have read it so many times from 1.0 guide, it already feels normal to me 🤣 But I do agree it can be better,

Since I have read it so many times from 1.0 guide, it already feels normal to me 🤣 But I do agree it can be better

So yeah, this is first time ever I'm consciously reading about window customization and my first perception was that I stated above 😅. Let's call @dreyfus92 to see his opinion on this PR

To make things easy, we can just slap a "external" icon <Icon name="external" /> on each "Configuration" entry, so as not cause confusion with a page navigation TOC

Ok, I just added it.

<svg> in mdx were set display: block, the icon and the link will separate into two lines, so I add a custom class .inline-icon to custom.css and force the <Icon> here to use display: inline-block