Category Archives: Design

Web design, typography, user experience, and visual aesthetics.

Back on The Verge

Automattic, Design, New York, Politics, Press, WordPress

In honor of Automattic’s 20th anniversary, and also since it’s been a few years, I joined Nilay Patel the editor-in-chief of The Verge on their Decoder Podcast. We talked about Tumblr and the Fediverse, how Automattic thinks about Ecosystem and Cosmos sides of the business, Automattic’s re-organization into cross-business functional teams and leadership, the vision of Clay as a personal CRM and Beeper as the super-human messaging app that puts control in the hands of users, Newspack, the future of websites, the obligatory coverage of the alleged WP Engine trademark violations and their subsequent preemptive suit, and much more. Please give it a listen! They chose the title “Why Automattic CEO Matt Mullenweg went to war over WordPress.”

Speaking of Beeper, we’re going to do a fun event for the next-gen version that’s launching on July 16 in New York City in NoHo. I’ll be there along with Beeper CEO Kishan Bagaria and some of the best and brightest in New York’s tech and creative class. If you’re a Beeper early adopter (or would like to be) and want to attend, leave a comment! We’ve held back some invites for cool folks like readers of ma.tt. 🙂 It’s like getting on board with WordPress in 2004.

Play With Clay

Automattic, Design, Video, WordPress

Happy to announce that the amazing Clay.earth product and team is joining Automattic. If you haven’t tried the app out yet, here’s a quick video to give you a taste.

TechCrunch has covered the broader strategy pretty well: One of the top requests we’ve heard from Beeper beta testers is they want to tie in more context, like a personal CRM, and some even requested Clay by name. We’ll keep the apps separate, as Clay also has some interesting team uses, but they will complement and integrate with each other as part of our all-in-one messaging strategy.

We share a vision to integrate Clay’s technology, which manages over 140 million relationships, as a layer across many of our products and experiences at Automattic. I’m excited to work with the founders, Matt and Zach, to bring this vision to life. I’ve always felt the missing primitive in WordPress’ content management data architecture was a scalable concept of a Person and Relationships outside of our user table.

Here’s the beautiful announcement on the Clay site and on Automattic’s.

Reflecting

Design, Open Source, Personal, WordPress

I know there’s been a lot of frustration directed at me specifically. Some of it, I believe, is misplaced—but I also understand where it’s coming from.

The passing of Pope Francis has deeply impacted me. While I still disagree with the Church on many issues, he was the Pope who broke the mold in so many ways, inspiring me and drawing me back to the Catholic faith I grew up with, with an emphasis on service, compassion, and humility. His passing on Easter Monday, a holiday about rebirth, feels historic. Moments like that invite reflection—not just on personal choices, but on the broader systems we’re a part of.

My life, which was primarily about generative creative work that was free for everyone to use, has been subsumed by legal battles. From the start, I’ve said this: after many rounds of negotiation that I approached in good faith, WPE chose to sue. In hindsight, those conversations weren’t held in the same spirit, and that’s unfortunate.

But we can’t rewrite the past. What we can do is decide how we move forward.

The maker-taker problem, at the heart of what we’ve been wrestling with, doesn’t disappear by avoiding it. If we’re serious about contributing to the future of open source, and about preserving the legacy of what we’ve built together, we need space to reset. That can’t happen under the weight of ongoing litigation. The cards are in WPE hands, a fight they’ve started and refuse to end.

So I’m asking for a moment of reflection for us all as stewards of a shared ecosystem. Let’s not lose sight of that.

The long-anticipated “Big Sky” AI site builder on WordPress.com went live today. It combines several models and can create logos, site designs, typography, color schemes, and content. It’s an entirely new way to interact with and edit a brand-new or existing WordPress site. This AI agent will make WordPress accessible to an entirely new generation and class of customers, and it will be a power tool for professionals to do things in minutes that used to take them hours.

Ed Catmull on Change

Books, Design, WordPress

