Our future form editor is going to be in Gutenberg, also known as the Block Editor.
In fact, we’ve already started working with it (screenshot below) and we hope to release a first version by the end of 2019.
In the near future, our email designer will also go down that route. More on that below.
A Year of Observing Gutenberg
When Gutenberg was launched a year ago in late 2018 as the default post editor in WordPress, we took time to study its lines of code and features.
We immediately asked ourselves:
- Could it become the default editor for emails and forms in MailPoet?
- Is the code ready to be extended to a third party plugin like ours?
Gutenberg looked promising enough, but we wanted to evaluate the community’s reception. It was — and still is — quite divisive amongst users because of the user experience. A typical review of Gutenberg:
Forcing a change to users’ habit will always create an initial backlash. We witness this reaction when newspapers update their homepage designs or when Facebook overhauled its newsfeed, as examples.
Even at MailPoet, feelings about Gutenberg are mixed. Why? We used it to redesign this website and it proved to be a headache. Perhaps we were a little optimistic since it’s not yet meant to be a page builder, like Beaver Builder or Elementor. Gutenberg feels like a page builder that hasn’t fully grown out of its teenage years.
I’ve been writing in Gutenberg for well over a year myself now, and while it’s a bit buggy at times, my user flow is… flowing! I can publish easily and it behaves as I expect, or almost. To enjoy it, it’s was important to take the time to learn some of its tricks.
In the past 12 months, millions of people have installed a plugin that restores the Classic Editor to essentially disable Gutenberg. Yikes! Which a year ago begged the question: what if Gutenberg is deemed to fail in the long run?
Fast forward a year later (fall 2019) and the Classic Editor still gets 50,000 new installs per week. The co-founder of WordPress estimates that about a quarter of people are still using the Classic Editor in his annual State of the Word (youtube).
But Gutenberg is holding its ground and growing into its role as the default WordPress editor.
Why Gutenberg is a great choice
There are many reasons why we are standing by Gutenberg and are choosing to fully adopt it.
The user experience is improving thanks to solid backing
In the past year, the Block Editor has improved by leaps and bounds. It’s easier to use, faster to load, and less buggy, not to mention constant new features.
It’s not a surprising feat considering there are often nearly 40 people contributing at any one time to Gutenberg. Many of them are Automattic employees. Read: serious backing. Many volunteer contributors have been hired by Automattic, according to Riad Benguella.
It’s source code is well designed
There are 8 engineers working at MailPoet and not a single one worked with WordPress prior to joining MailPoet.
None of them have anything nice to say about WordPress code. Rest assured, this is a common thread amongst developers.
With Gutenberg, cast this criticism aside!
Our team thinks it’s a well designed and modern application. While it’s a big project with a lot of lines of code, a developer can navigate the source and understand how it’s structured and find his or her way around without having to read documentation. That’s how modern application are supposed to be.
It’s going to redefine the WordPress user experience
Gutenberg will eventually allow you to edit your entire website, and not just a page or a post. This is what Wix and Squarespace have done so well and so have plugins, themes like Divi and Elementor.
You will soon be able to edit your website without having to learn CSS or ask for a friend’s help. In fact, this could be the end of themes as we’ve known them.
Extend this to MailPoet, and you could see how Gutenberg could be the next email designer.
Working on the Block Editor will allow us to contribute
MailPoet is a fairly large endeavor, one that has left little time for our team members to participate in other open source projects, starting with WordPress itself.
This has left us feeling on the fringe at times. It would have been quite satisfying to actually assign one of our team members to work on the core of WordPress.
Adopting Gutenberg will throw our team members into the fray and allow us to not only improve MailPoet, but also make WordPress better.
Our email editor can be made in Gutenberg
Late in 2018, Gutenberg’s code was still entangled into the WordPress post and page editor. For us to use it outside this context required hacking the Block Editor.
Earlier this year, one of the lead developers of Gutenberg shared it as a standalone app on GitHub.
This was the cue we were waiting for to debate further about the viability of switching our email and form editors to Gutenberg.
In September, one of our colleagues did a demo of Gutenberg. It took us 3 minutes to become convinced that Gutenberg was the way forward. The debate didn’t last long! The writing is on the wall.
Switching our email designer to Gutenberg is a fairly large project, especially since we want to ensure a smooth transition from the old to the new editor. We’ll first begin with the signup form editor to get ourselves warmed up.
First, we’ll change our current form editor
In MailPoet, we have a simple form editor that allows you to create fairly simple signup forms:
This editor has been a part of MailPoet since 2014 and has not evolved ever since. Its foundation was not solid enough to build on top of it, so it became stale (we were also working on other things because there are plenty of form plugins already).
Gutenberg is the future of WordPress. It’s normal to see initial pushback by users after nearly a decade of using tinyMCE, the default text editor since WordPress 2.5 (2008).
We want to be a part of that future by using the Block Editor in our own plugin because it’s well designed and it’s actively being improved at a fast pace.
MailPoet doesn’t want to reinvent the wheel. In fact, we’d like to participate in the core of WordPress by working on Block Editor ourselves.
The first step for us is to use Gutenberg as our default signup form editor later in 2019. Then, we will begin working on the email designer.
Sad. Time to migrate to another plugin. It was a good journey, thank you.
Or, maybe, you have plans to support classicpress.net?
Tad, what’s the thing you dislike the most about Gutenberg? A block for each paragraph?
Mostly, yes. It is impossible to write fast in the Gutenberg page builder. I prefer to write in a text editor, not page builder.
In general, I prefer a clean interface, focused on efficiency, not special effects. Dancing tooltips are a nightmare. I migrated my site to the ClassicPress for this reason.
I understand, I agree. This is my workflow when I need to type an article:
1. Write in Google Drive where our editor can comment and review
2. Paste to Gutenberg
3. Don’t use your mouse on Gutenberg to avoid getting distracted
As for ClassicPress, it’s going to be an uphill battle especially with the Classic Editor plugin still alive and kicking.
What about this workflow:
1. Write in the ClassicPress.
That’s all. You can use your mouse, have a powerful TinyMCE editor, edit formatting code, etc., etc. And it is a permanent solution to forced Gutenberg page builder, not a temporary, like a Classic Editor plugin.
All the way with you on this Tad!
While I am not able to appreciate Gutemberg for writing posts, i can see its potential to edit Pages. For this very reason maybe it s also a good match with MailPoet… let’s see.
I am not sure about about this narrative people at Automatic are trying to build: “Forcing a change to users’ habit will always create an initial backlash. We witness this reaction when newspapers update their homepage designs or when Facebook overhauled its newsfeed, as examples.”
there was an initial backlash for that reason maybe… but now one year is passed and the jury is clear. “Guty” sucked and was useless when it came out.
Manolo, do you think it’s a big enough backlash to pull people away from WordPress altogether, and switch to alternatives?
No, not enough (and some people appreciate) for now.
+ not enough alternative.
Just coz drinking soda only for a week is not gonna kill you, it does not means it s a wise idea to keep of having unhealty choice.
but, boy, I am less than excited to be “part of WP” and I am not so confortable to suggest WP to all my clients now
I’ve switched TWO site (out of tens – so very little) on classicpress, and when i find an easy Ghost hosting, I will switch a couple more.
and every month I invest energy to find an alternative.
the problem is not Gutemberg in itself, but the “Herd mentality”, totally in denial of the actual situation you read in the answer.
a lot of nice people willing to lie just to defend some other people decision.
That is my level of trust of WP now :-(
And I also remember clearly when WP came out… the PhpNuke guys were laughing and . Phpnukewhat some may ask… exactly.
Thanks for your insights Manolo.
There are many more reasons to move away from WordPress, other than Gutenberg. I often recommend Wix myself actually.
For example, security, updates that break your site, PHP version quagmire, website design that only WordPress developers can achieve…
The WordPress project is tackling many of those issues head on, thankfully.
As for design, we’re still in the early phases of Gutenberg. In 2 years, perhaps we won’t need page builders any longer or fiddle with CSS. To achieve that, we do need all parties to commit to it sooner or later.
> As for design, we’re still in the early phases of
> Gutenberg. In 2 years, perhaps we won’t need
> page builders any longer or fiddle with CSS. To
> achieve that, we do need all parties to commit to it
> sooner or later.
I agree and i think this is the most sensible reply people can get when there is a critic on Gutemberg.
“It’s not ok. but our plan is to have a better future so please bear the work in progress.” is something that not only i agree with, but i am ready to commit and help
“you understand nothing: gutemberg is good, better and you should only shut up (exactly the Wp.org mod behaviour)” is something people does not like.
merhaba etkin yazı teması değişikliği olabilirmi?
temada değişiklik yapılabiliyormu
Translation: “hello can there be active post theme changes?”
We are thinking about offering predefined templates for posts, yes. Gutenberg does offer the possibility to save blocks, so that can come in handy.
Great to hear that the form builder and email designer will be modernized.
During testing of many newsletter solutions your email designer (inside WP) felt a lot like a very very basic Gutenberg-Editor already. Making me wish for a bit more functionality but not the crazy interface and feature overkill some other tools provide.
So I’m looking forward to the “reworked and extended” email designer.
Thanks Ralf. Let’s see where the form editor takes us first. :)
Is MailPoet accessible for people with all kinds of disabilities? Is it WCAG 2.1 compliant? Can a person with any kind of disability create newsletters for other disabled persons?
Jazwiecka, unfortunately no, MailPoet is not fully compliant. We are aware that screen readers have a hard time with our email designer.
Sorry ! Comments are closed.