It’s time for another weekly roundup of WordPress-related articles and resources. If you have written your own post or know of one I should feature please submit the details through the contact form.
Matt Mullenweg wrote a long piece about Gutenberg, the forth coming editor change to WordPress, that is worth reading just to get the official take from Automatic on this subject that I consider to be controversial.
I’m not interested in doing a huge takedown on Matt’s article (someone is going to do that for me in the next link) but I will say this: Gutenberg just seems like big time trouble to me for WordPress plugin and theme developers. I agree that the current content editor and publishing setup in WordPress leaves a lot to be desired. Working with client projects built on WordPress for many years has driven that point home for me but I’m having a hard time getting behind this particular solution to the problem.
I hope Gutenberg will be worth it in the end but I have my doubts right now.
Gregory Schoppe has taken it upon himself to write the Gutenberg rebuttal to Matt Mullenweg that a lot of people probably wanted to do themselves.
Schoppe’s response to Matt’s Gutenberg post is basically spot on with my own personal feelings. Gregory’s post is long but I encourage everyone to read it if they haven’t drawn their own conclusions on the missteps Gutenberg could cause to the wider WordPress community.
What I liked most about Gregory’s piece is that he goes into problems with WordPress, beyond Gutenberg, that need to be addressed but continue to be ignored.
There’s a lot to think about with this issue and I’m glad this week gave us two sides of the argument to look at.
In positive WordPress news, the Core team has added support for a new “Requires PHP” header in the readme.txt files used in plugins. Developers can now explicitly show what version of PHP is needed to run their plugins. Hopefully this will cut down on support issues and also, in a round about way, encourage people running websites on old versions of PHP to get their hosts to upgrade.
There’s a chance that moving forward there will be a new featured implemented into the WordPress admin itself that will prevent people from installing plugins their server can’t support. If this comes to pass the “Requires PHP” will become an absolute necessity for all plugin developers.
I’ve got two Easy Digital Downloads related links this week.
First up, Igor Benić has released a book about building sites powered by Easy Digital Downloads for anyone out there looking for a good starting point.
Secondly, the fine folks at Easy Digital Downloads have released a free theme called Themedd. The goal with Themedd is to give you a quick start to selling digital goods with WordPress.
I write about EDD a lot just because I find it to be one of the most useful solutions for selling plugins and themes out there. If you haven’t seen my post about the best Easy Digital Downloads extensions for WordPress plugin sellers then you haven’t been visiting The Plugin Economy very long because I shamelessly promote it all the damn time.
Are You a WordPress Plugin Developer?
We would love to have a post on The Plugin Economy featuring your product.
Get started by submitting our interview request form.