Figuring that to do about api documentation
api.kde.org is a mess and sysadmins want to have a replacement ASAP, maybe we could move the api documentation to developer.kde.org, this would provide a real unified portal for all the developer projects.
I have a small proof of concept for the KDAV API here: http://kde.carlschwan.eu/api/kdav/classes/
It uses doxybook2 to generate Hugo markdown, but there are multiples problems:
- Output is not at the same quality as the current doxygen output.
- There are bugs in doxybook2 and that needs to be fixed upstream: e.g. no support for enum class -> crash
Maybe it could be worth seeing if integrating doxygen xml output is easier and less hacky.
This is probably not an immediate goal of developer.kde.org but something that would be nice to have with a global search function.