Tag Archives: WordPress

Aaron Brazell

Screenshots from WordPress 2.7

The upcoming release of WordPress is around the corner, and we’ll be covering the things you will need to know about it, as we always do.

However, this is such a big release (game changer, at that!) that I wanted to tease you with some screenshots. I’ll let your imagination run wild (and you can go Google around for what others are saying). Make sure you are subscribed to this blog so you get the big release cheat sheet as soon as it comes out.




Update: I have released the big writeup on WordPress 2.7 now, so go check it out.

Aaron Brazell

Why Pay For a Blog Platform?

An interesting auxiliary thread has developed over the past few days. It has to do with blog platforms.

So, it’s not really a new discussion but it seems to be cropping up again a bit. It has to do with paid blog platforms versus free blog platforms.

Before I go any farther, let me say that although I’m a WordPress fan and advocate, I completely recognize that platforms should not be the focus. It should be the content. And platforms should essentially be transparent to the blogger. Get out of the way and let the blogger blog. Realistically, some people need more than a blogging platform and need a full featured content management system. I get it.

However, for new bloggers with so many quality, free options available, it boggles my mind that anyone would pay for a blog?

It seems even at home plate, at Lijit, there seems to be a tendency to use Typepad (which boggles my mind) and in corporate settings, Expression Engine seems to have legs.

I asked this question on Twitter:

Here’s a question for everyone: why on earth would you choose Typepad for your blog platform when starting out? Who pays for blog platforms?

Responses were varied an interesting:

I certainly don’t want to get into a platform war. Whatever makes your job as a blogger easier. But with so many really great free options out there, who pays for a blog platform and why?

Aaron Brazell

3 More Blog Optimization Routines

Last month, Darren Rowse asked me to contribute a post to Problogger about methods to increase page loads. He gets a lot of questions from his community and he wanted someone who had some experience in the area to help out. I obliged.

Please read it.

I wanted to follow up that article with a few page load and other optimization techniques, largely because, as I surf around the internetz, I’m noticing an increasing number of blogs that are very weighed down.

The golden rule here is that if a page takes longer than 2 seconds to load, it’s too heavy. Realistically, you want to shoot for a page load of under a second. In an era where broadband is ubiquitous, there is no excuse.


While I talked about images in the post at Darren’s blog, I really want to hammer this home. Kill the background images. The textured backgrounds, though they look good, are sucking your bandwidth. The same can be said for full-size banner headers. The only image that really should be in your header is a logo and it should be cropped to the size it actually is. Unless there is just some aspect of your branding that has to be fit into a full 750 or 1000px wide header image, you’re wasting your users bandwidth and slowing down your site.

Google Analytics

This is not really a page load issue, but it is a highly valuable point that at the time of writing the Problogger article, I was unaware of. Duncan Riley actually had a fantastic pointer about Google Analytics code that suggested going against the conventional wisdom (and Google recommended) approach of inserting the code in the footer and instead placing it in the head of the page.

Google recommends (and it is standard practice for most tracking code) that the code be placed in the footer as it will end up being the last thing to load, allowing the rest of the page to render and give the appearance of a quicker load. Duncan notes, however, that sometimes readers move on before that Analytics code is loaded preventing a registration of a pageview.

Since reading that article, I moved my GA code to the header and have experienced only a miniscule reduction in load time, but have increased the number of pageview. It’s important to note, though, that the pageviews are not changing, just the perception. If you run ads, it is the perception of pageviews that advertisers are buying ads based on – so you do want this to be perceived closer to the actual pageview number.

WordPress users, reduce your plugins!

Some people love using every plugin under the sun for WordPress. It’s as bad as those people that install every Facebook app around (Love you both, Lorelle and Cathryn!). The end result is slower load time.

