This is a slightly extended version of my Twitter thread. As the W3C has embarked on a full web property rebuild, its vendor (Studio24) indirectly announced earlier this month that it had dropped WordPress from consideration as a CMS. WPTavern took issue with this yesterday, and Studio24 responded today, (politely)…
I am going to propose a way to increase the overall accessibility of the WordPress ecosystem. It requires acknowledging some mistakes and using those as the base for building a better platform. I long for a world where a metric for featuring #WordPress themes and plugins in the repo is…
When Rian Rietveld resigned from the WordPress accessibility team on October 9, I decided to track the fallout in an ongoing Twitter thread. The subsequent weeks and days proved to be wonderful insight into how a project can suffer when accessibility is not built in from the start. When subject…
TL;DR: When WordPress 5.0 is released, let’s keep the current editor on your site instead of allowing the new editor, Gutenberg, to replace it. Level Setting Some of you are familiar with WordPress beyond a platform that powers your site — you follow along with its changes and its direction.…
A big reveal at WordCamp Europe was Gutenberg, an inline WYSIWYG editor for WordPress. While I had first seen it at WordCamp London, it was not a public project yet. As of WordCamp Europe, it is now in open beta with a plug-in available for testing. I am not involved…
A few months ago (that read “days ago” when I started this post in April) I attended WordCamp Buffalo and saw a great talk on training and educating clients for using WordPress by Jen Witkowski (you can view her slides). While there is a free, regularly-updated, and unofficial manual (Easy…