I’ve been really enjoying the book Creativity Inc by Ed Catmull of Pixar, it was recommended to me by my colleague Dave Martin a while back and I finally got around to it. There’s an interesting story in it where George Lucas had asked him to develop a film editing system that was digital.

While George wanted this new video-editing system in place, the film editors at Lucasfilm did not. They were perfectly happy with the system they had already mastered, which involved actually cutting film into snippets with razor blades and then pasting them back together. They couldn’t have been less interested in making changes that would slow them down in the short term. They took comfort in their familiar ways, and change meant being uncomfortable. […] If left up to the editors, no new tool would ever be designed and no improvements would be possible.

This made me think a lot about the early days of Gutenberg and the huge resistance it had in the community, including causing the fork of ClassicPress. Now that we’re much further along there’s a pretty widespread acceptance of Gutenberg, and it’s responsible for the vast majority of all WP posts and pages made, however if we had taken a vote for whether it should happen or not, it probably wouldn’t have ever gotten off the ground.

What’s funny is if you go back even further, using a visual WYSIWYG editor in the first place was very controversial, and many people didn’t want the classic editor brought into WordPress.

Studio Sync

Design, Open Source, WordPress, WordPress.com

WordPress.com launched a new update to Studio this week, and we’re already seeing some buzz.

Studio is our free and open source app for local WordPress development, enabling you to spin up unlimited WordPress sites on your personal computer.

Through its newest feature, Studio Sync, you have complete freedom to:

  • Connect your Studio site to and from a WordPress.com production or staging site, included for free in Business and Commerce hosting plans.
  • Push and pull changes as a team by connecting a local Studio site to a shared WordPress.com site.
  • Synchronize your local and hosted sites at any time with one click.

Studio is an excellent tool to have in your development arsenal, and you can download it for free, explore the docs, and become a contributor on GitHub.

State of the Word Tokyo

Automattic, Design, Video, WordPress

It’s a dream come true being here in Tokyo for State of the Word 2024. We’re going to be in an amazing venue that looks over the city. Most of WordPress and Automattic’s senior leadership is here, and we’ll also have several hundred folks from the local community and press.

(Update: If you’d like a fantastic recap of how the event went, check out this post on .org.)

We’ve gotten so much inspiration over the years from Japanese culture, we wanted to make this event really “of the space” so we’re doing a few extra things this year. My presentation will include Mary Hubbard and Matías Ventura, but also part of it will be in Japanese and presented by Junko Fukui Nukaga. We’ll have piano performances by Aiko Takei. After the presentation and Q&A we’ll do a panel in Japanese with Mieko Kawakami (one of the top novelists in Japan, on par with Haruki Murakami), Craig Mod, Hajime Ogushi, and Genki Taniguchi.

For those who can attend in person, we’ll have a reception afterward with some unique gifts including posters from a local Kanji artist and nice sweater to keep everyone warm this winter.

If you’d like to livestream at home, you can do so on Youtube here:

My Freedom of Speech

Automattic, Design, New York, WordPress

WP Engine has filed hundreds pages of legal documents seeking an injunction against me and Automattic. They say this is about community or some nonsense, but if you look at the core, what they’re trying to do is ask a judge to curtail my First Amendment rights.

The First Amendment is the basis of our democracy. It is inconvenient and important. It’s also short, so I’m going to quote the First Amendment in its entirety:

Congress shall make no law respecting an establishment of religion, or prohibiting the free exercise thereof; or abridging the freedom of speech, or of the press; or the right of the people peaceably to assemble, and to petition the Government for a redress of grievances.

This means that, with rare exceptions, the government cannot tell you not to say something.

Freedom of Speech is not Freedom of Reach

The First Amendment says I should be able to state facts and my opinions about WP Engine. However, the New York Times is not required or compelled to publish them in their newspaper and distribute them to their subscribers.

WP Engine is free to publish whatever GPL code they want to the world. WordPress.org should not be compelled to distribute it or provide it free hosting.

Quiet For A While

