Consider using mkdocs material

[hypergonial]

Summary

We should consider using mkdocs material for the documentation.

I have the following reasons as to why:

• Much better search that is very responsive
• Nicer looking interface
• The entire site doesn't have to reload for every navigation (Instant Navigation)
• Highly extensible and customizable
• Properly builds objects.inv so it is actually usable by other repos
• Supports advanced markdown features such as tabs & admonishments (full list)
• Is also supported by readthedocs so documentation versioning & deployment should be simple

Why is this needed?

The current documentation is very slow to load, the search is not very responsive (if it works at all), and objects.inv is almost completely unusable by other documentation generators.

Ideal implementation

Something like this

If given the go-ahead, I'd be willing to work on a PR to switch the documentation to mkdocs-material with a similar configuration as the one I use, linked above.

Checklist

• I have searched the issue tracker and have made sure it's not a duplicate. If it is a follow up of another issue, I have specified it.

[parafoxia]

I can vouch for MkDocs Material -- I use it myself and it's wonderful.

[hypergonial]

I can vouch for MkDocs Material -- I use it myself and it's wonderful.

Way ahead of you already, PR is almost done :p

[parafoxia]

Oh yeah so there is, didn't see that lmao.