I'm personally a fan of adrdox because it shows a lot more things that are interesting for users as well as custom parsing code that adds things which aren't emitted in the ddoc output. Maybe we should switch to it for the documentation generation? Then we can also configure it on the dub package and could add extra custom documentation pages as well as customize the styling.
In the README for a while we had https://libdparse.dlang.io linked to but on the DUB package page there is the auto-generated documentation using dpldocs (adrdox): https://libdparse.dpldocs.info/v0.20.0/index.html
I'm personally a fan of adrdox because it shows a lot more things that are interesting for users as well as custom parsing code that adds things which aren't emitted in the ddoc output. Maybe we should switch to it for the documentation generation? Then we can also configure it on the dub package and could add extra custom documentation pages as well as customize the styling.
Opinions? @Geod24 @Hackerpilot