The WordPress Gutenberg project’s plan for internationalization (i18n) and localization (l10n) of Full Site Editing themes (FSE) has not yet been formulated. I’ve written a proposal, entitled Internationalization and localization: translating templates and template parts, raised as Feature request #27402.
I believe that very little needs to be done to Internationalize a file containing Gutenberg blocks and HTML, and that it can be translated and localized into a statically delivered file in the user’s required locale ( language and country ) using the process described in the feature request.
This post briefly discusses some of the challenges of translating rich text content.
Last updated:December 6, 2020
The SB Children bock plugin, which delivers a WordPress block called Children is now available in the WordPress Block Directory.
Last updated:August 9, 2020
Having looked at a couple of solutions, I believe I’ll be able to achieve it having the table nested in a Group block, and providing the CSS styling using my CSS block.
Last updated:June 29, 2020
I’m away on vacation very soon. I’ve taken the opportunity to release another beta version of my oik-blocks plugin with a new block called Dynamic content block (
This block implements 11 of my dynamic content shortcodes delivered by the oik base plugin, hence the prefix. When it’s ready for production then I’ll deliver the block in oik v4.1.0.
Last updated:February 9, 2020
It’s been nearly 9 years since I first released my oik plugin to wordpress.org
Today, after many months of procrastination I finally released another update. oik v4.0.0 now embraces the block editor.
Well, it delivers a number of blocks; 6 in total, though wordpress.org only detected 5.
Last updated:January 31, 2020
Well that was a fuck up!
I’ve heard reports that the Classic Editor plugin was updated just a few hours before WordPress 5.0 was released and now there’s a completely different user experience.
The ability to easily choose the editor to create your content has disappeared. For me, that was the whole reason for having the plugin. Some things don’t work in Gutenberg / 5.0 so I need the ability to use both.
I don’t think the use cases for the Classic Editor and Gutenberg and WordPress version combinations have been thought through. I know that I am going to continue to want to use both Gutenberg and the Classic editor under WordPress 5.0. And I need the ability to easily select my preferred editor. That’s how it was with 0.5. It’s how I tested my sites’ compatibility.
You don’t bugger about with something hours before a release. You give people a chance to test it.
Lessons need to be learned. WordPress 5.0 release should have been delayed until:
Fortunately, I haven’t yet upgraded anything yet. I will be testing Classic Editor v1.1 very carefully.
Last updated:December 7, 2018
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.
Last updated:November 28, 2018