It has over 130,000 views already! What I really love about this video in particular is that we get into the specifics of how a company can start to embrace a culture of letting employees work from anywhere, even if it started out as a traditional office with everyone in the same place. Automattic never started that way, so even as we’ve scaled up to more than 840 people in 68 countries, there’s never been a question — it’s now built in to our entire culture.

For distributed work to scale up, it’s going to require more CEOs, workers, and managers to test the waters. Any company can experiment with distributed work — just pick a day or two of the week in which everyone works from home, I suggest Tuesdays and Thursdays, then build the tools and systems to support it. Yes, that may require some shuffling of meetings, or more written documentation versus verbal real-time discussion. But I think companies will be surprised how quickly it will “just work.”

If the companies don’t experiment, workers may force them to do it anyway:

It’s been a difficult climate for the news business, particularly at the local level. It also breaks my heart how much of their limited resources these organizations still sink into closed-source or dead-end technology. Open source is clearly the future, and if we do this right Newspack can be the technology choice that lasts with them through the decades, and hopefully our 15 years of growth lends some credibility to our orientation to build things for the long term.

Here’s Kinsey in Nieman Lab:

The goal is to both make sure that the catalog of publishing tools as well as business tools they need to be able to run what one hopes is a sustainable news operation are addressed simultaneously. It’s not simply a CMS for a newsroom, but a full business system that enables publishing and monetization at the same time.

–Nieman Lab interview

As you have come to expect from Automattic, everything will be open source and developed to the same standards WordPress itself is. We’re working with Spirited Media and the News Revenue Hub on the platform, and we will likely look for even more partnership opportunities from across the WordPress ecosystem. If you’d like to invest or get involved, drop us a line at newspack@automattic.com.

Earlier today WordPress.com turned on the ability to push new blog posts to Tumblr, alongside the existing capability to do so for Twitter, Facebook, et al. This is interesting for a few reasons.

While the tech press often likes to paint companies in a similar market as competing in a zero sum game, the reality is that all are growing rapidly and services feed each other and cross-pollinate more than anyone gives them credit for. Tumblr built a dashboard reader product that has tons of pageviews and lots of followers, which can provide distribution for blogs much in the same way Facebook and Twitter do. (Its 85%-on-dashboard-centric usage looks more like a social network than a blogging network, actually.) WordPress has fantastic content that people on Tumblr love, and Tumblr has a rich and diverse content and curation community that can drive new visitors to WordPress — it’s like peanut butter and chocolate.

It’s true that we’re becoming simpler and more streamlined and it’s a process driven by our design vision and our community, not what any particular competitor is doing. WordPress has always flourished because it’s a hassle-free digital hub — a home on the web you can control, customize, and truly own due to the fact that it’s Open Source software. WordPress is the antidote to walled gardens.

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.

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!

But what about something more accurate? I’ve been a supporter of Quantcast since they launched and we run their code on all our blogs. It provides some interesting stats like demographics that we wouldn’t have on our own. (I also like that it’s fast and has never caused us problems, better than even Google Analytics.) Their numbers place us fairly well, #29 in the US with 16 million uniques. However there’s more…

Apparently the Quantcast numbers are just for blogs on a wordpress.com subdomain, none of our custom domain traffic is counted. They’re experimenting with a new feature called “networks” that aggregates the traffic for WordPress.com-hosted blog even with their own domains. Those numbers place us at 25 million US uniques and 70 million global a month, with a bit over 300 million monthly pageviews. We don’t track uniques, but their pageviews mirror our own closely so I feel this data is pretty accurate. 25 million US uniques would put us at #19 right next to Facebook.

The growth and reach isn’t a credit to us, it’s to our bloggers, but I am happy we’ve created a platform where some of the most creative bloggers can express themselves and attract a meaningful audience. Imagine what those numbers would look like if they included WordPress.org blogs.

This is a long way of saying happy 2nd birthday, WordPress.com. Thanks for the incredible ride over the last year.

As a service provider, you have a strong responsibility to these folks. They’re putting their life online with you, they deserve nothing less than 100% uptime. They tell all their friends to try you out, they deserve for the experience of the hundred thousandth user to be as great as the tenth. WordPress.com is serving 4.2 million hits a day on a handful of boxes. Akismet has gotten to the point where it’s blocking so many spams every second that any fraction of downtime is very noticable to users. (Like we had this morning.)

At Automattic we’ve always taken this very seriously, and from the bootstrap beginning I planned for it to be sustainable and frugal in the long term. Of course since I moved to San Francisco I’ve talked to dozens of really high-quality investors who were interested in what we were doing, but the bubble model of giant valuations and ultra-rapid growth never really appealed to me.

The growth of WordPress.com and Akismet has outpaced anyone’s expectations. Recently, I made the decision to sell a minority stake in the company to a few select partners who I think are going to bring a lot of value to the business far beyond mere dollars. This isn’t going to change how the business is run, or the people involved with it, but it will allow us to take better advantage of the opportunities before us and also for us to keep our promise to every one of you to maintain a fast, stable, and innovative platform in the long term.

Automattic isn’t going to get fancy SoMA offices, throw huge parties at SxSW, or “get big fast.” We took a small amount of capital to put things that were already growing fast in a stable position, so from month to month you’re not robbing Peter to pay Paul. We’re going to use the money to pre-emptively address scaling issues before they happen, and continue to share everything we can back to the community, like all of the code behind WP.com in WordPress MU, the spellchecking feature we sponsored, free Akismet for 99.9% of users, and a few other goodies we still have up our sleeve. In terms of hiring, we’re still going to grow very deliberately in line with our revenues and focus on the very best and brightest (and BBQ-loving), like Podz.

We’re going to publish more technical details about everything later, and this is already longer than I hoped — I’m sure you folks have some questions. I’m going to do something a little different and turn the comment section here into a FAQ. If you have a question, please post it below. If you want to say “congrats!” or “that sucks!” do it on this entry instead to keep the question and answer flow clean. If a question warrants a long enough answer I might turn it into a separate blog post.