I started to tweet some comments. I even considered commenting on Tony Perez’s blog post, WordCamp San Francisco 2012 Sponsorship Packages–Kettle Meet Pot, which is a great title. However, when I started to tweet, I ran out of characters. When I started to comment, I realized I had too much to say.

So…to me the drama boils down to a few things, really one thing: Leadership. First, the WordPress community is made of leaders and entrepreneurs, some great ones too. Second, change in an ever-changing world, especially among startups and entrepreneurs can be difficult and unsettling. Also, branding, messaging and change leadership from the WordPress Foundation and/or Automattic has had glimmers of excellence but it also has been somewhat confusing and at times misleading. Third, internal inspection both personally and corporately (pun intended) is integral to growth. And finally, the WordPress community is the trophy of WordPress, and as such the community needs to feel heard and action taken (and yes no action is an action).

The WordPress Community Consists of Leaders and Entrepreneurs

WordPress developers and designers and companies that profit from WordPress are used to being entrepreneurs. They have an entrepreneurial spirit. They are visionary leaders and have a plethora of ideas on how WordPress should do things. WordPress even encourages the creativity and innovation in the community.

Most companies are run by one or two individuals and are relatively small, even Audrey Capital fits the bill. Automattic is not even that big of a company with 108 dispersed (dare I say semi-autonomous) employees. And even those employeed by companies do freelance on the side. As such, many are their own bosses. They are the kings of their castles and the lords of their serifs serfs. Some have even said that they started their own companies because they didn’t want to report to or work for the Man (generally speaking and not about Matt). However, these chiefs are being told by another Chief (and a CBBQTT at that) what they can and cannot do, and that could even be miscommunication, misperception, and misunderstanding. And some times, many times, these decisions on the direction of WordPress are not very popular. That’s the stark nature of leadership. However, as the saying, “As iron sharpens iron,” so does one leader sharpen another leader, where there is sharpening, there will be sparks flying.

With WordPress, Matt is still the King. He heads the Foundation, started Audrey Capital, and AutoMATTic. He is THE co-founder. And as such, he pretty much controls and commands the future of WordPress until some sort of successful mutiny occurs, which I doubt the WordPress community would even allow. Thus, Matt is the Leader of everything WordPress, whether he wants it or not (and like most leaders, at times he probably doesn’t want it). So it’s a leadership clash. It’s a test of leadership fortitude.

The outcry is really an expression of feelings of unfairness and/or misunderstanding—sometimes jealousy. And no one, though they will try, can say that those feelings are wrong, bad, and/or misplaced. They simply are. However, Matt, Jane (just because she’s the most outspoken), and the other WordPress leaders, whomever they may be, can choose to lead and lead well through this—or not. Yet, I must remember that Matt was/is first a coder, a blogger a photo blogger. As Matt grows, so does Automattic. And so does WordPress, and the WordPress community benefits. So in summary, there are three groups of leaders: (1) One group (consisting of mostly the WordPress community) saying that something is not right, let’s talk, discuss, and move forward for the benefit of the WordPress community; (2) One group (consisting of both the WordPress community and the Foundation) fighting back point for point trying to dismantle each other; and (3) The WordPress Foundation sponsoring and putting on WordCamp San Fransisco and moving on with the business at hand. And frankly, it’s the third group that has the power (right now) and the other group (the vocal minority dissenters) are willing to respond, discuss, negotiate, and understand the Foundation. Really the community is asking for clarification from the Foundation.

Change Leadership from the WordPress Foundation

While WordPress is OpenSource and has grown as a result of the community, it doesn’t mean that there is some sort of group conscience or anarchian (I don’t even believe that’s a word!), even democratic movement and decision-making. No, there are processes. There are principles. There are people. And there is an organization and a network. These processes and principles are sometimes public and sometimes private and sometimes known, sometimes unknown, even by the ones making the decisions. There are principles in play that are very present among the community but not among the leadership and vice versa. There are the rules and there are unwritten rules. In organizations, processes change and principles change because the leader and times change. While we can debate and argue freely about whether the process and/or principles should have changed, should change, should change back, or even how it changed, the fact of the matter is that change happens. Good. Bad. Or indifferent. Simply, yes. It is what it is, and as an adult, I have a choice and the ability to respond, not just react.