After this post, I will refrain from personally commenting on the WP Engine case until a judge rules on the injunction. I will continue to exercise my First Amendment rights to promote others’ speech. However, I hope others speak up on our battle with WP Engine, and I will boost their speech wherever I can.

Response to DHH

Automattic, Design, Open Source, Politics, WordPress

I’ve taken this post down. I’ve been attacked so much the past few days; the most vicious, personal, hateful words poisoned my brain, and the original version of this post was mean. I am so sorry. I shouldn’t let this stuff get to me, but it clearly did, and I took it out on DHH, who, while I disagree with him on several points, isn’t the actual villain in this story: it’s WP Engine and Silver Lake.

A few bullets to his core points:

  • The headline “Automattic is doing open source dirty” is not fair.
  • Automattic did not work on a deal with WP Engine for 18+ months because of the GPL, or them using “WP” in their name, it was because of their abuse of the WordPress and WooCommerce trademarks. Trademarks must be protected, as evidenced by Rails trademark policy.
  • Our C&D is about public trademark abuse; theirs is about censorship, and doxxes private messages. They have since filed a kitchen sink lawsuit that embroils all of WordPress.org.
  • Updating ACF to Secure Custom Fields in our directory was to provide users of our plugin directory the best, safest, most secure code. It included a security update that still has not been merged by the ACF team.
  • We will merge any improvements ACF makes to their GPL code going forward and will also include enhanced functionality in the coming days to provide a secure and free drop-in replacement for ACF. If WP Engine didn’t want this to happen, they should not have published their code under the GPL or distributed it through WordPress.org’s directory.
  • I think it’s fantastic when businesses are built on open source, the WordPress ecosystem is at least 10B+ a year; Automattic and WP Engine are less than 5% of that.

Automattic Alignment

Automattic, Design, WordPress

Winston Churchill said, “Never let a good crisis go to waste.” Since I last blogged here, WP Engine filed a meritless lawsuit and Automattic responded, and there’s been a hurricane of public activity and press. Inside of Automattic, there’s been a parallel debate and process.

Silver Lake and WP Engine’s attacks on me and Automattic, while spurious, have been effective. It became clear a good chunk of my Automattic colleagues disagreed with me and our actions.

So we decided to design the most generous buy-out package possible, we called it an Alignment Offer: if you resigned before 20:00 UTC on Thursday, October 3, 2024, you would receive $30,000 or six months of salary, whichever is higher. But you’d lose access to Automattic that evening, and you wouldn’t be eligible to boomerang (what we call re-hires). HR added some extra details to sweeten the deal; we wanted to make it as enticing as possible.

I’ve been asking people to vote with their wallet a lot recently, and this is another example!

159 people took the offer, 8.4% of the company, the other 91.6% gave up $126M of potential severance to stay! 63.5% were male. 53% were in the US. By division it impacted our Ecosystem / WordPress areas the most: 79.2% of the people who took it were in our Ecosystem businesses, compared to 18.2% from Cosmos (our apps like Pocket Casts, Day One, Tumblr, Cloudup). 18 people made over 200k/yr! 1 person started two days before the deadline. 4 people took it then changed their minds.

It was an emotional roller coaster of a week. The day you hire someone you aren’t expecting them to resign or be fired, you’re hoping for a long and mutually beneficial relationship. Every resignation stings a bit.

However now, I feel much lighter. I’m grateful and thankful for all the people who took the offer, and even more excited to work with those who turned down $126M to stay. As the kids say, LFG!

Charitable Contributions

Design, Personal, WordPress

I knew going to war with Silver Lake, a $102B private equity firm, they would pull out every dirty trick to try to smear my name, do oppo research, imply I’m a mafia boss trying to extort them, etc.

I have kept my personal philanthropy private until now. I would like to offer up one piece of evidence for the public to consider, which is the IRS accounting of my 501c3 charitable donations.

