In open source, one thing that makes it even harder to ship great software is bringing together disparate groups of contributors who may have entirely different incentives or missions or philosophies about how to make great work. Working together on a team is such a delicate balance, and even one person rowing in the wrong direction can throw everyone else off.

That’s why periodically I think it is very healthy for open source projects to fork, it allows for people to try out and experiment with different forms of governance, leadership, decision-making, and technical approaches. As I’ve said, forking is beautiful, and forks have my full support and we’ll even link and promote them.

Joost is a self-proclaimed leader in the SEO space, an industry known for making the web better. He asked for and I gave him WordPress marketing leadership responsibility in January 2019 and he stepped down in June of 2019, I think we would both agree in those 5 months he was not effective at leading the marketing team or doing the work himself.

Karim leads a small WordPress agency called Crowd Favorite which counts clients such as Lexus and ABC and employs ~50 people.

Both are men I have shared meals with and consider of the highest integrity. I would trust them to watch any of my 15 godchildren for a day. These are good humans. Now go do the work. It probably won’t happen on day one, but Joost and Karim’s fork, which I’ll call JKPress until they come up with a better name, has a number of ideas they want to try out around governance and architecture. While Joost and Karim will be unilaterally in charge in the beginning, it sounds like they want to set up:

1. A non-profit foundation, with a broad board to control their new project.
2. A website owned by that foundation which hosts community resources like a plugin directory, forums, etc.
3. No more centralized and moderated plugin and theme directories with security guidelines or restrictions are what plugins are allowed to do like putting banners in your admin or gathering data, everything done in a federated/distributed manner.
4. The trademarks for their new project will either be public domain or held by their foundation.
5. “Modernization” of the technology stack, perhaps going a Laravel-like approach or changing how WordPress’ architecture works.
6. Teams and committees to make decisions for everything, so no single person has too much power or authority.

Karim has a similar post. Joost says he has the time and energy to lead:

Now, as core committer Jb Audras (not employed by me or Automattic) points out, within WordPress we have a process in which people earn the right to lead a release:

However in Joost and Karim’s new project, they don’t need to follow our process or put in the hours to prove their worth within the WordPress.org ecosystem, they can just lead by example by shipping code and product to people that they can use, evaluate, and test out for themselves. If they need financial or hosting support is sounds like WP Engine wants to support their fork:

Awesome! (Maybe it’s so successful they rebrand as JK Engine in the future.) WP Engine, with its half a billion in revenue and 1,000+ employees, has more than enough resources to support and maintain a legitimate fork of WordPress. And they are welcome to use all the GPL code myself and others have created to do so, including many parts of WordPress.org that are open source released under the GPL, and Gutenberg which is GPL + MPL.

Joost also is a major investor (owner?) in Post Status (which he tried to sell to me a few months ago, and I declined to buy, perhaps kicking off his consternation with me), so they have a news media site and Slack instance already ready to go. He also is an investor in PatchStack and appears to be trying to create a new business around something called Progress Planner, both of which could be incorporated into the new non-profit project to give them some competitive distinctions from WordPress.

To make this easy and hopefully give this project the push it needs to get off the ground, I’m deactivating the .org accounts of Joost, Karim, Se Reed, Heather Burns, and Morten Rand-Hendriksen. I strongly encourage anyone who wants to try different leadership models or align with WP Engine to join up with their new effort.

In the meantime, on top of my day job running a 1,700+ person company with 25+ products, which I typically work 60-80 hours a week on, I’ll find time on nights and weekends to work on WordPress 6.8 and beyond. Myself and other “non-sponsored” contributors have been doing this a long time and while we may need to reduce scope a bit I think we can put out a solid release in March.

Joost and Karim have a number of bold and interesting ideas, and I’m genuinely curious to see how they work out. The beauty of open source is they can take all of the GPL code in WordPress and ship their vision. You don’t need permission, you can just do things. If they create something that’s awesome, we may even merge it back into WordPress, that ability for code and ideas to freely flow between projects is part of what makes open source such an engine for innovation. I propose that in a year we do a WordPress + JKPress summit, look at what we’ve shipped and learned in the process, which I’d be happy to host and sponsor in NYC next January 2026. The broader community will benefit greatly from this effort, as it’s giving us a true chance to try something different and see how it goes.