This could be for a number of reasons. Plugins don’t necessarily go through the same QA and optimization process as the core WordPress code therefore, the activation of a plugin could introduce inefficient code or load unnecessary PHP processes into memory. Also, plugins that provide configuration options may also expose uncertain conditions when configured in certain way. The Google Sitemaps plugin is a great example of a plugin that, when misconfigured, can cause detrimental effects on a server which directly affects load time.

As always, my recommendation is always to run a tight ship, lean and mean is the best policy, and only use what you actually need. And if you stop using a plugin, make sure you deactivate it. There’s a security aspect to this as well.

Just a few more tips from experience. Feel free to add your own in comments.

Aaron Brazell

Google Blog Platform

A few years ago, in the early days of blogging, Google made a play to buy the Blogger platform. What occurred after that was a long period of time where Blogger received no love from their new parents. Also during this time, Movable Type came along and was then eclipsed by WordPress. WordPress went from a project to a business with the advent of Automattic and WordPress.com while the software remained an open source project for anyone to use and build upon.

It wasn’t until WordPress.com came along that we began to see some forward motion with Blogger. Google tied it to their authentication system and added some spit and polish, but nothing earth shattering. One of the biggest failures of Blogger is not the platform, but the management. It is the single largest source of splogs (or spam blogs) in the world – a failure of leadership that can be placed squarely at the feet of Google management. Meanwhile, WordPress.com is an open and airy environment that is policed actively (but passively, if that makes sense – no one is being a Nazi about content, but spam is ruthlessly dealt with).

While Google continues to release a parade of new products (anyone tracking the release of Google Shiny(Beta) today?), some of their largest and most potentially lucrative assets continues to meander aimlessly in an industry that continues to expand at a relentless pace.

Here’s a comparison between Blogger and WordPress.com

Blogger WordPress.com
Cost Free Free*
Personal Domains Yes Yes*
Template Control Yes CSS*
Javascript Yes No
Discoverability No Yes
Remote APIs Blogger Movable Type, Metaweblog, Atom, WordPress
Portability w/Domain Hosting only WXR Export
* Optional Paid Upgrade

Of all the migrations I’ve ever made, the biggest challenge exists around Blogger blogs. I’ve moved WordPress to WordPress, Movable Type to WordPress, Blogger to WordPress, Serendipty and Expression Engine to WordPress. I’ve moved TypePad to Movable Type. Blogger to Movable Type. You get the point. The most difficult migrations are off of the blogger platform.

Mark Evans suggested this morning that Google buy WordPress.com for name recognition and platform familiarity. The idea is to bolster the suite of services that Google offers now that it will have its integrated browser. Mark argues that WordPress.com has tons of traffic.

Here’s a hint though. Google doesn’t care about traffic. Plus, they have Blogger. Granted, Blogger sucks but according to Compete, it gets more traffic anyway.

Picture 2.png

So here’s what we know. Blogger gets more traffic, but savvy users like it less (particularly the UI and SEO). We also know that Blogger is a closed platform and that it is laden with spam. We know that Blogger is under very little active development, or their release schedule is abysmal.

We also know that WordPress is an open source platform that invites external developers to hack on it. We know there’s viable business in using the platform (hey, you don’t have to pay for active development on the platform!). We know that there is a hosted and self hosted version currently and that the WXR format makes it easy to transfer data around. We know that Akismet is open source and can be used to kill spam as well. We know that there are tens of thousands of people developing themes, plugins and offering knowledge. We know that it is possible to have a hosted version of WordPress in the vein of Blogger. We know Google engineers are smart.

So here’s what I propose instead. Leave Automattic alone. Let them keep innovating and building their enterprise client list like the New York Times, Dow Jones, and more. Matt has no interest in Google (at least he didn’t) as his philosophy is largely incongruous with Google (open source via mostly closed source).

Instead, Blogger should be transformed into an WordPress MU platform. Google engineers can solve problems such as providing FTP to other hosts, as Google has, with the new WP_Filesystem class that is used for plugin and automatic upgrades.

