Back in April I was developing a prototype plugin called oik-block that contained a number of prototype Gutenberg blocks plus a whole load of code that helped me to form opinions regarding Gutenberg’s compatibility with my sites and to estimate the code of migrating to Gutenberg and/or WordPress 5.0. I’ve recently forked oik-block to create a new plugin called oik-blocks. Here’s an update.
At the Portsmouth WordPress Meetup on 18th October 2018, I gave my presentation entitled “Switching from Canvas to Storefront”, subtitled “How to update a WooCommerce site with a new theme … the trials and tribulations”.
The talk was based on my experience of migrating Steve Goodyear’s Motorcycle Products online shop sgmotorsport.biz.
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.
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.
A few months ago, having resolved to internationalize, localize and test my WordPress plugins, I started busily beavering away at a solution that will enable me to automatically deliver UK English versions of my plugins.
Now that Global WordPress Translation Day #3 is fast approaching it seems timely to write up an outline of my approach. The solution involves a number of fairly well defined processes, and a lot of repetition. [Read more…]
WordCamp London 2017 is over and I am back home thinking about the past weekend and the future. Here’s an update to my bucket list. [Read more…]