So change is to be expected and even welcomed as it shows growth (or sometimes decay). For most people, though, change is difficult, hence the importance of communication, messaging, and discussions. Change leadership from the WordPress Foundation and/or Automattic has had glimmers of excellence, but it also has been somewhat confusing and at times misleading though I am sure that was never the intent. WordCamps probably did need some level of constraints placed on them, which was probably initiated by risk management and lawyers. Yet the risk one lawyer is willing to take is different from another. Likewise, the legal risk one company is willing to take is different from another. Thus, the WordPress Foundation responded according to the advice they were most likely given as well as what was most comfortable in regards to risk management.

And then WordCamp San Francisco (WCSF) suddenly announces their sponsorship packages. And that’s exactly what we have with WordPress SF: a sudden change. It’s a quick, unannounced, an precendented shift from what’s been communicated by the Foundation since the last WCSF as well as the many assumptions made based on what was said explicitly and implicitly. There was nothing said or implied to the community that this would happen. Anyone who has worked in communications or public relations would have seen that this would cause a stir in the community. Then if the WordPress Foundation, i.e. Matt, decided that he wants to move in that direction, change communications could have been planned and communicated. And it would have been received better than it was.

However, I bet (I’m hoping) that no one at Automattic, WCSF, Audrey Capital, or the WordPress Foundation even thought this would be an issue. Why? Well in their minds, there is a separation between WCSF and the “other” WordCamps. It has been said that the community knows that WCSF is different, and thus needs no justification. Apparently this is probably not the case, especially among WordCamp organizers. Several WordCamps probably see themselves as incredibly important. Some that have taken the attention of the community. However, even my involvement at WordCamp Atlanta, I see so much more potential and believe that WordCamp Atlanta could easily bring in an international audience and be over 1,000 people. It’s airport is perfect for it as is NYC, Chicago, and San Diego. So the point of the community is not necessarily the sponsorship levels even. That’s just the last straw for one person. It’s the the inconsistent, discretionary application of the constraints upon WordCamps, rather and apparently non-SF WordCamps v. WCSF. The measures and constraints placed on the various WordCamps may have been needed, may still be needed; however, the leadership has not given good answers to why WordCamps are being limited financially and even physically. It’s really an us v. them environment, which is surely not the goal of the Foundation or anyone involved with WordPress. Instead, proper and open lines of communications could have easily prevented this.

Simply, “What we’ve got here is (a) failure to communicate.” The WordPress Foundation have not stated explicitly and officially that WCSF is different (even though Jane has written her piece last year), why it is different, and the rules that WCSF will follow. If the WordPress Foundation sees “local” WordCamps (e.g., WordCamps that are not in SF) as WordCamps on a smaller scale and want to keep them small, then the decision as well as the rationale needs to be communicated. It needs to be declared that these are really not that much different than WordPress Meetups. Simply, the Foundation would need to answer the questions like, “Why can’t we put on a WordCamp just as good in ___?” And really this is more about the vision of WordCamps than anything else. And “where there is no vision, the people perish.” Really that proverb is more about where there is no captured, received, and accepted vision, the people will fall off. They will do what’s right in their own eyes if there is no vision and/or mission. And because WordPress, as an open source project, is a sociological loose confederation of sorts with many, many autonomous groups and sub-groups, it is imperative that there be some vision. Hence the talk, the State of the Word is so important and is received at WordCamps again and again.

Self-Inspection

Socrates said, “The unexamined life is not worth living.” The same can be said of companies and of WordPress/the Foundation. The unexamined company is not worth pursuing, leading or developing. WordPress does a good job of continuous improvement with Trac and the community. However, the leadership side of the coin is another matter.