They can use their cloud to provide DNS services to point Blogger blogs to a different host, as they do now. They can tie in Google Auth with the available hooks. They can even port existing Blogger theme offerings to WordPress themes.

They retain the traffic and immediately compete on a close level, at least by all tangible metrics, with WordPress.com. Of course, there is that little thing about management styles where WordPress.com wins hands down in the current paradigm, but… thats something that can’t be addressed by technology.

Personally, I think it’s a solid play. May not happen, but it probably should for Google’s sake.

Aaron Brazell

Search and Findability

I’m at WordCamp San Francisco 2008 today and had the distinct pleasure of giving a talk on Search and Findability. Distinct pleasure because it was the first session of the day at 9am. And if any of you know me, then you know that I don’t do mornings well. :-)

My session was about Search and Findability. There seemed to be a lot of misunderstandings about what the session would be about. Findability is not SEO. SEO is an aspect of Findability. SEO makes a blog findable for search engines.

Really, Findability is all about the right data being available to the reader, whether that reader is human or a machine (search engines). To that end, theme structure is a major area of concerns. Theme developers can setup their themes to have related posts or popular posts functionality, as well as attention to search implementation. I suggested theme authors should provide search results in full format, and not simply excerpts.

Secondly, findability is all about metadata and descriptive data. Microformats provide a human semantic understanding to machine-oriented descriptive data. Examples are




as well as WordPress built in XFN. Human understanding of machine data.

Multimedia content should take advantage of descriptive content. This means image tagging, show notes for podcasts and caption text for videos. Of course, and understanding of tags and categories is helpful.

Thirdly, I touched briefly on Ambient Findability, a concept introduced by Peter Morville in the O’Reilly publication with the same name. Ambient Findability suggests that no matter what, where or how, content should be easily findable. At b5media the mantra was “the right content, at the right time, to the right person on the right device”. Morville asks three questions:

  1. Can people find your blog?
  2. Can people find their way around your blog?
  3. Can people find your content, products and services despite your blog?

Finally, I suggested four plugins/features that can enhance the findability of a site:

  1. Possibly Related Posts – Only available for WordPress.com users.
  2. Search Everything – makes all areas of WordPress content available for the default search
  3. Microformats plugins – adds additional Microformats support to WordPress: Micro Anywhere, Blog Summary and Save Microformats
  4. Lijit for WordPress – our new plugin that allows registration and configuration from inside of the WordPress admin. Also, it makes it possible to hijack the theme search form.

The slide deck from the session is available below. It is Creative Commons Attribution Non-commercial licensed. In other words, use the idea, use the concepts, use the deck in it’s entirety as long as you attrbiute me. I’m Aaaron Brazell from Technosailor.com in case you didn’t know. Oh, and if you make money, I expect a cut. ;-)

Findability Abwc2008
View SlideShare presentation or Upload your own.
Aaron Brazell

WordPress Plugin: WP-Brightkite

Some of you have noticed that I’ve been doing some experimentation in recent months with geolocation. Geolocation is a very powerful aspect of the next generation web. Particularly in the mobile space.

Boulder, CO-based Brightkite stormed on the scene a few months back as a location based micro blogging network. Members could take photos from the cellphones, send short messages to be posted to the service, and follow their friends. Based on the concept of location, Brightkite users could “check in” to a location. I am currently checked in at “Woodlawn, Maryland”, a fairly generic location since I value my privacy in my home. However, people can check-in down to specific addresses, cafés, places of employment, etc.

Though my fascination with Brightkite as a mobile microcontent network has faded, their is one aspect to it that I find extremely valuable in the absence of GPS on my Blackberry and the lack of ownership of an iPhone 3G. That is their KML file.

I set about creating a plugin that would parse the KML file of the most recent Brightkite check in location. Thus, WP-Brightkite was born.

Notably, for those folks interested in the geotagging content, the Brightkite plugin will parse latitude and longitude of the most recent checkin and geotag feeds using the ICBM RSS namespace. For a little extra bling, I’ve provided a template tag which drops a little Google Map next to the subject line of posts with geotagging (see this post, for instance).

  1. Upload the

    directory to

  2. Activate the plugin through the ‘Plugins’ menu in WordPress
  3. Fill out Brightkite user data on your profile page. Note: Standard WP permissions apply.
  4. Use the

    within your template to print a mini 10×10 map icon, clickable for Google Maps location.

There’s quite a bit more I want to do with this, but since I’ve been using it here on Technosailor.com for a few months, I wanted to get it into the wild and fix any bugs (thus the beta tag) before exploring more functionality.

Let me know what you think, and consider a donation.

Update: Please log a ticket here if you are having difficulties. You must login with your WordPress Support Forums username and password (here) to get new ticket creation options. The comment system I have here does not seem to be sending people notices of followups on support requests.

When logging a ticket, please tell me what version of PHP you are using and what version of WordPress you are using. Thanks.

Aaron Brazell

Revolution vs. Thesis: The Premium Theme Cage Match

Now that WordPress 2.6 has been released and you’ve got yourself upgraded (you have upgraded right?), you might as well take some time to spruce up that old dingy theme of yours and replace it with something attractive and practical.

If you can afford your own custom theme development, then by all means, do it. Nothing says professional like a completely unique theme that has been professionally designed with not only appearance, but functionality and practicality.

However, maybe you can’t afford a $3500 theme or maybe there is something that, out of the box does what you need.

While I won’t get into the merits of “premium themes” and if themes should ever be mass marketed AND paid products, I would like to do a compare and contrast on two separate premium themes by two very competent designers.

Revolution Theme

If you believe your WordPress powered blog is more than a blog, you probably want to check out Revolution Theme. Revolution currently has ten different variations designed with the intentions of various industries in mind. If you’re using WordPress more as a content management system and your business is in real estate, pro media, tourism, online magazine, sports, tech news or other corporate variety – Revolution might be the theme for you.

Brian Gardner, the creator of the Revolution Theme commented to me that he “developed the Revolution themes in order to take WordPress to a higher level ““ to stretch the capabilities, and to show that it can be used for so much more than a blogging platform.”

Indeed, we used the Revolution Pro Media theme over at The District of Corruption and found it to be very suitable for displaying all our content in a sexy way.

Revolution was not without its problems though.

For instance, the out of the box CSS is not compatible with Firefox 3 which handles the


property incorrectly. We were able to hack the CSS with a different solution. In addition, the video box on this particular theme assumes that video content is going to come from YouTube which is an incorrect assumption, in our opinion, with all the video formats available.

Also a problem with our use of the theme was the requirement for every post to have images attached to them via custom fields. We had to hack the theme files to not display images when no images are available.

Revolution Pro (which again is only one variant) offers few options for power users. It does offer a WordPress administrative page but jumps to vast conclusions that are probably not relevant to bigger publishers.

Picture 6.png

Revolution Theme is an incredible sexy and well designed theme from the code point of view. Semantics are paid attention to and the use of the WordPress API ensures that the theme will be compatible with WordPress for, likely, years to come. I would recommend that Brian does not rely on plugins to accomplish tasks. Include that code in the theme’s functions.php if the code is GPL and use an

if( function_exixsts() )

check to find out if the extra code is needed.

The Revolution theme is available for as little as $79.95.

Thesis Theme

Unlike Revolution, Thesis comes in one variety. It is a good variety though. The brainchild behind the Thesis theme is Chris Pearson. Chris is never content just building a theme but making the theme as braindead simple for anyone to use in a wide variety of situations.

To that end, Thesis is mainly configurable directly from WordPress admin and I have yet to have to significantly modify the out of the box code base. Granted, I have not had the length of time with Thesis as I have with Revolution.

One of the things I get to do is maintain my church’s website, which was in desperate need of overhaul and maintenance. I did not want to spend tons of time on it as, let’s face it, I’m not paid to do so. ;-) Thesis allowed me to stand up new content, new organization and a completely different look and feel in less than an hour. There’s still work to be done, but Chris has done most of the work for me.