On WP Engine’s homepage, they promise “Unmatched performance, automated updates, and bulletproof security ensure your sites thrive.”

WP Engine was well aware that we could remove access when they chose to ignore our efforts to resolve our differences and enter into a commercial licensing agreement. Heather Brunner, Lee Wittlinger, and their Board chose to take this risk. WPE was also aware that they were placing this risk directly on WPE customers. You could assume that WPE has a workaround ready, or they were simply reckless in supporting their customers. Silver Lake and WP Engine put their customers at risk, not me.

We have lifted the blocks of their servers from accessing ours, until October 1, UTC 00:00. Hopefully this helps them spin up their mirrors of all of WordPress.org’s resources that they were using for free while not paying, and making legal threats against us.

The WordPress.org redesign continues

Learn WordPress is the latest section of WordPress.org to receive a design refresh, following other sections like the Showcase and Developer Resources. It brings a unified look and feel that’s modern, visual, and inviting.

Beyond its fresh aesthetic, the new Learn WordPress site prioritizes learners with a revamped user experience consistent with familiar modern learning platforms. It features a new navigation menu, eye-catching thumbnails, and search filters so you can explore and discover content quickly. The clearer and more structured layout helps you easily recognize the resources you need (courses, lessons, Online Workshops) based on your learning preferences.  

Introducing Learning Pathways

This redesign also highlights a new approach to Learn WordPress content, emphasizing what learners engage with the most. The introduction of Learning Pathways lets you grow your WordPress skills progressively. You can start with beginner essentials and then work your way through more advanced concepts at your own speed. This method lets you build a solid understanding as you move through each course. Learning Pathways are geared toward specific learners, like people using WordPress for the first time or those interested in development.

Four Learning Pathways are already launched and ready to explore:

• Beginner WordPress User
• Intermediate WordPress User
• Beginner WordPress Developer 
• Intermediate Theme Developer

You can look forward to more Learning Pathways in the User and Developer tracks soon. Two additional pathways, Designer and Contributor, are also on the roadmap. For more details about Learning Pathways, listen to episode 83 of the WordPress Briefing.

Get a guided tour of all the exciting Learn WordPress changes from the Training team’s very own Jonathan Bossenger, Wes Theron and Kathryn Presner. Sign up for one of their upcoming Online Workshops on Tuesday, August 6 at 14:00 UTC or Thursday, August 8 at 21:00 UTC.

Education for the future of WordPress

What started with the Training team’s effort to understand the needs and expectations of current and future learners became a push to create a dynamic learning experience. This next phase of Learn WordPress is an exciting move toward bringing more people into WordPress, whether new users just getting started or established developers looking to add more skills to their toolbox.

If you want to propose a change or report an issue, please do so in the Learn GitHub repository. If you love WordPress and want to contribute to making Learn WordPress an even greater resource, join the #training Slack channel. Want to make an immediate impact? Share Learn WordPress with someone you know.

Thank you (and props) to all involved

The new Learn WordPress couldn’t have been possible without the effective collaboration of the Training, Design, Marketing, and Meta teams.

@adamwood @agiljulio @arunshenoy99 @bsanevans @burtrw @cnormandigital @devmuhib @digitalchild @dufresnesteven @ervanyuffrizal @faisalahammad @fcoveram @hellosatya @huzaifaalmesbah @indirabiswas27 @ironnysh @itsmhrahman @jinalparekh @joedolson @joen @jominney @keithnoseworthy @kel-dc @lada7042 @laurahartwigdesign @laurlittle @markoserb @mustakim5 @nazmul111 @ndiego @nilovelez @noruzzaman @orangeambition @piyopiyofox @psykro @renyot @rfluethi @rjfrizz @rmartinezduque @ryelle @sakibsnaz @sfougnier @shsajalchowdhury @sierratr @sumitsingh @teuila_mau @webcommsat @webtechpooja  @west7 @zoonini

This new design provides much-needed improvements to the aesthetics and user experience. It emphasizes bold visuals and a more dynamic browsing experience through tags and categories. Individual site pages now include desktop and mobile screenshots, while the site introduces an improved layout on mobile devices. 

This redesign also brings new block-based functionality and several components that will be used elsewhere on WordPress.org. All of this was made possible through collaboration between Design, Marketing, and Meta teams. Thank you to everyone.

