43 years ago, at the tender age of 16 years and 11 months, I entered the IT industry. My salary was £1690 per annum; £65 a fortnight.
In the last month my development focus has been on General Data Protection Regulation ( GDPR ) and the changes required to my oik-bwtrace plugin that will enable me to continue to use it on publicly accessible live sites.
Version 2.7.0 of Gutenberg was released recently. It’s still auto saving drafts with a vengeance. 7 revisions so far on this short post. 9 now. 10. Oh my!
So I tried the Editable permalink. I found at least three problems. I bet no one’s bothered to raise them.
Oh fuck me! It’s a usability nightmare.
Most years, before visiting WordCamp London, I write a long bucket list of things I hope to achieve. This year it’s no different, although the main focus is on developing blocks for the new block editor, Gutenberg.
Most years, before visiting WordCamp London I write a long bucket list of things I hope to achieve. This year it’s no different.
In my first post about the new block editor for WordPress, code named Gutenberg, I commented on the apparent absence of an implementation plan. I was also acutely aware that I didn’t have a plan either. So, since then I’ve been attempting to:
- Evaluate Gutenberg’s compatibility with my sites.
- Estimate effort to develop solutions for my plugin customers.
- Estimate effort to ensure peaceful coexistence.
- Estimate effort to migrate each site to WordPress 5.0.
Should Gutenberg be allowed into WordPress core?
At the WordPress Portsmouth Meetup, 22nd February 2018, I gave a short talk and demonstration of the Gutenberg plugin which is being proposed as the new block editor for WordPress. In the deck are three slides entitled Road map, Current landscape and Projection. In this post I want to air my concerns about the part of the project that nobody appears to be thinking about… implementation.