As 2022 comes to an end, State of the Word will happen in NYC again. Apply to attend or tune in to the livestream. Check out the beta version of the WordPress Developer Blog. Still have sites on WordPress 3.7 – 4.0? It’s really time to upgrade as this will receive no further updates after December 1. It’s team rep nomination time too.
Sparked by Magne Ilsaas‘s ideas in The WordPress Enterprise Paradox, Tom started a Twitter thread and hosted a live discussion with Magne and others at enterprise WordPress agencies this week. Their main concern is the challenges that arise from not having a well-defined brand and market that allows “WordPress for the Enterprise” to stand out — without being ties to a particular WordPress company or host. After getting an outline of the problem as it stands today, I asked Tom what might help differentiate “Enterprise WordPress” as a collective or entire ecosystem of agencies operating within it. Can open-source values of sharing and cooperation shape a unique global identity for enterprise WordPress agencies? Is it time for an inter-agency association or “guild” to take on these challenges?
Time to update, WordPress 6.1.1 is out! GitHub has made Codespaces available for 60 hours/month, and WordPress is exploring Core contribution integrations with
wordpress/wordpress-develop. It’s team rep nomination time too.
The journey to GiveWP 3.0 is well underway — an open, iterative development process that fully embraces WordPress’s Gutenberg block editor. Give cofounder Matt Cromwell and development director Jason Adams share what they’ve learned so far.
James Farmer’s WordPress story goes all the way back to his launch of the first hosted WordPress multisite blogging platform — just a few days ahead of WordPress.com. Edublogs currently hosts millions of students’ and educators’ blogs. James talks about successes and failures, his views on Gutenberg, how he stays competitive with Squarespace, and how he thinks the WordPress business community should respond to the loss of active install growth data at WordPress.org.
This week was all about revisiting and continuing conversations that have special value and maybe for that reason tend to continue on with a life of their own. Tom Willmot dropped a fine Twitter thread about the challenge all enterprise WordPress agencies face. This came in response to Magne Ilsas‘ featured post here last week, The WordPress Enterprise Paradox. In a similar theme of industry peer cooperation, Eric Karkovack asks if WordPress product owners and developers can see a common interest in “voluntary standards.” Could this clean up the plugin market? James Farmer thinks the WordPress business community can do more for itself too — by sharing data. In Post Status Slack we’re learning the tricks and trials of ranking in the WordPress.org plugin repository. How about plugin telemetry? Learn from the voices of experience.
Get a look at the latest default theme, Twenty Twenty-Three! 🎨 Full Site Editing has a new name: “Site Editor.” 📝 And WordPress 6.1.1 will be released on November 15. 📅
#WordPress 6.1 was released on November 1. ✨ Check out all the updated and revised support articles. 📖 Learn about #accessibility and contributor Raghavendra Satish Peri from the WordPress India community. 🇮🇳
WordPress 6.1 rolls out on November 1. Help test 6.1 Release Candidate 3 — and the Rollback feature plugin. Be sure to look over the 6.1 DevNotes, Field Guides, and Team Updates.
This week in an article shared in Post Status Slack, Eric Karkovack suggested some ways to improve the WordPress user experience, especially for DIY users setting up a website for the first time. Some of the things Eric wants to see happen, like a standard interface for plugins and a curated view of the plugin ecosystem, are also commonly expressed by designers, developers, and people in other roles at WordPress agencies serving enterprise clients. Can we get everyone to “yes” on a better UX?
Building, Supporting, and Selling a Winning Product — With or Without WordPress.org • Are Active Install Counts Relevant to Your Business’s Success? (Even if they are accurate? And they haven’t been.) • Let’s Fix What’s Broken (The Plugin Repo) Not What Isn’t (The Freemium Model) • Follow Leaders, Adopt Standards • Tools and expertise from rtCamp • Some great and “doable” ideas for the future of plugin business metrics on the .org repo. Could some of them help put an end to intrusive and manipulative dark patterns in the WordPress Admin dashboard and notifications?
This week I sat down again with Eric Karkovack to talk about the WordPress stories and topics that are on the top of our minds. Independently, we made nearly the same selections. There’s a single throughline in this episode — what works, what doesn’t, and what will take WordPress businesses forward in the product, agency, and hosting spaces.
Justin Labadie’s wishlist for the WordPress.org plugin repo:
1) Ensure all search results are relevant.
2) Standardize a Premium product upsell interface.
3) Make it possible to show other products by the same author.
Pretty snazzy new looks coming the the WordPress documentation site! You can help the Docs Team: Come to the first ever Documentation team Contributor Day on October 25th.
Get a sneak peek at WordPress 6.1 with Nick Diego. Help test 6.1 Release Candidate 2 — and the Plugin Dependencies feature plugin. Be sure to browse the 6.1 DevNotes, Field Guides, and Team Updates. WP-CLI 2.7.1 is available now.
Good ideas for the future of data disclosed to plugin authors using the wordpress.org repository:
1) Identify surges of unhappy users reacting to a bad release — and the opposite, happier outcome.
2) Use pageview analytics to estimate total potential user interest and conversion rates.
3) Assess a plugin’s performance with the .org search algorithm, the quality of releases, and plugin incompatibility as well as PHP compatibility issues.
4) Collect significant user behavior data anonymously without phoning home.
5) Just reveal all the raw data with privacy options for individual authors — no interpretive analysis on wordpress.org.
BONUS: Let’s take this discussion somewhere else!
End of content
End of content