@adamwood @alexstine @annezazu @bengreeley @cbringmann @chanthaboune @dufresnesteven @eidolonnight @fcoveram @joen @jonoaldersonwp @jpantani @laurlittle @matt @markoserb @ndiego @pablohoneyhoney @paulkevan @renyot @ryelle @sereedmedia @_dorsvenabili

If you would like to propose a change or report an issue, please do so in the wporg-showcase-2022  GitHub repository. Also, make sure to join the #website-redesign Slack channel if you are interested in additional updates coming to WordPress.org and want to contribute.

The new homepage brings more attention to the benefits and experience of using WordPress, while also highlighting the community and resources to get started. 

The new download page greets visitors with a new layout that makes getting started with WordPress even easier by presenting both the download and hosting options right at the top.

This redesign was made possible through great collaboration between Design, Marketing, and Meta teams. Thank you to everyone involved throughout this update:

@abuzon @adamwood @adeebmalik @alexandreb3 @alipawp @angelasjin @aniash_29 @annezazu @beafialho @bjmcsherry @chanthaboune @colinchadwick @crevilaro @critterverse @dansoschin @dd32 @dufresnesteven @eboxnet @eidolonnight @elmastudio @fernandot @geoffgraham @iandunn @javiarce @joedolson @jpantani @kellychoffman @laurlittle @marybaum @matt @maurodf @melchoyce @mikachan @nikhilgandal @pablohoneyhoney @peakzebra @poliuk @priethor @psmits1567 @renyot @rmartinezduque @ryelle @santanainniss @sereedmedia @sippis @tellyworth @tobifjellner @webdados @willmot

Your comments, including some feedback from the 2016 redesign, were taken into consideration with this work. Expect more updates to come as efforts to jazz up WordPress.org continue.

In June 2021, @beafialho in collaboration with @pablohoney floated the idea of giving WordPress News a new look. Today, those ideas become a reality—we’re excited to share that redesign of WordPress News is live!

The new design leans on the aesthetics of jazz, intrinsically connected to WordPress and which ultimately translates its uniqueness, historic significance and future potential. Among other improvements, the new design leaves more space for content and includes new typefaces for better readability. It also uses a color palette intended to reflect the evolving Gutenberg language.

The revamp of the WordPress News page includes the header and footer of the page. We also shipped those two global elements to all pages of WordPress.org. However, there’s more work to do within the header to improve the information architecture. This new design is just the first, small step to modernize and improve the site iteratively. Any further discussion on future redesigns will occur in the #design channel on Slack.

Take a look around and subscribe to WordPress News if you haven’t already. If you see something in the design that doesn’t look right, please submit an issue on GitHub.

Since our last birthday we developed our 40th release and now also support over 40% of the web. So it seems fitting that this year’s celebration should be a list of 40 milestones that have helped us get there.

Grab a slice of cake or festive beverage and give it a scroll!

New Theme and Plugin Directories

Since WordPress 3.8, you’ve been enjoying improved theme management in your WordPress admin, and in WordPress 4.0 plugin management was refined. We’ve brought these experiences from your admin and re-created them right here on WordPress.org.

Theme Directory

The Theme Directory has a better browsing experience, with handy tabs where you can view featured, popular, and the latest themes. As with the theme experience in your admin, you can use the feature filter to browse for just the right theme for your WordPress website.

Click on a theme to get more information about it, including shiny screenshots, ratings, and statistics.

Konstantin Obenland posted a good overview of everything involved with the theme directory overhaul and followed up with a post on improved statistics.

Plugin Directory

The Plugin Directory has a brand new theme that mirrors the experience in your WordPress admin, with a more visual experience, and better search and statistics.

As well as a facelift, there are some great new features for you to play around with:

• Favorites – when you’re logged in to you WordPress.org account, this page gives you direct access to the plugins that you have favorited.
• Beta Testing – try out plugins where developers are experimenting with new features for WordPress.
• Search by plugin author – you can search for a plugin author using their username.
• Better statistics – listings now display the number of active installs so you can see how many people are actually using a plugin.

An overview of the new theme was posted by Scott Reilly.

Better Statistics

We’ve made huge improvements to our statistics. This gives us more useful information about the WordPress versions people are using, their PHP version, and their MySQL version.