This is something I’ve tried to keep quiet, because true philanthropy isn’t about recognition. As you can see, my personal liquidity goes up and down but I give back as much as I can when I can.

  • 2011: $295,044.60
  • 2012: $401,121.00
  • 2013: $2,088,890.88
  • 2014: $98,648.00
  • 2015: $101,947.00
  • 2016: $42,300.00
  • 2017: $51,562.50
  • 2018: $606,957.68
  • 2019: $620,802.65
  • 2020: $607,452.48
  • 2021: $2,151,602.26
  • 2022: $2,780,054.20
  • 2023: $2,276,425.06

If Lee Wittlinger, who controls Silver Lake’s investments in the WordPress ecosystem, or Heather Brunner, the CEO of WP Engine, would like to publish their charitable contributions over the past 12 years, they are welcome to do so.

Burning Man So Far

Design

This is my 9th Burning Man; I started coming in 2013. It’s incredible how much it has changed and evolved in that time. I love seeing all the technology and engineering advances every year. In my time it has gone from more fire and flashlights to LEDs with rainbow and color everywhere.

I drove in on Sunday, my first time driving in. Logistically, it’s been smooth so far regarding access to power and water, and of course, I set up a Starlink. ☺️ It’s also been a Goldilocks year with the weather and wind.

I swear this will be my last Burn with Micro-USB, which I consider my personal nemesis. Ultimate Ears has finally upgraded their Booms to USB-C (thank you Hanneke!) but Micro USB came back to bite me unexpectedly this year.

Burning Man is heaven for photographers; the dust makes everything look dramatic. I wanted to return to my “PhotoMatt” roots and shoot this year, so I resurrected back my big camera, a Nikon D5, and I’ve gotten some incredible shots. Burning Man has a principle of Radical Self Reliance, which I tried to practice, but the XQD reader I brought isn’t working. The D5 has a USB port you can connect to, but it’s the one I consider the most cursed of all USB ports: Micro USB B Data.

No one likes that connector.

People often ask me what Burning Man is like, it’s hard to answer because it’s very much “choose your own adventure.” People can and do have radically different experiences. For me, this year has had highlights that included seeing the most amazing whirling dervish with live music, talking to people coding visualizations on art pieces, and doing dishes! This year I’m camping with Maxa and my work shifts are with the kitchen team. Maxa is legendary for the love and care they put into food, so it’s been amazing to see the effort that goes into making meals for 100+ people three times a day in extreme conditions. As you can imagine, this generates a lot of dishes and I’ve made it a personal goal to be the best dishwasher ever, scrubbing every nook and cranny while trying to conserve water.

If I can get a cable or card reader to download photos, I’ll post them on my Tumblr, so keep an eye out for updates.

Anbernic, Sol, and Daylight

Audrey, Design, Tech, Video

I’m always trying out new things. First, something fun: my friend Jesse gifted me a very cool Gameboy-like device called the Anbernic RG35XX, at ~$46. It has almost every game you remember, like if you got all the cartridges at Toys R Us or checked them out at Blockbuster. Having something without Wi-Fi, notifications, etc., is nice to relax. Very fun. I’m also keeping my eye on Palmer Luckey’s new ModRetro.

Second, I give to you the Sol E-reader, $399, basically glasses with a Kindle built-in, and a remote you hold in your hand for turning pages. The website is slick, even the packaging and design was nice, but the product is not. Do not buy this. It’s really not pleasant to use. The resolution was so low and the typography so bad it felt like reading on a TI-89 calculator.

Third, I’ve been really enjoying the DC-1 Daylight Computer, $729, which is like if a Kindle mixed with an iPad in the best possible way. This feels like an actually new platform, in that I find myself imagining new ways and places (like outdoors) I’d want to spend time with it. It runs Android, so you can have any app on it, even code on it. This video gives a good sense of the device and its founder Anjan Katta:

I could see Daylight being fantastic for kids as well; it just feels less “toxic” than the hyper-display world in which smartphones have us trapped. Audrey invested back in 2022 and it’s awesome to see how this turned out, it’s so rare that hardware makes it to this stage. I’ve shifted a lot of my nighttime consumption and play over to the Daylight; it’s so fun to play chess or read an article. It has surpassed the Kindle as my favorite reading device. And it looks good everywhere:

I used the Daylight a lot on the recent Sydney to Hamilton Island ~1,000 mile transport I did with the Drumfire crew and my friend Herman/John, which was part of my “learning to sail” goal for this year.

WP21

Design, Review, Themes, WordPress

It seems like just yesterday WordPress was becoming a teenager, and in a blink of the eye it’s now old enough to drink! 21 years since Mike and I did the first release of WordPress, forking Michel’s work on b2/cafélog.

There’s been many milestones and highlights along the way, and many more to come. I’ve been thinking a lot about elements that made WordPress successful in its early years that we should keep in mind as we build this year and beyond. Here’s 11 opinions:

  1. Simple things should be easy and intuitive, and complex things possible.
  2. Blogging, commenting, and pingbacks need to be fun. Static websites are fine, but dynamic ones are better. Almost every site would be improved by having a great blog.
  3. Wikis are amazing, and our documentation should be wiki-easy to edit.
  4. Forums should be front and center in the community. bbPress and BuddyPress need some love.
  5. Every plugin and theme should have all the infrastructure that we use to build WordPress itself—version control, bug trackers, forums, documentation, internationalization, chat rooms, P2, and easy pathways for contribution and community. We shouldn’t be uploading ZIPs in 2024!
  6. Theme previews should be great, and a wide collection of non-commercial themes with diverse aesthetics and functionality are crucial.
  7. We can’t over-index for guidelines and requirements. Better to have good marketplace dynamics and engineer automated feedback loops and transparency to users. Boundaries in functionality and design should be pushed. (But spam and spammy behavior deserves zero tolerance.)
  8. Feedback loops are so important, and should scale with usage and the entire community rather than being reliant on gatekeepers.
  9. Core should be opinionated and quirky: Easter eggs, language with personality even if it’s difficult to translate, jazzy.
  10. Everyone developing and making decisions for software needs to use it.
  11. It’s important that we all do support, go to meetups and events, anything we can to stay close to regular end-users of what we make.

A bonus: Playground is going to change everything. What would you add?

Fun fact: On May 27, 2003 I blogged “Working backwards, earlier tonight was great. Put WordPress out, which felt great.” as one sentence in a 953-word entry written from the porch of my parent’s house where I was accidentally locked out all night until my Dad left in the morning to go to work. Had no idea WordPress would be as big as it is. Earlier that night had set up WP for my friend Ramie Speight, and done some phone tech support for another friend Mike Tremoulet I had met through the local blogger meetup. My friends from high school all had their own domains with WP and that feedback loop was magical for shaping the software.

Vision Pro First Impressions

Design, Review

Okay… wow. The hardware and display are like nothing I’ve ever seen, really feels like it’s from the future. That said, I found the setup clunky and buggy. Some might have been user error, for example I kept trying to “select” things with my middle finger and thumb and not my left finger.

I almost got stuck in the Persona setup, couldn’t continue. I don’t love how my Persona looks. Looking and selecting stopped working and I could only continue by physically reaching out and hitting the buttons. (This must sound ridiculous to someone who hasn’t used a Vision Pro yet. I looked pretty silly!)

I got totally stuck at the part of the setup where it was importing iCloud apps from backup, and I was ready to give up. A friend put it on and was able to get past that step for me. Adding credit cards was a terrible UI, with the security code PIN pad in front of the interface.

I decided to call it a night, and try more tomorrow. Just like I learned to type I think I’m going to need to learn to become fluent in this new interaction paradigm. I did have a before and after feeling, like the world had shifted, not unlike when you saw the first iPod or iPhone. This post probably doesn’t make any sense to someone who hasn’t tried the Vision Pro, but hopefully the team sees it and can take this feedback.

The Wix Mobile App, a WordPress Joint

Design, Open Source, WordPress

Anyone who knows me knows that I like to try new things — phones, gadgets, apps. Last week I downloaded the new Wix (closed, proprietary, non-open-sourced, non-GPL) mobile app. I’m always interested to see how others tackle the challenge of building and editing websites from a mobile device.

I started playing around with the editor, and felt… déjà vu. It was familiar. Like I had used it before.

Turns out I had. Because it’s WordPress.

If I were being charitable, I’d say, “The app’s editor is based on the WordPress mobile app’s editor.” If I were being honest, I’d say that Wix copied WordPress without attribution, credit, or following the license. The custom icons, the class names, even the bugs. You can see the forked repositories on GitHub complete with original commits from Alex and Maxime, two developers on Automattic’s mobile team. Wix has always borrowed liberally from WordPress — including their company name, which used to be Wixpress Ltd. — but this blatant rip-off and code theft is beyond anything I’ve seen before from a competitor.

Dear Wix,

This explicitly contravenes the GPL, which requires attribution and a corresponding GPL license on whatever you release publicly built on top of GPL code. The GPL is what has allowed WordPress to flourish, and that let us create this code. Your app’s editor is built with stolen code, so your whole app is now in violation of the license.

I suppose we’ll take this as a compliment — I’m sure the hundreds of people who have contributed to WordPress Core and our mobile apps are flattered that you chose to build one of your company’s core features using our code. We’re also excited to see what great things you create with all the time you saved not having to write your own mobile editor.

You know what’d be even more exciting? To see you abide by the GPL and release your source code back to the community that gave you that jump start.

I’ve always said that the GPL isn’t about limits, it’s about possibilities. In open source software, you trade some of your control as a developer to better serve the developer community and the people using your sites and products. I don’t think that’s a limit, I think it’s a way to make sure we encourage innovation and momentum. If you want to close the door on innovation, Wix, that’s your decision to make — just write your own code. If you’re going to join the open source community, play by the open source rules.

Release your app under the GPL, and put the source code for your app up on GitHub so that we can all build on it, improve it, and learn from it.

Love,
Matt and the open source community

An Update

The CEO of Wix has posted a response on their blog. I’ll also try to post my response it to the comments there. Miriam Schwab also has a very good response.

We were all very surprised by your post, as you have so many claims against us.

Wow, dude I did not even know we were fighting.

It’s not a fight: the claim is that the Wix mobile apps distribute GPL code and aren’t themselves GPL, so they violate the license.

First, you say we have been taking from the open source community without giving back, well, of course, that isn’t true. Here is a list of 224 projects on our public GitHub page, and as you can see they are all dated before your post. We have not checked if WordPress is using them, but you are more than welcome to do so, some of them are pretty good.

Very glad your company has projects on GitHub! Thank you for the offer to use them; if we do, we’ll make sure to follow the license you’ve put on the code very carefully.

Releasing other open source projects doesn’t mean that you can violate the license of the editor code you distributed in your mobile apps. To repeat my earlier points: since you distributed GPL code with your apps, the entire apps need to be released at GPL, not just your modifications to that one library.

As this Hacker News comment put it, “Open source is not a swap meet; you can’t violate a license if you voluntarily release some other code to make up for it.”

We always shared and admired your commitment to give back, which is exactly why we have those 224 open source projects, and thousands more bugs/improvements available to the open source community and we will release the app you saw as well.

If you were to release the entire source code of the apps under GPL that would bring you back into compliance with the license you violated. I think you’re saying you will do that here, but can you clarify? When should we look for the app code to be released, and where? That would resolve this issue completely.

Next, you talk about the Wix App being stolen from WordPress. There are more than 3 million lines of code in the Wix application, notably the hotels/blogs/chat/eCommerce/scheduling/booking is all our code.

I said the app includes stolen code. It doesn’t matter if it’s 30 lines or 30 million lines: because it includes GPL code and you distributed the app, the entire thing needs to be GPL. If you release the entire app’s code, as I think you said you would, then that resolves the license violation.

Yes, we did use the WordPress open source library for a minor part of the application (that is the concept of open source right?), and everything we improved there or modified, we submitted back as open source, see here in this link – you should check it out, pretty cool way of using it on mobile native. I really think you guys can use it with your app (and it is open source, so you are welcome to use it for free). And, by the way, the part that we used was in fact developed by another and modified by you.

Thank you for admitting you used the code and not trying to hide it. The issue isn’t the changes you made, it’s that including the editor means you need to submit the entire app as open source, which you have not yet — it’s completely proprietary.

If you want to read the account from Tal Kol, one of the leading engineers on this project, here it is. He was really happy to share his side of the story.

I have seen it, and it already has a number of good comments on it, including this one: “Can you address this point made in Matt’s post: ‘This explicitly contravenes the GPL, which requires attribution and a corresponding GPL license on whatever you release publicly built on top of GPL code’.” It appears you and Tal might share a misunderstanding of how the GPL works — software licensing can be tricky and many people make honest mistakes. (If you want to get into serious detail, this comment lays the licensing requirements out clearly.) It is easy to rectify this one: release your apps as open source under the GPL.

Now, what is this thing about us stealing your branding? Our product was always called Wix and our website Wix.com, we never borrowed from your marketing or brand.

Sorry for including this distraction; I was referring specifically to the fact that Wix used to go by “Wixpress.” You can see this in your Form F-1, and there used to be a support page about this on your site:

Although that is still in Google, the page it links to now mysteriously returns a 404 error, which you may want to look into.

In fact, if I remember correctly, until recently the Automattic home page was all about blogs and only recently it has become “websites.” Also, your business model changed to almost exactly the one we had for years. Can it be that you guys are borrowing from us? If so, again, you are welcome to it.

The Automattic home page has been a series of haiku about our products since 2009, pretty much unchanged — I think you mean the WordPress.com home page here. WordPress has been used for creating websites, not just blogs, since our 1.5 release in 2005 added themes and pages. In my 2014 State of the Word address I talked about how 87% of WordPress sites use it as a CMS. We regularly test dozens of variations of the WP.com homepage and some of them definitely emphasize website creation. I will say we look to Wix, Weebly, and Squarespace as innovators in the space with products that reach many small businesses, and Wix especially should be commended for its success and growth as a public company.

If you believe that we need to give you credit, that you deserve credit, I must say, absolutely yes. You guys deserve a lot of credit, but not because of a few lines of source code, you deserve credit because you guys have been making the internet dramatically better, and for that we at Wix are big fans. We love what you have been trying to do, and are working very hard to add our own contribution to make the internet better.

Thank you very much, that is kind. I do think there are a lot of values we share in common and would love to see this one issue resolved.

If you need source code that we have, and we have not yet released, then, most likely we will be happy to share, you only need to ask. We share your belief that making the internet better, is best for everyone.

That’s what my post was asking, for you to release the code. To quote my original letter: “Release your app under the GPL, and put the source code for your app up on GitHub so that we can all build on it, improve it, and learn from it.”

Finally, during the last couple of years, I reached out a couple of times trying to meet with you. Could I do that again here? I believe in friendly competition, and as much fun as it is to chat over the blogosphere, maybe we can also do it over a cup of coffee?

Once this is resolved I’d be happy to meet up. I believe when we exchanged emails in 2014 there was trouble finding overlap in our travel schedules.

I hope the above clarifies where we think Wix made a mistake, and how to fix it.

Dance to Calypso

Automattic, Design, WordPress

One of the hardest things to do in technology is disrupt yourself.

But we’re trying our darndest, and have some cool news to introduce today. When I took on the responsibility of CEO of Automattic January of last year, we faced two huge problems: our growth was constrained by lack of capital, and the technological foundations of the past decade weren’t strong enough for the demands of next one.

