Martin Donath

> There's also the separate matter that there is a "material/typeset" plugin (not public) that was relying on the behavior that Markdown is being ignored/preserved as it's being moved to...

> The most helpful feedback that I'd like to see is what value of title you expect to see for a given input Markdown. Ideally a title without Markdown formatting...

I second @ofek – it would be great if this could be sorted out. IMHO, it is a pretty severe bug that causes a lot of frustration among users and...

This was closed without comment. @oprypin could you please explain why?

Title handling is broken since MkDocs 1.5 (see #3357). There are some instances where markup ends up in `Page.title` (see linked issue). Should `Page.meta.title` be allowed to contain markup? Plugins...

Honestly, I'm having a really hard time committing to anything with "yes" or "no" right now, because there are so many changes related to title handling in the making that...

Have you tested compatibility with plugins that augment the serve capabilities of MkDocs? For example, the mkdocs monorepo plugin provides a [consolidated serve mode](https://github.com/backstage/mkdocs-monorepo-plugin/blob/b1965a216af41c7e503753c63551d894fac8399d/mkdocs_monorepo_plugin/plugin.py#L74-L100), same as the [projects plugin](https://squidfunk.github.io/mkdocs-material/plugins/projects/). __Edit__:...

I'd vouch for removing `changefreq` altogether. It's optional anyway, and I doubt that any of the big relevant search engines will use it when deciding when to re-index your site:...

I'm fine with that as well, but the problem is that you'd need to go through all keys and check if it's a path to an actual file, which is...

We could definitely try that, jup. But I think it wouldn't hurt to add `!resolve` as well.