Hello!

I have come to my third and final migration from Sphinx to MkDocs, which I expected to be the simplest of the three. I was, however, quite incorrect. This is shaping up to be the most complicated.

The existing documentation makes liberal use of the Sphinx .. class:: directive to "manually document a class that doesn't exist in a .py. file". As I understand it, it takes the information provided in the .rst file, and formats it the same way it would use autodoc to format class documentation pulled from the source code. So, it renders attributes/parameters etc included in the reStructuredText as it would if it was being pulled from a docstring in a .py file.

I'm not seeing anything obvious as an equivalent to this available for MkDocs, at least not through mkdocstrings, which is what I would at least assume it would be associated with. To that end, I have questions.

1. Is there some equivalent to the .. class:: Sphinx directive that I'm missing?
2. If not, is a custom mkdocstrings extension a possible solution here? I'm unclear on exactly what extensions can do, so I'm not sure if they make sense for this.
3. If an extension isn't the right route, do you have any other suggestions as to how I can go about appropriately handling this documentation?

The inelegant, and less-than-ideal answer is to include the content in the Markdown with some kind of identifier that can be used with CSS, and style it manually to make it look like the class documentation. I would prefer to avoid that for a long list of reasons.

Thank you for your time!