Yep, so the idea would be to generate the structur...

# dokka

[apatrida]

Yep, so the idea would be to generate the structure of the documentation that has the information from the doc parsing which is basically the structure, with references, and fragments of markdown AST carried in the tree, and some things like [DataType] links would just be normal links in the AST with special link format "fqcn:uy.kohesive.klutter.SomeClass" which can be looked-up from a reference table elsewhere when rendering. Then people can provide indexes of classes outside of the current doc generation that can still be linked by reference. Then a template function organizes the output, and a format draws it. But the format must be in control of everything (escaping, whether LF or <br/> is used in a given nesting level, and more).