The key to this ease is the amazing configurability directly from WordPress admin. With the interface, I have granular control of my navigation elements, formatting of posts, ad and analytics software, etc.

Picture 7.png

Thesis does not allow me to modify some of the basic layout rendering to my heart’s content, however. Fortunately, I could write little plugins to do little things like apply different CSS to elements but, as robust as it is, more could be done.

The Thesis theme only comes with one variety and it is available for $89.95.

Comparison Chart

Revolution Thesis Winner
Ease of Deployment (1-10) 6 8 Thesis
Variations 10 1 Revolution
Plugin Dependencies Yes No Thesis
Price $79.95 $89.95 Revolution
Support Forum Blog + Forum Thesis
CSS Firefox 3 Incompat Support for custom CSS Thesis
CMS-Friendly Yes Kinda Revolution

Winner: Thesis 4-3.

Both are great and Chris and Brian should be commended for providing great resources.

Added: I forgot to mention one thing that I really wish theme authors would do more of. The Thesis theme has some of this but it could use more. Hooks, people! Add hooks everywhere in a theme.

The main reason for this is that people who want to modify the behavior of a theme can do so without editing the theme at all if there are hooks built into the theme.


WordPress 2.6: Officially Launched

If sources very close to WordPress development are to be believed, it’s dropping tonight. Many people will be upgrading their WordPress blogs tonight or tomorrow. Lots of folks have written about new things that you should be aware of so here’s a quick recap.

WordPress MU is following the WordPress development timeline and should see a similar bump in short order. It is jumping to version 2.6 to mirror WordPress development.

I’ll update this post when it actually drops, though as I said, it should be “sometime this evening Pacific time”.

Bonus points to the attentive user who discovers the easter egg in WordPress 2.6 and reports back here. ;)

Update: SVN Users. WordPress 2.6 is versioned. Revision 8332. Yet to be branched though the versioning in trunk indicates it’s imminent.

Update 2: Version 2.6 has been branched in SVN now –


. For those unaware, that pretty much means that 2.6 is final, just awaiting bundling and availability at WordPress.org.

Update 3: WordPress 2.6 is in the Wild

Aaron Brazell

10 Things You Need to Know About WordPress 2.6

WordPress 2.6 is around the corner (sometime next week, it looks like), and as usual, there’s a bunch of changes, improvements, enhancements that have went into this version. In my opinion, this is an odd major release. While there are certainly major new changes that warrant a new major release, much of the release consists of various improvements generally saved for “dot releases”. Security and enhancement type stuff. The thinking is that WP 2.6 can be released so a WordPress 2.7 can come in the early fall timeframe and integrate new features developed in conjunction with the Google Summer of Code project.

Still though, there is a significant amount of new functionality that I find quite nice.

Google Gears Support

Gears is the Google technology that allows for Firefox (apparently IE 6 too, but I can’t confirm) to “pre-cache” pages and speed up access. Gears has been integrated with WordPress 2.6 on the admin side and speeds things up tremendously. This is particularly important where broadband access is limited or inaccessible (third world, for instance). To enable Gears in your new WordPress 2.6 installation, click on the Turbo link in the upper right corner of your WordPress admin.

XML-RPC Editor Functionality

Quietly, a new bit of functionality snuck into WordPress trunk that threw a number of developers and kicked off an interesting discussion. In the development cycle, XML-RPC and Atom Pub API for remote editing was turned off by default as a “security precaution” since many recent WordPress security issues seem to stem from the XML-RPC protocol.

Daniel took the issue up on his blog in a bit of a vicious manner because he has a vested interest in desktop client support for blogs. He is the developer behind the very nice MarsEdit client for Mac which, incidentally, I’m using to write this post. He took his battle up, a bit more congenially among WordPress developers, and the result was a compromise. New WordPress 2.6 installs would be given the option at install to enable XML-RPC editing and upgraded blogs (pre-existing) ware grandfathered in to an “enabled” paradigm.

