![]() ![]() ![]() We can now review our workflow scheme in a more detailed way: You’ll have to edit the CSS to be inlined directly into your HTML file, then launch an inliner tool (the Mailchimp inliner, for example), and finally you have to embed the second CSS into the inlined file (It bores me just writing about it!). Going back to CSS, you’ll probably have to deal with two files: one to be inlined and one to be embedded (for the clients that support media queries). In the past, I used a little PHP script to send the test emails, which could save some time, but it still requires repeating certain tasks. If you have a testing platform account ( Litmus, Email On Acid, Campaign Monitor or some other), you can simplify the final testing task by submitting your inlined code to the test platform but in order to perform a more accurate test, you’ll still have to send them your code by mail. But every test requires many actions to compose the mail, inline the CSS, paste the code, etc. ![]() Sending your code by email is a little tricky, since most clients don’t allow you to compose an email by pasting HTML code in its body (the only one I know is Thunderbird). Also, the final testing requires you to send your inlined HTML to various accounts to check your design against various email clients. Moreover, the “CSS inlining” and “Testing” tasks require a little extra work and attention: first, you’ll have to take care of preserving your original working copy from the inlined one. The final testing (with inlined CSS) is the step that requires more time since we’ll probably have to repeat it many times. Authoring (with preliminary local testing).A classic email development workflow has three primary steps (see my Crash course article for more details): ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |