<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Hey all,</div><div><br></div>There are many websites out there that automatically parse the phpdoc of trunk, creating a very complete, although very big, documentation of WP core. <div><br></div><div>Examples:</div><div><br></div><div><a href="http://phpxref.com/xref/wordpress/_functions/index.html">http://phpxref.com/xref/wordpress/_functions/index.html</a></div><div><a href="http://wpseek.com">wpseek.com</a></div><div><br></div><div>On <a href="http://WP.org">WP.org</a> there is this: <a href="http://phpdoc.wordpress.org/trunk/">http://phpdoc.wordpress.org/trunk/</a> which catalogs code in a similar manner.</div><div><br></div><div>I'm wondering why functions and their phpdoc are not hooked into the Codex at all, at least have pages made automatically for functions. It wouldn't clog the codex by creating tons of pages, because these functions won't be in a huge list anywhere, however where deemed appropriate functions can be linked to from the Functions Reference or anywhere else.</div><div><br></div><div>Perhaps a similar process could be employed for actions and hooks.</div><div><br></div><div>The reason I bring this up is because I just used media_sideload_image in a project I'm working on and realized there wasn't a Codex page for this function, which I made immediately. It would've been nice to at least have the PHPdoc there waiting for me, which I used to make the basis of the page.</div><div><br></div><div>Eric Lewis</div></body></html>