It would be better to include your own CSS file that way you can: Use a relative path to your CSS. Avoid problems getting the path right to the wp-admin directory. Not all people put WordPress in the root directory, so your example above would break for them. Possibly redundancy by reusing the CSS in … Read more
Great question. There is no generic and comprehensive documentation workflow in WordPress circles. However there are some nice tools and options to make use of. readme.txt Markdown-based machine-readable file. It’s main purpose is to be parsed and presented by official plugin repository, but it’s not too convenient outside of that. It is great and fitting … Read more
You’re going to have to go with some plugins. The WordPress page editor is dog slow. Throw more resources at it and/or disable some functions from showing under the “Screen Options” tab. It should not really be slow unless your have a ton of people working on a ton of pages at same time, if … Read more
You may want to take a look at the code itself: https://core.trac.wordpress.org/browser/tags/4.8/src/wp-includes/user.php#L1376 The above links to a documented list of the meta generated when WordPress generates a new user in the wp_create_user function. From these comments I pulled a quick list: user_pass, user_login, user_nicename, user_url, user_email, display_name, nickname, first_name, last_name, description, rich_editing, comment_shortcuts, admin_color, use_ssl, … Read more
Interconnect/Spectacula folks manage free WordPress User Guide for training users.
To partly answer my own question: As mentioned in this git issue you can use console.log(wp.blocks.getBlockTypes()); in the browser console after all the Gutenberg magic loaded (e.g. in the editor window of a post) to show all currently registered blocks, inluding their attributes. Another Info-Source: The Git-Project of Gutenberg holds all core blocks and their … Read more
There is no such documentation, and I don’t expect one anytime soon. WordPress could implement specialized property objects for these cases, for get_taxonomies() it could look like this: class WP_Taxonomy_Properties { private $data; public function __construct( Array $data ) { $this->data = $data; } public function get_labels() { return $this->data[‘labels’]; } public function get_description() {} … Read more
Function doc block should document what it does, what it might be useful for, but not who uses it. It makes sense to document that it was designed with hook X in mind but that is it. Think of unit testing. In that context you are likely to call the function by itself without doing … Read more
VTC and Lynda have very good training videos on this.
Not at the moment, but, you can go to a page with the block editor, open the browser dev tools, go to the console, and run the following: // grab all block types const types = wp.blocks.getBlockTypes(); // filter to just the core blocks const core_blocks = types.filter( type => type.name.startsWith( ‘core/’ ) ); // … Read more