I don’t know Matt from Adam, and Matt does know me from Adam. Though we have met, he probably doesn’t remember, nor do I expect him to remember as our meeting was unremarkable. And I seriously doubt that a blog post in the deep blue ocean will make any difference in that (I even doubt he’ll read it) and that is not my intent either. However, that does not mean that Matt doesn’t know me…that he won’t read this post…that’s just my perception and my expectation. Likewise, many of us have expecations and perceptions that just may not be true. We see only dimly. We see what we want to see. We see things how we were raised to see them. Our personal experiences, perceptions, principles, and expectations highlight ourlives, as well as darken them.

If we look at ourselves and our own companies, designs, developments, products, outputs, etc, many of us have the same or similar reaction that the WordPress leaders have reacted when our stuff is criticized. Some of us say nothing. Some respond rather loudly. Some respond acutely and cogently. Some respond quickly. Some don’t respond. Some stoic. Some indifferent. Some bitter and resentful. Some become the Honey Badger. Simply take a look at Tony’s post to see, and notice the Twitter reactions there about as well.

The outcry, the expressed frustration by many well-known WordPress leaders (Carl Hancock, Gravity Forms; Lisa Sabin-Wilson, WordPress for Dummies; Brad Williams, author of Professional WordPress; Dre of Sucuri) is not threatening to WordPress and the leaders–though it can be misconstrued as such. The frustrations and emotions rise and fall, and frankly it’s been a while since the last WordPress drama, well unless you consider the comic drama by the Honey Badger or Pink Pony. In all seriousness, I believe the last bit of drama was when Kevinjohn Gallagher left the WordPress community rather publicly. But these things are not threatening to the WordPress Foundation, nor are they meant to be. Instead, they serve as opportunities to change and grow even more, even if we/I disagree with that change in direction. That’s the prerogative of the leadership.

My only hope is that the WordPress leadership is more aware and proactive in their leadership.

The WordPress Difference: The Community

The thing that sets WordPress apart from many organizations is that the WordPress community is a living, breathing community in a state of constant flux. Even Matt has said that WordPress will walk to the beat of its own drum adapting when it’s ready, not when the Silicon Valley dictates that it should.

The WordPress community is great. It’s self policing. It’s responsive. It’s growing.

I’ve heard individuals say things like, “Matt/WordPress shouldn’t forsake the people that have made it.” While that is true, the flip is also true: The community that has made WordPress shouldn’t bite the hand that feeds it. However, if we drop the finger pointing, bickering, and look at the reality of the situation, then the community can change, can grow, and can flourish even more.

Everyone has a choice. Everyone has a choice to use WordPress or to abandon WordPress. Everyone can choose to follow the WordPress licensing or not. Everyone has a voice, and you can use that voice however you’d like. You can talk publicly or privately. You can blog, share photos/graphics/infographics, create sites, etc. to express your voice. You can do it entertainingly. You can do it shamefully. You can do it however you want.

Yet it is very true that the community has made WordPress in more ways than WordPress has made the community. However, it should never be an us v. them mentality as many real life community organizers and leaders do. Instead, the Foundation exists to serve the community (“the public good”). And as such the WordPress Foundation’s leadership can be measured against a servant leadership model, which essentially asks, is the foundation serving the public good or the Foundation good?

In functions.php or your core functionality plugin where you created the custom post types, enter this code:

add_action( 'genesis_before_post_content', 'wps_do_post_image_check' );
/*
 * Remove genesis_do_post_image() action if on post type archive of
 * a custom post type
 *
 * @global stdClass $post Post object
 * @uses genesis_get_option() Gets the genesis option for content archive thumbnails
 */
function wps_do_post_image_check() {
	global $post;
	if ( ! is_singular() && genesis_get_option( 'content_archive_thumbnail' ) && is_post_type_archive() && ! in_array( $post->post_type, array( 'page', 'post', 'attachment' ) ) )
		remove_action( 'genesis_post_content', 'genesis_do_post_image' );
}

NOTE: Though posts, pages, and attachments by default do not have archive pages, I cannot assume that in this code snippet.

Check out these features:

• Fully responsive FlexSlider
• Incredibly efficient
• Handles multiple instances (seen below!)
• Sleek and sexy UI
• User-friendly AND Developer-friendly

Default Slider

Here’s an example:

So here’s how I created that:

1. Uploaded my images.
2. Sorted my images.
3. Determined the size of my slider.
4. Clicked Publish.

Custom Slider

For developer’s, the many hooks (57) and filters (34) in the code make it extremely easy to customize. So whatever the issue or desired change or needed change, you can easily adapt soliloquy to do what you want and not have to worry about an update eradicating your changes.

In about 30 lines of code, I was able to do this:

I have converted this into an add-on, which Thomas will be developing even further to add some additional features.

Lightbox Slider

Thomas has already released the first add-on for developers. This add-on is sweet!

Multiple Height/Width Images Slider

However, this does require that you add a line (or 3) to your CSS.

.flex-container {
	max-height: none !important;
}

Upcoming Add-ons

As I mentioned previously, the thumbnail with an external/public API is forthcoming. Another add-on, once Thomas figures out some AJAX stuff to sweeten it a bit more, is the preview add-on. Previously, you had to refresh the page the slider resided to see the slider in action. With this add-on, you can click the Preview button, just like Posts and Pages, OR look in the Preview metabox to see the slider. In version 1, most likely, it will just be the slider upon publish or save or update. In version 2, Thomas hopes to have it display changes made immediately via AJAX. It truly will be sweet!

And finally, the Featured Posts Add-on. And as you can see it can integrate with Thumbnails. I still need to figure out the best way to integrate Lightbox, but that will be version 2.

Get Soliloquy!

On almost every install of WordPress I do, I now have at least 2 custom post types: Tweets and Bookmarks.

Since I have this in a plugin, I am using a constant for my URL base:

define( 'WPSPS_URL', WP_CONTENT_URL . '/themes/my-child-theme-folder' );

First, there is the creation function. This creation function, which I call wps_create_post_types() is the only function that I ever edit, really append.

add_action( 'init' , 'wps_create_post_types' );
/**
 * Create Post Types
 *
 * @link http://codex.wordpress.org/Function_Reference/register_post_type
 *
 */
function wps_create_post_types() {
	$post_types = array(
		'Tweet' => array(
			'rewrite' => array( 'slug' => 'tweets' ),
			'menu_icon' => WPSPS_URL . '/lib/images/tweets_16x16.png',
			'description' => 'Twitter Archive (@wp_smith)',
			'supports' => array( 'title', 'editor', 'custom-fields', 'post-formats' ),
			'taxonomies' => array( 'category' , 'post_tag' , ),
		),
		'Bookmark' => array(
			'rewrite' => array( 'slug' => 'tweets' ),
			'description' => 'Bookmarks',
			'supports'    => array( 'title', 'thumbnail', ),
			'menu_icon' => WPSPS_URL .'/lib/images/bookmarks16x16.png',
			'taxonomies'  => array( 'wps_bookmark_category', 'wps_bookmark_tags' ),
		),
	);
	foreach ( $post_types as $title => $args ) {
		wps_register_post_type( $title , $args );
	}
}

So what’s going on here is that I am cycling through the post types array registering each post type with a helper function called wps_register_post_type(). Note that I am calling this main function in the init hook, which is required for custom post type registration. So every time I add a new post type I am adding the following:

'CPT Name' => array(
	'post_type' => '', // String
	'description' => '', // String
	'rewrite' => array( 'slug' => 'cpt-names' ), // Array with 'slug'
	'menu_icon' => WPSPS_URL .'/path/to/my/images/bookmarks16x16.png', // String URL
	'supports' => array( 'title', 'editor', 'excerpt', 'revisions', 'thumbnail', 'page-attributes', 'custom-fields' ), // Array of strings = features
	'taxonomies' => array( 'category', 'post_tag', ),// Array of strings = taxonomies
),

First, while I never have to do this (because this is my code and I’ve set it up how I like it), you can add a post_type entry to your array. This is the name of the registered post type. If you didn’t, the helper functions would do it for you. In this case, ‘CPT Name’ would be registered as wps_cpt_names. It converts the name to lower case and replaces the spaces with underscores. Note, my custom post type name is always my singular title, so if I want to pluralize the slug, then I add a rewrite entry to the array. On all my custom post types I add a menu_icon (call me Vain!), and since custom post types vary, I add my own support entry to the array. However, there does exist a default if you want everything. If I want my custom post type to support some Genesis functionality, I would include them here (e.g., ‘genesis-seo’, ‘genesis-layouts’, ‘genesis-simple-sidebars’).

