Core taxonomies Post Tags Categories Link Categories Menus
They describe your content. The difference between tags and categories is hierarchy. Topics People Cities Cities Content: Travel blog Cuisine Content: Restaurants Songs Content: Concerts Actors, Directors, Producers Content: Movies
Custom taxonomies are not new Database schema — WP 2.3, Sept. 2007 Custom taxonomies — WP 2.5, March 2008 Partial UI — WP 2.8, June 2009 In WP 3.0 — full custom UI implementation So basically, they’re now on steroids.
Evolving Theme Development get_template_part() It’s basicallyinclude()on steroids. Example: get_template_part('loop', 'archive'); Process: Check for loop-archive.php. Check the child theme first, if applicable. Otherwise, check for loop.php. Less Redundancy FTW.
get_template_part('header', 'home'); Is like calling: get_header( 'home' ); Same deal: header-home.php,then header.php.
What’s with thetheme improvements?In 3.0, we weretheme developers.
WordPress Multisite The WPMU fork was merged Massive merge sprint, followed by cleanup Terminology/concept nightmare TODO: Network admin UI improvements TODO: Easier to manage, use, and install (in that order
Oh no, please don’t. define( 'WP_ALLOW_MULTISITE', true );
Other cool features Pick a username/password during install comment_form() and wp_login_form() Stronger authentication security by default Bulk update plugins and themes “Search Engines Blocked” Rewritten initialization code
Follow along #wordpress-dev on freenode.net http://wpdevel.wordpress.com http://core.trac.wordpress.org wp-svn– mailing list for commits wp-hackers – plugin and core developers wp-testers
What might be next Column sorting and a more AJAX feel More features for custom post types and custom taxonomies Support for custom comment types Better support for custom post statuses Media/upload overhaul Incremental admin, DRY, UX changes Incremental improvements to multisite Links as a post type Roles/capabilities overhaul
Preferences have a cost. Too many means you can't find any of them. They damage QA and testing. They make good UI difficult. They confuse users. Do something specific and do it well. Defaults that work will lead the UI in the right direction.
The quality of an interface design is inversely proportional to the number of designers.
If you're too lazy to do the homework and think through the big-picture rationale, I'm too lazy to add the feature.
In the presence of good rationale, maintainers should be willing to change their mind often.
QualysBlindElephant BlindElephantis a web application fingerprinter. Drupal, Joomla!, Liferay, Mediawiki, Moodle, MovableType, osCommerce, phpBB, phpMyAdmin, phpNuke, SPIP, WordPress
96 percent JOOMLA 1.5.20 Versions < 1.0.15 and < 1.5.17 are critically insecure. Version 1.5.17 was released 3 months ago.Percentage of installs running a critically insecure version?
69 percent (and up) DRUPAL 6.19 Versions < 5.22 and < 6.16 are critically insecure. Version 6.16 was released in March. Versions 6.18 and 5.23 were critical security fixes released last week.Percentage of installs running a critically insecure version?
4 percent WORDPRESS 3.0.1 Versions < 2.5.1 are critically insecure. (Released in April 2008.)Versions < 2.8.3 are insecure. (August 2009.)Percentage of installs running a critically insecure version?