You don’t document function calls, but function definitions. Because the function could be called unlimited times, right? So it makes no sense to document functions when they are called. If you document the call, then probably because you do some things you want to remember later – or let other following developers know. But normally, … Read more
I’m not aware of any besides michel fortin’s WP text flow diagram from a few years ago: http://michelf.com/weblog/2005/wordpress-text-flow-vs-markdown/ That said, there were recent talks about writing some kind of plugin dev’s companion reference with the full flowchart of the WP hooks and API.
http://codex.wordpress.org/Javascript_Reference/wp It’s a work in progress. Contribute if you can!
WordPress is very… utilitarian I suppose. People tend to use and know as much as they need to get things done. Curiously that tends to exclude the low level core load process. It doesn’t help the situation that (unlike modern frameworks) WordPress doesn’t use a complete routing logic for everything. Front-end is governed by rewrite/permalinks, … Read more
The difference is really no difference in regular (single install) WordPress. It’s in a multisite install (network) where there is a difference. In multisite, only a Super Admin (who can manage everything on the network) has delete_users capability, while an “admin” (who would own/manage a single site) can remove_users from their site, but cannot delete … Read more
If you look into the source code for getEntityRecords, you’ll see that the the core/data library creates entities using the WordPress API in entities.js. So you can use any parameter available in the REST API. Here are options for posts: context page per_page search after author author_exclude before exclude include offset order orderby slug status … Read more
(hmm this is somewhat off-topic, but will let others decide on it) Better answer Although it is hard to track official announcement, as @darmb pointed out in the comments there are indications that the official documentation effort is drifting away from the codex in favor of the developer site, and the “make” blogs/sites. So in … Read more
When I added the drawbacks to the Codex, I was mainly thinking of using the ‘request’ filter as an alternative to query_posts(). That filter is only run for the main query, so that solves the problem with ‘pre_get_posts’, which fires for every query. The downside is that you don’t have access to query flags like … Read more
I Use a much faster and easier way to create a local copy of the codex without installing a local server and without installing copy of mediawiki, its called ScrapBook which is a Firefox extension, that helps you to save Web pages and manage the collection. Key features are lightness, speed, accuracy and multi-language support. … Read more
Probably you are looking for JavaScript™ for Acrobat® API Reference. This reference should be the most complete. But, as @Orbling said, not all PDF viewers might support all of the API. EDIT: It turns out there are newer versions of the reference in Acrobat SDK (thanks to @jss). Acrobat Developer Center contains links to different versions of … Read more