Martin Donath

@pawamoy You're right, this should probably be handled as a separate issue. However, I thought it might be useful to start a discussion first, whether this would actually be considered...

I've thought about this for a while now and currently see two options: ### Options #### Option 1 – Move business logic and `readthedocs` theme out - `mkdocs` (depends on...

> I will add one counterpoint to this. Moving the `readthedocs` theme out will be a breaking change for some users. Excellent observation that slipped my attention. When following option...

@tomchristie I'm not sure I follow. As I understand from what you write, you're proposing to follow what I described as __Option 2__: move both themes out. Have you considered...

A crossover of __Option 2__ and what @tomchristie suggested in https://github.com/mkdocs/mkdocs/issues/3636#issuecomment-2064427861 #### Option 3 – Move everything out and convert `mkdocs` to a shell - `mkdocs` (has `mkdocs-classic` and `mkdocs-readthedocs`...

@pawamoy excellent idea – vendoring could be a viable deprecation path ✌️ @tomchristie Okay, let me try to interpret your beautiful prose 😅 It sounds like you're suggesting to move...

If we'd opt for vendoring, we'd end up with two themes with the same name, so we'd need to make sure that precedence works in our favor, similar to what...

Great feedback. `site_url` and `use_directory_urls` are definitely settings that users often have trouble with. The problem is that building documentation to look at from your file system, and building documentation...

[MagicLink](https://facelessuser.github.io/pymdown-extensions/extensions/magiclink/) might be useful here (I did not test it)

> To be honest, knowing that `` can be used to allow any URL, it makes something like requiring a space before titles less pressing. Embarrassingly, I did not realize...