October 2021 | BEE HTML for Email 3.0
We're excited to announce the release of BEE HTML for Email 3.0!
This latest build offers several improvements over the previous version, including:
- Faster design rendering
- Reduced output file size
- Simpler, cleaner HTML output
- Wider email client compatibility, including reduced Gmail clipping
This document is a brief description of the new release. For a more in-depth description of the technical changes, please see this article.
About BEE HTML for Email
HTML File Compression
Our average exported HTML data footprint size has decreased roughly ~56% over previous builds. We've based these findings on extensive testing of over 600 designs.
Summary of Key Changes:
- Faster loading and rendering
- Reduced mobile clipping
- Reduced bandwidth consumption
Improved HTML Rendering
Migration from <div> to <table> formatted codebase
Most Content Blocks have been re-coded for conciseness
Final HTML code is now compressed to remove whitespace between tags
- Transparent dividers are now automatically converted into padding
Improved response time, almost 8x faster HTML rendering from JSON
Optimized to support heavier workloads, minimizing potential errors during peak load times
Activating BEE HTML for Email 3.0
If you are currently using the Plugin, you can enable the new version in your account at developers.beefree.io. We strongly recommend doing this in a development instance before using it in production. This is particularly important if your application applies any postprocessing to the HTML, as the general structure and tag syntax have changed.
The new version is enabled in new instances of the Plugin by default. You can disable it at any time to revert to the previous version.
The activation widget is available in application details:
You will be asked to confirm the version change. Again, be sure you have tested thoroughly before applying to your production environment!
Enable BEE HTML 3.0 in your development instance.
Test your message creation workflow. Identify any potential issues that occur due to the markup change. For example, a post-process may append an attribute to a markup element that no longer exists.
Report any issues that you cannot resolve to BEE Plugin support so we may troubleshoot them.
Enable BEE HTML 3.0 in your production instance.
Run through your workflow once more in production.
If you're interested in learning about previous versions of BEE HTML for Email click here.