WordPress Community Roundup
A New Home for the WordPress Community? RSS Friends • WP community stories of the pandemic • The History of Screen Readers • Dumb questions about disability • “Crip Time”
A New Home for the WordPress Community? RSS Friends • WP community stories of the pandemic • The History of Screen Readers • Dumb questions about disability • “Crip Time”
Tom Willmot on the Challenges and Opportunities Facing Enterprise WordPress • Tom Lach on the costs of rapid growth — It’s not for everyone • The Future of GiveWP and the Block Editor • Evolving Edupack — and Sunsetting It • and more…
Tech jargon and analysts with acronyms. Buzzwords and ranking voodoo. Where does WordPress fit in the enterprise tech industry? A guide for the genuinely curious or perplexed.
Post Status has been a haven for kindness and generosity, but it’s thanks to our members, readers, listeners, colleagues, and friends that the work we do together and the fun we have is good, meaningful, and regenerative for our community. On that note, this is my last post in my role as editor at Post Status…
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?
Jetpack and WordPress.com can publish to Telegram. The ultimate gitignore for WordPress projects.
As a followup to my note in August on this topic, here’s what Tom … Read more
Back in July, Sabina Ionescu published a lot of different responses from people in … Read more
Back in August, Oliver Sild announced in Post Status Slack that Patchstack was opening … Read more
Bob puts out so much writing and audio at Do the Woo and has … Read more
This is an important topic that came out of a Post Status Slack #security … Read more
I wish this was a WordPress story. It should’ve been and could still be … Read more
Critical OpenSSL vulnerability • Australia raises fines for data breaches • Apple only commits to patching the latest OS • EU may require secure code and timely patches.• NSA/CISA guidance for software developers and suppliers
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.
Who’s doing the four-day work week in WordPress? • What good sources for professional development have you found? • Getting your implementation intentions right.
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.