Cyber Monday is rapidly approaching. Are you prepared? (We hope so!) Check out these last minute tips for sending an email newsletter on the biggest eCommerce day of the year.
Some time has passed since our last post about MailPoet 3. We hit a few bumps down the road and reorganized the team a little bit. I’m Marco, currently leading the dev team here at MailPoet, and I’d like to shed some lights on the building process, what we’re working on, what we’re aiming for.
The first beta of MailPoet 3 is coming soon.
It took some more time than expected, as usual. We, as an industry, still haven’t figured out a way to estimate development tasks, but that’s another story.
While the current version of MailPoet works good, MailPoet 3 for us is the future, the new foundation. It has to be:
Although MailPoet is not one of the heaviest plugins around, it’s surely feature-packed. We’re trying to blend all current and new features together while staying as lightweight as possible. We know very well many WordPress websites run on low-memory servers. It’s one of the reasons why we’ll require PHP 5.3.
We’re working hard on improving the stability of the plugin during the delicate phases of install, upgrade, and downgrade. We’re aiming for a project that is always in a recoverable state. A trash feature and a solid database layer will make this happen.
The single blocking sending queue is being replaced with a new multi-threaded queue that is able to send multiple newsletters at the same time, enabling performances that can scale with the power of the server. In order to overcome the limitations of the WordPress routing layer the new plugin will be mainly a single page application, powered by React and Webpack.
It’s not a secret, we have more and more services running around the plugin. As many of you know, we run a distributed Ruby/Haskell-powered cron system that keeps MailPoet installs alive without the need to rely on the WordPress cron. We also have our own sending service in beta. Yes, the new MailPoet will be able to send newsletters without a local SMTP or third-party service. We’ll hit 3 millions messages delivered since we started the beta a while back, serving 200 beta testers.
Our main concern, and the first reason why we are building a new MailPoet, is the technical debt we acquired over the last years. We became too slow in adding features and fixing bugs. We need a new code base that enables a fast release cycle. The new MailPoet can be continuously tested. It has PHP and JS unit tests and a full acceptance tests suite that takes UX bugs under control.
As you can see, it’s not one of the easiest projects to build. But we accepted the challenge a while back. It’s now time to take MailPoet to the next level.
I’ll leave you with a nice screenshot of our sending service metrics system and a promise: from now on we’ll be more open about our development process.
If you have a shop or you’re attending a trade show, then you’ll probably want to consider how you can subscribe people to your newsletter “offline”, without sending them to your website (you’ll still need an internet connection). Traditionally you’d use a notepad and pen, but this is incredibly time-consuming, as someone will have to manually type in the details (plus, bad handwriting and input errors can cause additional problems.)
In this tutorial, I’ll show you a much more effective way of getting people to sign up, using the MailPoet iFrame form.
Photo by Jan Tik
It’s a popular time of the year for themed holidays so it’s a good idea to prepare early for them. Here’s some top tips to get yourself seasonally ready, whatever time of year it is.
In this Email Clinic, we’ll give a fresh but impactful update to a Danish Football Club’s newsletter.
No one likes to say goodbye, but it doesn’t mean that you can’t learn something from the experience.
Setting up a drip campaign is easy with MailPoet! In this post, we’ll show you how to set up a series of automated emails to create your own drip campaign.
Sometimes, you might only want a subscriber to choose one from a selection of lists to subscribe to. By default, when you give the user a choice of lists, our forms only give you the ability to have checkboxes, meaning that the subscriber can opt-in to multiple lists.
In this tutorial, we’ll show you how to edit the signup form and replace the list selection checkboxes (with either radio buttons or a dropdown list).
In the final part of this series, we’ll look at the “welcome email,” or a message that comes at the end of the signup confirmation process.
In Part 1 we showed you how to customize the signup email, and now we’ll show you how to make that signup experience even better when the subscriber clicks through to confirm their subscription.