WordPress 5.0 is almost here. Yay. But I am not that excited. As WordPress Developer working for more than 5 years, I am really worried at the moment. But as optimistic as I am, let’s hope this will be something better in coming years. Gutenberg sucks We must all open to changes. So I did […]
WordPress 5.0 is almost here. Yay. But I am not that excited. As WordPress Developer working for more than 5 years, I am really worried at the moment. But as optimistic as I am, let’s hope this will be something better in coming years.
We must all open to changes. So I did gave Gutenberg a chance, but hated it. Considering it’s relatively new, let’s hope it will grow and become versatile in coming days.
Testing Gutenberg as an editor for 5 minutes was enough for me. It was bit hard to use. It was way easy to break things, get confused.
At the point I am worried how easy it will be for my existing clients if they have to use Gutenberg to maintain their existing website.
Hate to say it, but my first impression of Gutenberg was it was targeted for bloggers predominantly. Are they trying to replicate Medium?
It does look so. And if you are a blogger, it’s a good news for you.
WordPress is (or used to be) quiet a solid platform or CMS to build versatile websites. This is in question with release of Gutenberg and WordPress trying to force it as default core editor.
There are still some workaround, like installing default editor plugin. But honestly should Gutenberg be mandatory? The kind of review it’s getting or as mediocre as it is shouldn’t it be just optional plugin.
One of the most powerful feature of WordPress is custom fields which had been quiet important to create complex CMS and plugins. The question of whether WordPress will keep on supporting custom fields is yet unknown, but at the point of writing WordPress will be supporting them. Though, it’s advised to convert them into Gutenberg compatible blocks as soon as possible.
Personally, I find the idea of blocks should be limited to creating simple structure and let custom fields to create more complex structures, but then again, it’s not unto us.
It’s too early to consider alternatives for WordPress 5.0.
Like so many other developers out there, I am open to try new CMS. But for time being I will keep my faith on the CMS.