/**
 * Registers a post type with default values which can be overridden as needed.
 *
 * @author Nick the Geek
 * @author Travis Smith
 * @link http://designsbynickthegeek.com/tutorials/custom-post-types-made-easy
 * @link http://codex.wordpress.org/Function_Reference/register_post_type
 * @link http://wpsmith.net/2012/custom-post-types/registering-multiple-custom-post-types
 *
 * @uses sanitize_title() WordPress function that formats text for use as a slug
 * @uses wp_parse_args() WordPress function that merges two arrays and parses the values to override defaults
 * @uses register_post_type() WordPress function for registering a new post type
 *
 * @param string $title title of the post type. This will be automatically converted for plural and slug use
 * @param array $args overrides the defaults
 * @param string $prefix prefix string
 */
function wps_register_post_type( $title, $args = array() ) {
	$prefix = 'wps_';
	$sanitized_title = sanitize_title( $title );
	$plural_title = isset( $args['plural_title'] ) ? $args['plural_title'] : '';
	unset( $args['plural_title'] );

	$defaults = array(
		'labels' => wps_post_type_labels( $title , $plural_title ),
		'_builtin' => false,
		'description' => $title . __( ' Custom Post Type' , 'child-translate-domain' ),
		'menu_position' => 6, // WP default: null (below comments ~ 25)
		'menu_icon' => '', // WP default: null
		'public' => true, // WP default: true
		'publicly_queryable' => true, // WP default: value of 'public'
		'show_ui' => true, // WP default: value of 'public'
		'show_in_nav_menus' => true, // WP default: value of 'public'
		'show_in_menu' => true, // WP default: null; 'show_ui' must be true
		'has_archive' => true, // WP default: false
		'capability_type' => 'post', // WP default: post; defines 'capabilities' as well
		'map_meta_cap' => false,  // WP default: false
		'hierarchical' => false,
		'taxonomies' => array(),
		'rewrite' => array( 'slug' => $sanitized_title ),
		'query_var' => true,
		'can_export' => true,
		'supports' => array( 'title' , 'editor' , 'excerpt' , 'author' , 'comments' , 'custom-fields' , 'revisions' , 'thumbnail' , 'genesis-seo' , 'genesis-layouts' , 'genesis-simple-sidebars' ),
        );

	$args = wp_parse_args( $args, $defaults );

	// Correct show_in_menu arg
	if ( false === $args['show_ui'] && true === $args['show_in_menu'] )
		$args['show_in_menu'] = false; 

	$post_type = isset( $args['post_type'] ) ? $args['post_type'] : $prefix . str_replace( '-', '_', $sanitized_title) . 's';

	register_post_type( $post_type, $args );

}

While the PHP documentation makes the function self-explanatory, let me explain in a bit more detail. First, I sanitize the title, which formats text for use as a slug. So if the title is: “This Is the Title of My Post,” the resulting sanitized title would be: “this-is-the-title-of-my-post.” This is important because case and spacing matters.

Then for the arguments, I have a list of default arguments that I use, which basically match the WordPress defaults (and an argument could be made against having them at all). However, I include everything (except capabilities, permalink_epmask, and register_meta_box_cb) so you can see everything that you need or may want.

Next, I am getting my labels from another helper function called wps_post_type_labels()

/**
 * A helper function for generating localizable labels
 *
 * @author Travis Smith
 * @uses _x() WordPress function that retrieves translated string with gettext context
 * @uses __() WordPress function that retrieves the translated string from the translate()
 *
 * @param string $singular Singular Title/Label
 * @param string $plural Plural Title/Label (optional)
 */
