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.
At present 33% of my content could safely be edited using the Gutenberg block editor. Migrating safely to Gutenberg is going to take a long time.
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.
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.
Tools like Slack, Facebook, Twitter and WordPress itself are capable of embedding content from another site just by being given a link. I’ve just updated oik so that it will expand shortcodes during ‘the_excerpt_embed’ filtering.
Which means you shoudn’t see a load of strange
Today I updated the version of PHP I use in my development environment, from PHP 7.0.7 to PHP 7.1.1.
WordPress version 0.70 was released on 27th May 2003. Today, 2nd Feb 2017, it has reached 5,000 days of age.
Since WordPress 3.0, released in June 2010, the themes bundled with WordPress core have been named twentysomething, starting from twentyten. The latest is twentyseventeen.