The first has a relatively straightforward answer. We found some fantastic partners, agreed on a fair price, issued new equity in the company to raise $160M, and started investing in areas we felt were high potential, like this year’s WooCommerce acquisition. This “war chest” gives us a huge array of options, especially given our fairly flat burn rate — we don’t need to raise money again to keep the company going, and any capital we raise in the future will be purely discretionary. (Since last May when the round happened we’ve only spent $3M of the investment on opex.)

The second is much harder to address. The WordPress codebase is actually incredible in many ways — the result of many thousands of people collaborating over 13 years — but some of WordPress’ greatest strengths were also holding it back.

The WordPress codebase contains a sea of institutional knowledge and countless bug fixes. It handles hundreds of edge cases. Integrates constant security improvements. Is coded to scale. Development moves at a fast clip, with six major releases over the past two years and more around the corner. Its power and flexibility is undeniable: WordPress just passed a huge milestone, and now powers 25% of the web. You can run it on a $5-a-month web host, or scale it up to serve billions of pageviews on one of the largest sites on the web, WordPress.com.

The interface, however, has been a struggle. Many of us attempted to give it a reboot with the MP6 project and the version 3.8 release, but what that release made clear to me is that an incremental approach wouldn’t give us the improvements we needed, and that two of the things that helped make WordPress the strong, stable, powerful tool it is — backward compatibility and working without JavaScript — were actually holding it back.

The basic paradigms of wp-admin are largely the same as they were five years ago. Working within them had become limiting. The time seemed ripe for something new, something big… but if you’re going to break back compat, it needs to be for a really good reason. A 20x improvement, not a 2x. Most open source projects fade away rather than make evolutionary jumps.

So we asked ourselves a big question. What would we build if we were starting from scratch today, knowing all we’ve learned over the past 13 years of building WordPress? At the beginning of last year, we decided to start experimenting and see.

Today we’re announcing something brand new, a new approach to WordPress, and open sourcing the code behind it. The project, codenamed Calypso, is the culmination of more than 20 months of work by dozens of the most talented engineers and designers I’ve had the pleasure of working with (127 contributors with over 26,000 commits!).

gm-2015-final

Calypso is…

  • Incredibly fast. It’ll charm you.
  • Written purely in JavaScript, leveraging libraries like Node and React.
  • 100% API-powered. Those APIs are open, and now available to every developer in the world.
  • A great place to read, allowing you to follow sites across the web (even if they’re not using WordPress).
  • Social, with stats, likes, and notifications baked in.
  • Fully responsive. Make it small and put it in your sidebar, or go full-screen.
  • Really fun to write in, especially the drag-and-drop image uploads.
  • Fully multi-site for advanced users, so you can manage hundreds of WordPresses from one place.
  • Able to manage plugins and themes on Jetpack sites, including auto-upgrading them!
  • 100% open source, with all future development happening in the open.
  • Available for anyone to adapt to make their own, including building custom interfaces, distributions, or working with web services besides WordPress.com.

A lot of people thought we should keep this proprietary, but throughout my life I’ve learned that the more you give away, the more you get back. We still have a ton to figure out around plugins, extensibility, contributions, Windows and Linux releases, API speed, localization, and harmonizing the WordPress.com API and WP-API so it can work with core WordPress. Thousands more PHP developers will need to become fluent with JavaScript to recreate their admin interfaces in this fashion. I’m also really excited to revisit and redesign many more screens now that we have this first version out the door.

This is a beginning, not an ending. (1.0 is the loneliest.) Better things are yet to come, as all of you dig in. Check out these links to read more about Calypso from different perpsectives:

This was a huge bet, incredibly risky, and difficult to execute, but it paid off. Like any disruption it is uncomfortable, and I’m sure will be controversial in some circles. What the team has accomplished in such a short time is amazing, and I’m incredibly proud of everyone who has contributed and will contribute in the future. This is the most exciting project I’ve been involved with in my career.

With core WordPress on the server and Calypso as a client I think we have a good chance to bring another 25% of the web onto open source, making the web a more open place, and people’s lives more free.

If you’re curious more about the before and after, what’s changed, here’s a chart:

Whats-New-WPcom@2x