Post Status Podcasts

Welcome to the Post Status Draft podcast, which you can find on iTunes, Stitcher, and via RSS for your favorite podcatcher. Post Status Draft is hosted by Joe Hoyle -- the CTO of Human Made -- and Brian Krogsgard.

Software as a service (SaaS) is often viewed as a holy grail for successful online business. The ability to generate recurring revenue that doesn’t require hours-for-dollars is attractive to most entrepreneurs.

WordPress can be a helpful tool to get a lot of SaaS functionality out of the box. In today’s episode, we discuss WordPress and SaaS in two contexts: one, using WordPress as a technology basis for a SaaS in another industry, and two, creating a SaaS catered to the WordPress world.

Welcome to the Post Status Draft podcast, which you can find on iTunes, Stitcher, and via RSS for your favorite podcatcher. Post Status Draft is hosted by Joe Hoyle -- the CTO of Human Made -- and Brian Krogsgard.

WordPress hosting is always a hot topic of conversation, due to the difficult task of differentiating one host from another. There is also a lot of money and marketing involved in the industry -- an industry that includes some of the largest companies in the WordPress ecosystem.

In this episode, Joe and I attempt to break down what different types of hosting are available, how they are applicable to WordPress, and even dig in to some of the drama and politics that surround the hosting world.

The techical part of the conversation is the first 50 minutes or so, and around that mark, we get into the politics and non-technical issues around WordPress hosting, as well as tell some stories of how companies have successfully marketed themselves by getting embedded in the WordPress community.

Welcome to the Post Status Draft podcast, which you can find on iTunes, Stitcher, and via RSS for your favorite podcatcher. Post Status Draft is hosted by Joe Hoyle -- the CTO of Human Made -- and Brian Krogsgard.

HTTPS and HTTP/2 are somewhat intertwined, and a lot has been going on lately in this realm. Google has made a big push to encourage the use of SSL for websites -- including making it a search ranking factor -- and LetsEncrypt and other services are offering new ways to deliver free SSL certificates, securely. And HTTPS is required for HTTP/2, which is making a big splash as well, quickly outpacing SPDY. Today, we’ll talk about what these terms are, and what it means for the web and for WordPress.

Welcome to the Post Status Draft podcast, which you can find on iTunes, Stitcher, and via RSS for your favorite podcatcher. Post Status Draft is hosted by Joe Hoyle -- the CTO of Human Made -- and Brian Krogsgard.

Today, Joe and Brian discuss WordPress in the “enterprise," starting with a discussion on what the enterprise even is. We discuss WordPress’s value to the enterprise, and what enterprise level companies are looking for in their technology solutions.

The conversation turns into conspiracy theories and joking around by the 50 minute mark, so don’t be intimidated by the hour and fifteen minute timestamp.

Welcome to the Post Status Draft podcast, which you can find on iTunes, Stitcher, and via RSS for your favorite podcatcher. Post Status Draft is hosted by Joe Hoyle -- the CTO of Human Made -- and Brian Krogsgard.

Joe and Brian were joined by Ryan McCue, the Lead Developer of the REST API, Daniel Bachhuber, a contributing developer to the REST API, and K.Adam White, Aaron Jorbin, and Jack Lenox — each with unique experiences using the REST API. They discussed the talks from A Day of REST, but also about the impact of the new API more broadly as well.

If you’re at all interested in the REST API, this is an excellent round table to listen to.

Welcome to the Post Status Draft podcast, which you can find on iTunes, Stitcher, and via RSS for your favorite podcatcher. Post Status Draft is hosted by Joe Hoyle -- the CTO of Human Made -- and Brian Krogsgard.

This week’s Post Status Draft podcast is hosted by Brian Krogsgard and Joe Hoyle. This week, they talk working in an agency and doing client work.

Joe and Brian discussed a variety of facets to agency and client work, including:

Welcome to the Post Status Draft podcast, which you can find on iTunes, Stitcher, and via RSS for your favorite podcatcher. Post Status Draft is hosted by Joe Hoyle -- the CTO of Human Made -- and Brian Krogsgard.

In this episode of Draft, Joe and Brian discuss the biggest stories of 2015 and look forward to predict where the WordPress world will go in 2016.

Topics and Links

