> clearly, it's not working if a website like this is even required. you say it is HTML compatible, then continue to tell me things in HTML are not valid for use. you say it can use CSS, then continue to tell me all of the valid CSS that cannot be used. so I'd suggest s/working/working*/ and then define the caveat as required.
That is not the point though.
The point is that the vast majority of people prefer transactional / marketing emails in rich formatting. They understand them better, they prefer interacting with them, it results in a better overall user experience.
Who creates all those transactional / marketing emails in HTML? Developers. Plenty of them.
All of them are in a difficult situation because writing HTML for sucks. It REALLY sucks. Tools like this one help them (the developers!).
Not using HTML emails is not an option in this field. It will never be as long as the average user (AKA the average customer) responds well to rich formatted emails.
That is not the point though.
The point is that the vast majority of people prefer transactional / marketing emails in rich formatting. They understand them better, they prefer interacting with them, it results in a better overall user experience.
Who creates all those transactional / marketing emails in HTML? Developers. Plenty of them.
All of them are in a difficult situation because writing HTML for sucks. It REALLY sucks. Tools like this one help them (the developers!).
Not using HTML emails is not an option in this field. It will never be as long as the average user (AKA the average customer) responds well to rich formatted emails.