What constitutes an email being "broken" for users?
An email is "broken" when content can't be accessed and when an image is shifted in a way that makes it feel like the quality has been reduced.
Is having a 1440px wide design inherently "broken" for users?
No, but it's not something I would risk for sales-oriented emails. People may not go the extra mile to open in full view.
Is an email like this worth the experiment?
YES! This email and the report itself is a celebration, both of Litmus and of email as a whole. While the ultimate goal is to get people to click through to the report, I think it was paramount to show how far email clients have come in 2016. Hopefully, the Outlook team will see this email and this thread to understand that it is the primary detractor to email at this stage. I'm optimistic that the open communication amongst the team there and the community will lead to great things.
Congratulations on a killer year, having an awesome team, and on creating another email that sets the bar for what I'd like to achieve with my work.
I'm the exact same, the only reason I have ever done it was to try to find missing closing tags and there's no need for that anymore with all that pink up in Builder.
No, but I use Haml so I have similar problems occasionally but I luckily there's a site that does HTML to Haml which helps speed things up a bit. I haven't seen one for Jade yet, though.
The biggest drawback to it for me is that I can't really share my stuff easily. Since I've become more active in the community I've been debating on cutting it out of my workflow so that I can share more. That's an unusual problem, though. You just have to work in what works best for you (and your team).
Thank you for following up, it's cool to hear. Based on what you're doing, you may want to stick with that flow (sans inlining). Either way you're learning a syntax (handlebars or the middleman helpers) and the only gain from Middleman would be creating your own custom reports.
Add me to the "no inlining" list and for the same reasons mentioned. I thought I'd jump in for this part: "If you don't use an inliner, how do you manage to keep the CSS reusable and consistent?".
I use a styleguide but rely heavily on snippets. If I need to reuse something I've created before, it goes in the styleguide and I make a snippet for it if I keep using it. Aside from that, I have a partial of Sass that is included in every email, though it's not very big. (Text sizes and helper classes to change padding mostly).