
Why Community Translation Can't Scale for WordPress Themes and Plugins
Our analysis of 60,000+ WordPress plugins and themes shows community translation covers under 5% of needs in 40 languages.
WordPress 5.0 (a.k.a. the Gutenberg version) is approaching. We highly recommend postponing this update in your production sites until January.
Once you switch to WordPress 5.0, the editor that you’re using now will be retired and completely replaced by the new Gutenberg editor.

Here is how the new editor looks like and how to translate content with it:
However, for the next few weeks, and especially when dealing with existing sites, the drawbacks are bigger than the benefits.
Gutenberg is certainly a cool new editor, but it’s a completely new thing to WordPress. This means that a lot can break at the beginning.
Unfortunately, Gutenberg is still not stable enough for full integration. Since it’s changing between each release (including the release candidates), there’s a chance that new compatibility issues will arise with the upcoming WordPress 5.0 release and with every subsequent 5.x update.
Of course, we will do our very best to keep up with these changes. When we can fix things ourselves, we do that immediately. Sometimes, we need tiny changes from Gutenberg side. Mainly, we may need new filters and hooks. Right now, we are facing several issues that will not work until addressed in WordPress:
WPML enjoys a large development team, so we can keep up with these rapid changes. Not all plugins and themes have this capacity, so it may take a little longer to adjust to Gutenberg.
We’ll be updating our production sites to WordPress 5.0 on January, assuming that from today and until January we’ll see only one release of WordPress and it will go out smoothly. This is the first time since our launch that we’re holding off updating our production sites to new WordPress versions.