The thing about having a "Codex" is that all the information is *instant*. For example, here's what I get when I Google `tpl_link`:
http://xref.dokuwiki.org/reference/dokuwiki/nav.html?_functions/tpl_link.html
In my opinion, that's super useful if you're a core DokuWiki developer because BOOM you know where it is and how many times it appears, but for someone building templates or someone who doesn't really know DokuWiki that well (me) they just want to know what it does and go back to coding. When I click the link I can see more information, but it's on the same page as other functions and it's distracting...and I know that sounds silly but for someone who is unfamiliar with DokuWiki the less the better.
Here are some examples of Docs I use everyday that are super helpful (and of which I modeled the template off of):
*
http://codex.wordpress.org/Function_Reference/wp_nav_menu
*
http://underscorejs.org/
*
http://www.php.net/var_dump
*
http://api.jquery.com/closest/
Each of those also have xref or similar, but detailed docs is what makes it user-friendly.
Also I think each function should live in its own page so the community can stuff it with examples or link to tutorials.
@turnermm I've implemented most of those and turned it into a starter template: (see bottom of
https://www.dokuwiki.org/codex )
#2 would be awesome, because I'm sure once I understand DokuWiki better I'll be using the Xref more and more
Automating it would definitely give us a head start...honestly I didn't know how many functions/methods there were before I started haha I'm usually way ahead of schedule at work, so I can knock one out here and there when I'm not busy with anything else. It shouldn't really take more than a few weeks to do everything other than the examples