Picture 9.png

This is an important shift in the way bloggers think about writing. Most of us simply want to write. We don’t want to worry about the technical aspects of maintaining a blog. This is the philosophy that drove the b5media team, whom I worked for from very early days, to develop a network of bloggers that were able to simply write without worrying about the logistics of maintenance, upgrades, monetization, etc. Unfortunately, while most bloggers are not technical, malicious parties ‘out there’ are technical and look for any opportunity to attack blogs and other websites. XML-RPC and APP provide a vector which, though pretty secure, has seen its share of exploits in the past. Disabling functionality that is not explicitly used by every user makes sense for security reasons.

Bloggers can enable or disable the functionality via the Settings > Writing page in WordPress admin and most desktop editors still only support the XML-RPC protocol so unless you’re explicitly using the Atom Publishing Protocol, you’re probably safe to leave only XML-RPC checked.

Post Versioning

Developers familiar with Subversion, or SVN, understand the concept of versioning and diffs. Compare one file, or revision, against another file, or revision, and see a breakdown of differences between the two. With the help of GUI tools, developers can see a color-coded red vs. green (removed vs. added) presentation.

This concept has now been applied to posts so you can view differences between posts as well as “revert” to an earlier version of a post. I absolutely love this feature and you can see an example of a “revision compare” built directly into WordPress.

SQL Security – $wpdb->prepare()

Back in WordPress 2.3, the


first emerged, initially unused… but there. The method was very experimental at the time and was not ready for prime-time so, though it was included, it was not yet used. We started to see its emergence in WordPress 2.5 and in WordPress 2.6 it is being used just about everywhere.

The idea behind


, if you’ll allow me to get geeky for a minute, is to sanitize SQL in such a way that SQL injection is prevented. So, plugin developers, in particular, should be happy with this method (part of the


class). Not only should they be happy, but from a best practice standpoint, you should be using it.

In my opinion, this should be a part of a “dot release” and not as a major feature of a major release.

Shift-Click Selection of Multiple Checkboxes in WP-Admin

As the backend of WordPress continues to evolve after the release of the drastically redesigned admin in WP 2.5, usability enhancements are also making their way in.

One of the better usability enhancements added in WordPress 2.6 is the ability to “shift click” to select multiple checkboxes at once. Say, for instance, you want to clean up an unwieldy category system (as I need to), Simply navigate to your category management page, click on the first category you want to delete, for instance (posts will go into the default category), and “Shift-click” on a checkbox farther down the list. Magically, all checkboxes in between will also be selected.

This, of course, works anywhere where checkboxes are employed in the WordPress admin.

More Avatar Options

With the Automattic acquisition of Gravatar last year, in-built support for Gravatars was introduced in WordPress 2.5. WordPress 2.6 gives the blogger more options by allowing for selection of the “default” avatar. Out of the box, the default Gravatar can be “Mystery Man”, a generic grey avatar with a white silhouette of someone. Default avatars can also be “blank” (self-explanatory), the Gravatar logo, Identicons, Wavatars or MonsterIDs. These have all been a part of WordPress.com for some time and now come to the rest of us. For more information, Matt wrote a post for the WP.com community that you should probably check out. The difference here being, of course, that WordPress.com offers “dashboard avatars” and WPFROU (WordPress for the Rest of Us) does not include this functionality.

Page Templates over XML-RPC

In addition to the XML-RPC/APP security measures listed above, a new key bit of functionality has now been exposed for API editors (and also, if you think about it, demonstrates the power behind XML-RPC and why you might want to turn it off if you don’t use it). The XML-RPC interface now allows for managing page templates from an API editor. To the best of my knowledge, no editor supports this yet and may not. However, increasingly there is the ability to remotely post content from places like YouTube, Utterz and others. None of these services would have any real use for this functionality either, however I want to point out that because they can post remotely anything that is exposed to the remote world can also be managed.

