WP.com Marketplace Idea

WordPress.com, ,

At WordCamp Argentina yesterday I talked about an upcoming feature for WordPress.com, a theme marketplace, and while the feedback has been universally positive amoung everyone I talked to some folks who weren’t there and don’t speak Spanish seem to be criticizing third-hand, Google-translated information, which is a little sad to watch, so here’s some details. 🙂

Right now WordPress.com is a little bit like a clothing store with only XXL men’s pink ponchos available — not a lot of selection. We’d like to offer more products, hence the idea of a theme marketplace.

Imagine you’re a theme designer and if you do a custom one-off theme for a site like this you may get $500. (Keeping the numbers simple for the sake of argument.) Making a good theme is really hard, and you may only be able to do one a week. Now imagine you made a theme and uploaded it to our theme marketplace, then set a price of $50. You’re now an option on the dashboard of 1,736,206 blogs, if we split the price evenly and 20 of those 1,736,206 blogs purchase the theme, you just made as much as you would doing a one-off design. You can plug in different numbers and assumptions there and it’s pretty easy to see how this could be big for designers.

There are some obvious things that need to be in place, and probably a few we haven’t thought of yet. There need to be some theme guidelines (and good taste) enforced, an easy, safe interface for uploading and updating of themes, a system for previewing a theme live on your blog. Beyond the obvious guidelines of browser compatibility and general not-sucking, we’ll require submissions be original, link-free, not published before, and GPL-licensed. (That also means that all themes in the marketplace will be available FREE to wordpress.org users. That may force some to switch from .com to .org, but that’s fine. :)) Will .com users want to buy premium themes? I think so, but the only people really taking that risk are launch partners, and worst-case scenario you’ve got a cool WP theme on your hands. (By the way if you have an amazing theme and you want to be in this program at launch, which should give it a nice boost, drop me an email m@mullenweg.com with “killer theme” in the subject.)

At the end of the day, it’s just a market. I’m sure styles, pricing strategies, and more will develop over time.

Google Penalizing Paid Links

Asides, ,

Now that Google is officially penalizing paid links, I’m glad the WordPress community took such a strong stand against them in themes. Countless blogs could have been penalized just for the theme they were using, not related to anything they did or did not do on their blog. It was a tough decision at the time, it probably drew more criticism and personal attacks against me than anything we’ve done before, but time has proved us right.

Comscore Numbers

Asides

This snippet from the Wall Street Journal shows the Comscore numbers for the top social media sites, show us about 22 million ahead of Flickr and “Six Apart Sites” (which I think is Livejournal/Typepad/Vox combined) but about 9 million behind Facebook. I think the reason they say N/A for our growth is because a year ago we weren’t even tracked by Comscore. We’re too cheap for a subscription though, maybe someone with one can check that?

Rails Bashing

Asides, ,

Since 7 reasons I switched back to PHP there seems to be a trend of Rails-bashing articles, epitomized by this one which is a fine example of the form until it advocates ASP.NET. Through it all, I still haven’t heard of a startup or web service that failed or succeeded due solely to its web framework or language. These articles are like the celebrity gossip stories of Web 2.0, complete with ad hominem attacks, and just as useless. Hacker News tends to be a fairly high signal source of discussions actually relevant to startups.

S3 News

WordPress.com, , ,

Three bits of Amazon S3 news:

  1. We’re now using S3 as the primary storage for WordPress.com, rather than just for backups. We have some layers in front of it, notably Varnish, so the majority of our serving doesn’t hit S3. Still, our AWS bill went from around $200/mo to $1500/mo, and rising. It has simplified some of our requirements, but doesn’t look like it’ll save any money.
  2. Amazon now has a Service Level Agreement (SLA). Big companies like this, but in the real world I’ve found there to be a low correlation with service reliability and the presence of a SLA.
  3. In the Amazon newsletter they promoted Content Spooling Network as a good use of their services. Unfortunately, the service appears to be tailored for using Mechanical Turk to “ghostwrite keyword-based articles for SEO,” or more succinctly, “spam.” Get a web-savvy editor for that newsletter, guys!