René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"refactor: Stop relying on the template fallback mechanism?","articleBody":"The fallback mechanism is sometimes confusing when overriding templates and using a theme different than the fallback one. For example if one uses the `nature` theme, they have to use `nature` in the path of custom templates, instead of `material`, even if the `nature` theme doesn't even exist in mkdocstrings-python's sources.\r\n\r\nIt might be even more confusing with the [extended templates feature](https://mkdocstrings.github.io/usage/handlers/#handler-extensions) recently introduced by mkdocstrings (which by itself could be a mistake too :see_no_evil:).\r\n\r\nAlso, MkDocs wants to create a new default theme, as well as moving the classic and readthedocs theme out of core, see https://github.com/mkdocs/mkdocs/issues/3636.\r\n\r\nWhat I suggest for mkdocstrings, or mkdocstrings-python at least in the short term, is that we stop relying on the fallback mechanism, and either entirely support a theme, or not at all, whether directly in mkdocstrings-python's sources, or in external packages. I'm not sure yet how we would handle dependencies then: `mkdocstrings`, `mkdocstrings-python`, `mkdocstrings-python-material`...  ","author":{"url":"https://github.com/pawamoy","@type":"Person","name":"pawamoy"},"datePublished":"2024-04-23T19:10:40.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/152/python/issues/152"}