Already these new statistics have provided us with useful insights into WordPress usage.

• More than 43% of all sites are running the latest version of WordPress. Previously, we thought only 10% of sites were up-to-date. By excluding sites that are no longer online we were able to improve these statistics.
• We were able to clear up the data around WordPress 3.0, bringing it more in line with expectations. This anomaly was a by-product of spammers.
• Only 15.9% of sites are using PHP 5.2, which is better than we thought.

Over the coming months we’ll be able to use these statistics to bring you new tools and improvements, and to make more informed decisions across the board. Read Andrew Nacin’s post about these changes for more background.

Thanks!

Thanks to everyone who contributed to the theme directory redesign, the plugin directory refresh, and improved statistics: Alin Marcu, Damon Cook, Dion Hulse, Dominik Schilling, Jan Cavan Boulas, Konstantin Obenland, Kyle Maurer, Matías Ventura, Mel Choyce, Natalie MacLees, Paul de Wouters, Samuel Sidler, Samuel Wood (Otto), Scott Reilly, Siobhan McKeown.

If you want to help out or follow along with future WordPress.org projects, check out Make WordPress and our meta development blog.

At ten years, it’s fun to reflect on our beginnings. We launched WordPress on 27th May 2003, but that wasn’t inception. Go back far enough, and you can read a post by Michel Valdrighi who, frustrated by the self-hosted blogging platforms available, decided to write his own software; “b2, a PHP+MySQL alternative to Blogger and GreyMatter.” b2 was easy to install, easy to configure, and easy for developers to extend. Of all the blogging platforms out there, b2 was the right one for me: I could write my content and get it on the web quickly and painlessly.

Sometimes, however, life gets in the way. In 2002, Michel stopped maintaining b2. Over time, security flaws became apparent and updates were needed and, while the b2 community could write patches and fixes, no one was driving the software forward. We were lucky that Michel decided to release b2 under the GPL; the software may have been abandoned, but we weren’t without options. A fork was always a possibility. That was where it stood in January 2003, when I posted about forking b2 and Mike responded. The rest, as they say, is history.

From the very beginning to the present day, I’ve been impressed by the thought, care, and dedication that WordPress’ developers have demonstrated. Each one has brought his or her unique perspective, each individual has strengthened the whole. It would be impossible to thank each of them here individually, but their achievements speak for themselves. In WordPress 1.2 the new Plugin API made it easy for developers to extend WordPress. In the same release gettext() internationalization opened WordPress up to every language (hat tip: Ryan Boren for spending hours wrapping strings with gettext). In WordPress 1.5 our Theme system made it possible for WordPress users to quickly change their site’s design: there was huge resistance to the theme system from the wider community at the time, but can you imagine WordPress without it? Versions 2.7, 2.8, and 2.9 saw improvements that let users install and update their plugins and themes with one click. WordPress has seen a redesign by happycog (2.3) and gone under extensive user testing and redesign (Crazyhorse, Liz Danzico and Jen Mylo, WordPress 2.5). In WordPress 3.0 we merged WordPress MU with WordPress — a huge job but 100% worth it. And in WordPress 3.5 we revamped the media uploader to make it easier for people to get their images, video, and media online.

In sticking to our commitment to user experience, we’ve done a few things that have made us unpopular. The WYSIWYG editor was hated by many, especially those who felt that if you have a blog you should know HTML. Some developers hated that we stuck with our code, refusing to rewrite, but it’s always been the users that matter: better a developer lose sleep than a site break for a user. Our code isn’t always beautiful, after all, when WordPress was created most of us were still learning PHP, but we try to make a flawless experience for users.

It’s not all about developers. WordPress’ strength lies in the diversity of its community. From the start, we wanted a low barrier to entry and we came up with our “famous 5 minute install”. This brought on board users from varied technical background: people who didn’t write code wanted to help make WordPress better. If you couldn’t write code, it didn’t matter: you could answer a question in the support forums, write documentation, translate WordPress, or build your friends and family a WordPress website. There is space in the community for anyone with a passion for WordPress.

It’s been wonderful to see all of the people who have used WordPress to build their home on the internet. Early on we got excited by switchers. From a community of tinkerers we grew, as writers such as Om Malik, Mark Pilgrim, and Molly Holzschlag made the switch to WordPress. Our commitment to effortless publishing quickly paid off and has continued to do so: the WordPress 1.2 release saw 822 downloads per day, our latest release, WordPress 3.5, has seen 145,692 per day.

