The now-forming Incident Response Team (IRT) is a community-led effort to help us all build and sustain a culture around WordPress that is healthy, inclusive, and safe. Angela Jin is calling for your nominations for a diverse group of people who can contribute by serving on the IRT.
It’s still far from simple to do well — let alone do better — what was first possible in the Web 1.0 era, even before WordPress was born. Thoughts on “WordPress Lite” and “Create Once, Publish Everywhere.”
🎧 Podcasts worth catching: “Tumblr can be a better Twitter than Twitter ever was.” • The unfolding recession. • Catch up with GitHub Actions • How to think about accessibility and the things we forget about being inclusive and open.
Allie Nimmons wrote a really good take on this question in last week’s issue … Read more
I didn’t have a chance to dig into Daniele Scasciafratte‘s report and analysis regarding … Read more
Thomas Nachbar of the University of Virginia School of Law writes in “Why We … Read more
We’ve seen forced updates become increasingly common and less controversial over time. But who decides, and how is that decision made? Are there unofficial channels and processes, like a decision tree, for escalating to a forced update?
Post Status members discuss declining revenue — and how to offset it. How will the market slump affect acquisitions and sale prices?
The Post Status podcast picks of the week include two takes on selling businesses, going back to work for someone else, and then… Chris Coyier and Corey Maas tell their stories. • Daisy Olson has the lowdown on block themes. • Raquel Landefeld on the power of community. • Press the Issue launches a solidly journalistic WordPress podcast with Allie Nimmons investigating the pandemic’s impact on WordCamps for the first episode.
Deeper, thoughtful insight and analysis make slower work and harder to come by. I hope to model it once in a while, and we’ve got more in the bin. We want to invite especially our business members to submit story ideas, questions, sources, and articles for publication at Post Status.
What if WordPress, growing as an operating system for the web, spawns distributions and spins, like Linux? What do nine years of Jetpack teach us about Automattic and WordPress — the project and the dot-com? Rethinking how we think about SaaS, hosting, and the WordPress ecosystem…
Gutenberg 13.4 • Learning FSE sooner rather than later • Gutenberg in Tumblr and Day One • WordCamps and the vitality of the WordPress community • AUS WordPress community only mostly dead? • Get SEO Schema graphs • Web font loading geek out • PHP is 28! • PHP namespaces and autoloaders • You can work anywhere… why not Cleveland? • North Commerce — faster than the rest? • and more…
Our WordPress Podcast and Video Picks for the Week of June 13 🎙️ JavaScript development journeys • Questions coming out of WCEU • The WordPress toolkit for podcasters • How newcomers and outsiders view WordPress • Are WordPress developers “real developers?” • Gutenber changes • Dave Martin on WP.com • A Gutenberg roadmap for WordPress 6.1.
It’s a good time to celebrate growth, maturity — and longevity. This is our 500th issue. WordPress is 19! And the 6.0 release is just a few days old, with new and old hands contributing from all over the world. Many are “developers” of some kind. Those who are showing up every day to make the project work and to make a living in WordPress are the professionals. Here’s to them!
In an alternate universe two WordPress “products” exist: the WordPress we know today plus a slimmed-down or highly streamlined “lite” version. We gather a panel of WordPress professionals to ask “what if” and “what could be done” and “would it be practical?”
© 2024 Post Status. All rights reserved
