I believe there is a way to semi-automate API docs using ReadTheDocs even for PHP. If there is, you should definite look into that. I would much prefer to have all of my docs in one place. But if that isn't really feasible, then write some kind of directive or extension or whatever to RTD/Sphinx that makes it super easy to link to API docs from a class/method name.
[ ] Create a new branch to test this little experiment on
[x] Install/require sphpdox/sphpdox (I tried generating API docs with this lib and it gets me about half-way there. Just need to fork it and customize it to my needs)
[x] Fork sphpdox/sphpdox
[ ] Use your forked version (nozavroni/sphpdox) rather than sphpdox/sphpdox (going to need to look up how to do this without adding a new packagist package for "nozavroni/sphpdox". I know there is a composer option to do it...
[ ] Add options from ApiGen if possible
[ ] Add option to include syntax-highlighted source code for doc'd classes
[ ] Add option to generate class tree
[ ] Add option to include public, protected, and/or private methods/properties
[ ] Update class page--needs to generate more useful class pages
[ ] Update main index--make it more like ApiGen's home page
[ ] Just look at what ApiGen generates and see if you can get sphpdox to do pretty close to the same thing
[ ] Actually now that I think about it, the reST it generates should be like some kind of index/reference. It shouldn't be a part of the main documentation. It should be an index that comes after the other docs that the main docs can reference as needed.
I believe there is a way to semi-automate API docs using ReadTheDocs even for PHP. If there is, you should definite look into that. I would much prefer to have all of my docs in one place. But if that isn't really feasible, then write some kind of directive or extension or whatever to RTD/Sphinx that makes it super easy to link to API docs from a class/method name.
sphpdox/sphpdox
(I tried generating API docs with this lib and it gets me about half-way there. Just need to fork it and customize it to my needs)CSVelte\Flavor
or :api:csvelte/flavor
or something along those lines...