I’m continually amazed by what people have built with WordPress. I’ve seen musicians and photographers, magazines such as Life, BoingBoing, and the New York Observer, government websites, a filesystem, mobile applications, and even seen WordPress guide missiles.

As the web evolves, WordPress evolves. Factors outside of our control will always influence WordPress’ development: today it’s mobile devices and retina display, tomorrow it could be Google Glass or technology not yet conceived. A lot can happen in ten years! As technology changes and advances, WordPress has to change with it while remaining true to its core values: making publishing online easy for everyone. How we rise to these challenges will be what defines WordPress over the coming ten years.

To celebrate ten years of WordPress, we’re working on a book about our history. We’re carrying out interviews with people who have involved with the community from the very beginning, those who are still around, and those who have left. It’s a huge project, but we wanted to have something to share with you on the 10th anniversary. To learn about the very early days of WordPress, just after Mike and I forked b2 you can download Chapter 3 right here. We’ll be releasing the rest of the book serially, so watch out as the story of the last ten years emerges.

In the meantime, I penned my own letter to WordPress and other community members have been sharing their thoughts:

• Mike Little on our Ten Year Journey.
• Core contributor Helen Hou-Sandi wishes WordPress happy birthday.
• Peter Westwood on a decade gone.
• Support rep Mika Epstein on her WordPress journey.
• Dougal Campbell celebrating with his wife, Suze.
• Otto on how WordPress affected him.

You can see how WordPress’ 10th Anniversary was celebrated all over the world by visiting the wp10 website, according to Meetup we had 4,999 celebrators.

To finish, I just want to say thank you to everyone: to the developers who write the code, to the designers who make WordPress sing, to the worldwide community translating WordPress into so many languages, to volunteers who answer support questions, to those who make WordPress accessible, to the systems team and the plugin and theme reviewers, to documentation writers, event organisers, evangelists, detractors, supporters and friends. Thanks to the jazzers whose music inspired us and whose names are at the heart of WordPress. Thanks to everyone who uses WordPress to power their blog or website, and to everyone who will in the future. Thanks to WordPress and its community that I’m proud to be part of.

Thank you. I can’t wait to see what the next ten years bring.

Final thanks to Siobhan McKeown for help with this post.

Our first focus was around improving the discussion and support around plugins.

You’ll now notice that threads about a plugin are pulled directly into a “support” tab on the plugin page — each plugin has its own forum. We’ve made authors much more prominent and with bigger Gravatars and better placement, so you can get a sense of who made the plugin you’re using. And finally to show how active and well-supported a plugin is, you can see  “16 of 75 support threads in the last two weeks have been resolved.” Finally, if you’re logged in you get access to the new “favorites” feature that lets you mark the plugins you use the most so you can share them on your profile page and find them quickly later. We soft-launched favorites a few days ago and there have already been 2,000 saved!

If you’re a plugin author, we’ve started with a short threshold (2 weeks) for the resolved stats so it’s easy to catch up and stay on top of it. (It’ll eventually go to two months.) You also now have the ability to set stickies on your plugin forum to put FAQs or important information at the top, and of course any person you put as a committer on the plugin will have moderation access. People on the forum tag will see your custom header and links to the other resources attached to your plugin.

We’ve tightened up the styling a bit on the forums and plugin pages, though still some cleanups to do there. Some older improvements you might have missed, but are still useful for users and developers alike:

• “Plugin headers” or those cool graphics you see at the top of plugin pages have really taken off, there are over 1,600 active now.
• You can now subscribe to get an email whenever a commit is made to a plugin repository even if it isn’t yours. There is no better way to follow the development of your favorite plugins. There’s nothing like the smell of fresh changesets in the morning.
• Behind the scenes, we’ve dramatically ramped up proactive scanning of the entire repository to help authors fix security and other problems they might not even know about yet. The quality level of the repo has gone way, way up.

All of this will continue to evolve as we get feedback and see usage, but we’re happy to have been able to make some key improvements in just a few days while hanging out in Memphis. (This is why WordCamps usually have BBQ — it imparts magical coding powers.)