Hello reader.

I started working on this project in 2020 simply because I used it, and original author stopped working on it (and was kind enough to give me write access). I spent quite some time reworking a lot of the code (like merging the core back into the repo, merging PR, fixing bugs and updating very outdated things).

When designing APIv2 for my app, I switched to OpenAPI specification, which is much better than documenting the API in source code comments like what apidoc does. It also allows me to generate client code directly from the spec without having to do anything.

My point is that nowadays I would recommend using OpenAPI spec to describe your endpoints, and then whatever doc engine you wish to use. But the important part is that now I do not use apidoc anymore.

Which means I don't have the incentive to maintain it for free, answer issues, fix bugs, etc...

I'm effectively stepping out of maintainer status for this project.

Now that you know that apidoc is not really maintained, it might be a good time to re-evaluate your choices regarding the tech stack for api documentation.

Best regards,
~Nicolas