function wps_post_type_labels( $singular, $plural = '' ) {
    if ( $plural == '' ) $plural = $singular . 's';

    return array(
        'name' => _x( $plural, 'post type general name', 'child-translate-domain' ),
        'singular_name' => _x( $singular, 'post type singular name', 'child-translate-domain' ),
        'add_new' => __( 'Add New' , 'child-translate-domain' ),
        'add_new_item' => __( 'Add New '. $singular , 'child-translate-domain' ),
        'edit_item' => __( 'Edit '. $singular , 'child-translate-domain' ),
        'new_item' => __( 'New '. $singular , 'child-translate-domain' ),
        'view_item' => __( 'View '. $singular , 'child-translate-domain' ),
        'search_items' => __( 'Search '. $plural , 'child-translate-domain' ),
        'not_found' =>  __( 'No '. $plural .' found' , 'child-translate-domain' ),
        'not_found_in_trash' => __( 'No '. $plural .' found in Trash' , 'child-translate-domain' ),
        'parent_item_colon' => ''
    );
}

This helper labels function pluralizes my labels for me unless I specify a plural label myself, and makes all the strings compatible for localization, which if you are not making your custom post types labels able to be translated, then you need to be. Some of you may say that you never have the need; however, if you get in the practice of localizing, then when you do have the need, your code is already ready/done instead of having to re-invest the work later (which really is more work).

Now, if you want to add Genesis functionality to existing custom post types (that you may have registered via another plugin), then you may need the following.

add_action( 'init', 'wps_add_post_type_support' );
/**
 * Add Genesis custom support for registered post types
 * Add Genesis SEO/Layout support to CPTs (if not registered with them)
 *
 * @uses add_post_type_support() Registers support of certain features for a given post_type
 * @link http://codex.wordpress.org/Function_Reference/add_post_type_support
 *
 */
function wps_add_post_type_support() {
	// Uncomment below as appropriate
	//add_post_type_support( 'post_type', 'genesis-seo' );
	//add_post_type_support( 'post_type', 'genesis-layouts' );
	//add_post_type_support( 'post_type', 'genesis-simple-sidebars' );
}

To add the above to multiple post types:

add_action( 'init', 'wps_add_post_type_support' );
/**
 * Add Genesis custom support for registered post types
 * Add Genesis SEO/Layout support to CPTs (if not registered with them)
 *
 * @uses add_post_type_support() Registers support of certain features for a given post_type
 * @link http://codex.wordpress.org/Function_Reference/add_post_type_support
 *
 */
function wps_add_post_type_support() {
	$pts = array( 'post_type1', 'post_type2' );
	foreach( $pts as $pt ) {
		// Uncomment below as appropriate
		//add_post_type_support( $pt, 'genesis-seo' );
		//add_post_type_support( $pt, 'genesis-layouts' );
		//add_post_type_support( $pt, 'genesis-simple-sidebars' );
	}
}

add_action( 'init', 'wps_add_post_type_support' );
/**
 * Add Genesis custom support for registered post types
 * Add Genesis SEO/Layout support to CPTs (if not registered with them)
 *
 * @uses add_post_type_support() Registers support of certain features for a given post_type
 * @link http://codex.wordpress.org/Function_Reference/add_post_type_support
 *
 */
function wps_add_post_type_support() {
	// Uncomment below as appropriate
	//add_post_type_support( 'post_type', 'genesis-seo' );
	//add_post_type_support( 'post_type', 'genesis-layouts' );
	//add_post_type_support( 'post_type', 'genesis-simple-sidebars' );
}

To add the above to multiple post types:

add_action( 'init', 'wps_add_post_type_support' );
/**
 * Add Genesis custom support for registered post types
 * Add Genesis SEO/Layout support to CPTs (if not registered with them)
 *
 * @uses add_post_type_support() Registers support of certain features for a given post_type
 * @link http://codex.wordpress.org/Function_Reference/add_post_type_support
 *
 */
function wps_add_post_type_support() {
	$pts = array( 'post_type1', 'post_type2' );
	foreach( $pts as $pt ) {
		// Uncomment below as appropriate
		//add_post_type_support( $pt, 'genesis-seo' );
		//add_post_type_support( $pt, 'genesis-layouts' );
		//add_post_type_support( $pt, 'genesis-simple-sidebars' );
	}
}