Yes, due to some gmail client combinations still not supporting CSS in the head.
Personally, during development I use a gulp task, which will:
Run 'gulp-less', which will compile Less into a CSS file
Run the 'gulp-file-include' task, which allows for partial html files to be included during development, and compiles them all into 1 file.
Run 'gulp-inline-source' which builds an HTML file by inlining any specified linked css files into a single file, that i then copy and paste into the ESP's head area (usually contains media queries and specific client fixes)
Run 'gulp-inline-css' which will inline the CSS from the file in #1
Run 'run-sequence' This just makes sure that things happen in a specific order (so the css file to be inlined runs before the inlining process)
The above all runs on every save locally, so I wouldn't save any time by not inlining
if the template is done correctly in the first place its easy to change things. U could also creat code "Snippets" in litmus and build the html structure faster.
It's really not that much more work on my end to inline the code. There are lots of tools out there and I have code snippets I reuse all the time that allow creation of new code easy as copy and paste.
Also, we use an ESP that allows us to tokens for any values so I can essentially do what happens in the head by updating a single line per value in my email template.
Once the last email client that needs inline styling drops below .1% global usage, then I will change the way we do code our emails but until then, I don't want to risk a sale because of the tiny extra work at the onset of the project.
DD
Yes, due to some gmail client combinations still not supporting CSS in the head.
Personally, during development I use a gulp task, which will:
The above all runs on every save locally, so I wouldn't save any time by not inlining
I still inline yes, because there are still some mail clients/Gmail app combinations that strip the head.
Yes, cuz some design have to be done this way. You can see the support for css in email clints here:
https://www.campaignmonitor.com/css/
if the template is done correctly in the first place its easy to change things. U could also creat code "Snippets" in litmus and build the html structure faster.
It's really not that much more work on my end to inline the code. There are lots of tools out there and I have code snippets I reuse all the time that allow creation of new code easy as copy and paste.
Also, we use an ESP that allows us to tokens for any values so I can essentially do what happens in the head by updating a single line per value in my email template.
Once the last email client that needs inline styling drops below .1% global usage, then I will change the way we do code our emails but until then, I don't want to risk a sale because of the tiny extra work at the onset of the project.
Yes, because some mail clients/Gmail app does not support styling in head