Welcome to the Post Status Draft podcast, which you can find on iTunes, Stitcher, and via RSS for your favorite podcatcher. Post Status Draft is hosted by Joe Hoyle -- the CTO of Human Made -- and myself.

In this episode, Joe and I interview Scott Taylor, who works at The New York Times, is a WordPress Core Committer, and has lead the release of WordPress 4.4. We discuss dig into many WordPress 4.4 features, the thinking behind them, what it's like to lead a release, and core development in general.

We also talked about WordCamp US, where we recorded the podcast from, including Scott's experience speaking during the State of the Word. After the interview with Scott, Joe and I dig more into the State of the Word and WordCamp US in general.

The interview with Scott is first and Joe and I switch to WCUS and the State of the Word around 37 minutes in.

I had the opportunity to interview Matt Mullenweg about an   ambitious project that included more than a year and a half of development to create an all new WordPress.com interface, both for the web and a desktop app. The project was codenamed Calypso, and we talked about many aspects fo Calypso, as well  as a   variety of subjects that relate to it.

He also notes how he's always  looking for things that will "move the needle" for greater WordPress adoption. We were both thinking about the same statistic: that roughly 96% of WordPress.com users (and probably a high number of WordPress.org users too) essentially abandon their websites after a short tenure. So anything that can increase that number, to say 8% or 15% of folks that stick with it long term, can make a huge difference.

Matt  and I talked about the merits of WordPress as a network versus a platform. He thinks it can be both. And I think this touches on one of the big goals for Calypso that we haven't discussed yet: to make WordPress a better network.

To me, WordPress.com is a platform, but WordPress (both .com and Jetpack enabled sites) are ripe to be a hugely successful network, through the huge number of websites and independent publishers that are interconnected via WordPress.com.

There is more evidence that this is a goal for them too, with the launch of Discover WordPress along with the release of the new interface. Discover WordPress is a project by the editorial team to surface the best writing across WordPress.com and Jetpack enabled websites.

Furthermore, beyond the human curated content, much could be done in the future algorithmically. We didn't get as much into this stuff as I would've liked, but I think it's  an enormous growth area for Automattic.

There are a slew of fancy React components that could be pretty easily lifted from Calypso and used independently, as well as a guide to getting started with the full codebase.

He doesn't think it's too much of a problem, but says it's important that we experiment and learn from our experiments; he was hesitant to call the potential for confusion fragmentation as much as experimentation. Either way, I do think education and documentation will be important as other folks continue to use parts of WordPress to make impressive things, without supporting every specific thing that can also run on WordPress.

An example of this is the WordPress.com app itself. You can manage   Jetpack enabled sites through it, but that doesn't mean you get everything in the editor you'd get with a WordPress.org site, like custom fields and other plugin functionality that the desktop app doesn't support.

From a WordPress.org   perspective, WordPress.com integrated tools like Stats, VaultPress, and Akismet are difficult to match with other tools.

For  WordPress.com, he thinks the potential power of the Reader and network can be compelling. I agree there that the diversity of the WordPress.com and Jetpack author  audience could make for a compelling Reading product, that has more potential than I see right now in a competitor   like Medium, which is very tech heavy.

Matt   says,   [pullquote align="right"]"We've built up a lot of trust in the community, and that goodwill definitely pays back."[/pullquote] Part of what makes it hard to identify Automattic's specific differentiator is that they do a lot of things. Matt acknoledged this, but counters by saying that they work hard on user experience and being a good community citizen.

The rule of thumb Matt wants   to maintain is that someone should have   no more than 10 people that report directly to them, though he has around 23.

According to the standards of the tech world, Automattic's scale in terms of the number of employees may be somewhat ordinary, but they have still had massive and consistent change over the decade of the company's existence. And they are hiring as fast as they can to this day.

As he notes, the customizer has undergone a lot of positive iteration over the last several releases, and today the WordPress.com and WordPress.org customizers are using the same base code; whereas for a while WordPress.com had their own custom implementation.

But he still says that, "if we're candid with ourselves, ... customization is still the  worst part of WordPress, you know?  It's the hardest. It's  where people get stuck. It's where there's a real gap between the promise and what people are able to realize and create when they get started using WordPress."

It's not as much a problem with the use of themes, or if you can code, but for new users, "it's their biggest struggle."