It’s also conceivable that an offline WordPress client could be built that replicates WordPress admin in a desktop client, and this is one more step in that direction.

Press This

Press this! is a new enhancement of a long-existing concept. Bookmarklets. In fact, WordPress used to have a bookmarklet included that would allow a user to quickly start a new post from the browser toolbar, but the functionality was limited.

The Press This! functionality rocks, actually, because it allows the user to be on any website, click the bookmarklet and get a miniaturized version of WordPress admin with options to snip text, photos from the page, quotes or video embeds.

Picture 10.png

Obviously, we can lead you to water but we can’t make you drink. BE VERY CAREFUL OF COPYRIGHT VIOLATIONS! Oh, and the Associated Press sponsored this. (kidding!)

Integrated Theme Preview

Theme previewing has been a bugaboo for many a theme designer. How do we check and develop without affecting the rest of the site. Some folks resorted to using Ryan’s venerable Theme Preview plugin. Others setup a beta version of a site that was sandboxed off from the rest of the world. Lots of different approaches, all of which remain valid.

However, for theme developers and bloggers looking to see how a theme will look on their site, with their content, there is now theme preview bling. When you are on your Design page, click on one of the theme screenshots and your site will be loaded in a lightbox-like overlay to allow you a live preview. Heavily inspired, I’d imagine, by the Mac OS X Leopard Quick Look functionality.

Remember when Technosailor looked like this?

Picture 11.png

Plugin Management Overhaul

Finally, the plugin management interface has received a face-lift and some added functionality. Active plugins and inactive plugins are segregated and with that new fangled Shift-click functionality I talked about before, plugin management just got really freaking simple. Note that Active plugins can be deactivated in bulk and Deactivated plugins can be activated or even deleted in bulk. Clean up that stale plugin list in a snap. But… there’s always a but… make a backup before you go nuts.

Aaron Brazell

WordPress Plugin: WP-Twitterpitch

Obviously, there’s been a lot of talk about PR pitches gone bad. Stowe Boyd coined the word Twit Pitches last month. The concept is to force PR firms to use the economy of words (characters?) to pitch bloggers. It’s a reality in life, and I fight with my wife on this regularly, that no one cares about your “thing” as much as you do and so are less likely to want to give you the time to “pitch” the story or idea. You need to be quick, succinct and use compelling hooks.

Thus, the Twitter Pitch was born.

I’m releasing a new plugin that I hacked together over the weekend called WP-Twitterpitch that I’m also running here at Technosailor. Check out the navigation for a demo.

WP-TwitterPitch is all about getting the pitch delivered to you in the form you want to get it delivered – in other words in Twitter format. If you’re like me, then your Twitter direct message box is a lot like your email inbox. Personally, I don’t want to get pitches from PR companies in certain email inboxes. For whatever reason, I may not check them or they are personal, etc.

Twitter, however, provides the ultimate quick-messaging system. This plugin provides a template tag that you can drop anywhere in your theme. Clicking the link provides lightbox-like functionality for a “pitch form”. Using the form does not require a Twitter account (but does require that you have a secondary Twitter account you can use for this purpose, since you can’t send Direct Messages to yourself via Twitter). Note: Your WP-TwitterPitch Twitter account must follow the account that is being pitched and vica versa. This is a one-off action (hopefully, depending on Twitter) and only needs to be done when setting up WP-TwitterPitch.

Messages sent from the form are DMmed to the account getting the pitch and the form is limited to 140 characters or less. The beauty of linguistic efficiency.


  1. Upload the

    folder to the



  2. Activate the plugin through the ‘Plugins’ menu in WordPress
  3. Edit Admin options to include Twitter ID to pitch, Twitter ID and Password to send Twitter pitches
  4. as, as well as a message to “pitchers” that will be displayed in the form after the pitch has been sent.

    Place wherever you want the link to appear

Direct Download Link