Waylan Limberg

> * Input: `Title *title* title :material-book:` > MkDocs 1.4: `Title *title* title :material-book:` > MkDocs 1.5: `Title title title ` I would say the last one would be most...

The existing prioritization is based on the idea that explicit trumps implicit. If a user explicitly defines a title for a page (in nav or meta-data), then that title is...

> why on earth would the user specify the meta title if it's impossible for it to be used if the site specifies titles in the nav config Some more...

And how does this proposal address the issues raised in the first comment on #3560?

I can't make out the issue with the 2 remaining mypy errors.

The current lint errors appear to be related to a new [markdownlint rule](https://github.com/DavidAnson/markdownlint/blob/main/doc/md055.md) that was [added](https://github.com/DavidAnson/markdownlint/commit/30d62f19acf237c3ec017e660960389881cbd06b) in the most [recent release](https://github.com/DavidAnson/markdownlint/blob/main/CHANGELOG.md#0330). Presumably the various tables in the documentation need to...

Thanks for the feedback. I have made all of the changes... except for the one where we are meeting lunr.js' API. I think this is ready to go.

> 1. I don't see how the changes in this pull request cause a need for this new feature. I don't think they do. > For `` # `foo(bar=0)` ``...

> However, I think this diff is for the negative: Yes, and that is why I added keywords. Lets take this diff: ``` diff - documentation_pages + \n documentation_pages(*, inclusion:...

> Here's what you get when searching for `InclusionLevel` with this change. Let's run with that. Right now, today, without my proposed changes, on mkdocs.org, if you search for `InclusionLevel`,...