One idea that I have is to have a more Medium-like interface be the "default" view, versus a changing default theme. That way, WordPress.com could be more opinionated about the default view, and change the theme at will, or along with trends, versus giving new users the default theme of a particular year and then that theme is untouched unless the user decides to switch.

Matt said they have that a bit on the Reader view, but that is what someone in the WordPress.com network would see, versus what an outside website visitor would see.

Anyway, there are definitely challenges ahead for making customization and, more importantly,  just ensuring sites look good for users. I think that this is an area where other platforms -- like Medium and Squarespace, though in different ways -- are doing a good job.

Additionally to the natural desires that Automattic employees should have to learn, they created internal resources for helping people, and are considering releasing some of that material, maybe in the form of webinars or an online conference.

Matt said Automatticians will also be sharing what they learn at other conferences, like the upcoming A Day of REST, where  two Automatticians will be speaking.

Matt did admit that he hasn't made the PHP to JavaScript switch yet, and personally feels more comfortable in PHP; though some of his team have said it wasn't as intimidating as it sounds.

Generally, he says  they put their focus in, "three main buckets." The use that focus both for revenue purposes and product purposes. Those areas are  WordPress.com, Jetpack, and WooCommerce.

They group things like VaultPress and Akismet under Jetpack; so it's basically their WordPress.org SaaS revenue stream. Those are paid subscription products.  They have been transitioning that offering, as Matt shared, "a big trend over the past few years, has been to move away from a la carte upgrades, and have more bundles."

They've discovered that bundled plans of $100 per year and $300  per year have been successful. Here are those plans, for both WordPress.com and WordPress.org, as shown in the new WordPress.com/Calypso interface:

It appears they get most of their revenue from this stream. I do know, and have previously reported, that at least one point, WordPress.com VIP accounted for upwards of 25% of overally revenue, and though that gross number has gone up over the years, its percentage of overally revenue has gone down, meaning that these paid plans have outpaced VIP, growth-wise. I'd guess VIP revenue is now less than half of that 25% number now, but can't confirm it.

I tried to get him to share the number of active websites, but that's not something he could share.

He also noted that since WooCommerce is now "part of the family," that there may be future monetization opportunities   through that, though he said they don't have current plans for a hosted version of WordPress.com. I was honestly pretty surprised by this:

He says the Woo team is now 63 people, and a number of Automatticians are doing "Wootations", or rotations with the Woo team.

But they expect to do more going forward. They want to see what there is demand for, and what other people do with the open source nature of the project.

Matt also noted that he'd like to "loop back" to content blocks (code named CEUX) -- the project that stalled last year. And he's like to see what can be done around collaboration, editing, and the suggestion process.

Matt thinks this balance is important, and that we must continue to improve in both directions to continue WordPress's growth.

The Calypso project is a fascinating one, and it's a great example of what we should continue to expect: powerful, catered tools  that run on a RESTful API. They aren't always going to be tools for use everywhere, but we can expect to continue to see WordPress used in innovative ways, and be an exceptional platform for all kinds of applications.

And finally, at the end of the interview, I  pitched Matt on one  of my most hairbrained ideas. The naming conflict between WordPress.com and WordPress was really bad with this project, as nearly everyone not deeply embedded within the WordPress world got it wrong, and conflated Automattic's WordPress.com with WordPress the software.

And I think Jetpack's brand has really blossomed. I think there is an argument to be made that Automattic could change the name of WordPress.com to Jetpack, and both Automattic and WordPress would win from the change. It wouldn't be easy, but all I asked from him, is whether he'd read my post if I made one to give the pitch. He said he would, so expect that sometime soon.

Thanks to Matt for the interview, and thanks to Mark Armstrong for helping me get going with the new WordPress.com app and arranging the interview.

Welcome to the Post Status Draft podcast, which you can find on iTunes, Stitcher, and via RSS for your favorite podcatcher.

Joe is away this week, so Brian goes solo. Brian highlights WordCamp US and A Day of REST and describes why you should attend these events. He also tells the story of his first ever WordCamp San Francisco (the precursor to WCUS). Then, he interviews Mike McAlister, of Array Themes, and they talk about the process of building a commercial WordPress theme from the ground up.

The interview with Mike starts around 14 minutes in.