I’m pretty new to html emails and I’m picking things up, but I appear to be using quite a (IMO) convoluted method of creating them. I will list below the route that I take, which does produce a finished email, but I would like to know if this method can be refined to make it any less arduous OR whether any of you far-more-experienced readers can create a set of guidelines/tutorial that would be of help to a lot of us.
doc setup: IE compatibility: normal. html 4.1 transitional
create using tables, no divs, no layers, no background images, 580px wide. When finished, apply ‘email ready html action’
upload to web server
check in browser for problems(I also use emailonacid.com testing)
It now starts getting arduous:
open the html file in Textwrangler and replace the pound signs/bullet points etc with html equivalents. Also replace the ‘locations’ of linked files with absolute references (i.e. the full web address of the files ON the web server)
copy the new html file onto the web server using an FTP client
import web-based html file into distribution software (I use Direct Mail) then send email to client for approval.
If the client makes changes, I then need to go back through steps 1 to 6 again. And again. And again.
Is this really the way everybody does it? I haven’t even touched on what I have to do with mailing lists/subscription lists/unsubscribe links etc.
Well you can eliminate step 4 (or make it less arduous) by changing your character encoding to Windows Latin 1 or similar using the Output tab of the Page Inspector. That should make all of the high-bit ASCII characters become their entity equivalents.
As to the rest, it’s pretty much the price you pay (that plus your immortal soul) for sending HTML in e-mail, which is, by definition, text.
Austin Wells Design Limited
One Elmgate Drive - Littledown - Bournemouth BH7 7EF
t 01202 301271 e email@hidden w http://www.austinwellsdesign.co.uk
Member of NAPP | Zen Affiliate | Dorset Business Member | YEC
Facebook | Twitter | LinkedIn
On 22 Jun 2010, at 13:30, waltd wrote:
Well you can eliminate step 4 (or make it less arduous) by changing your character encoding to Windows Latin 1 or similar using the Output tab of the Page Inspector. That should make all of the high-bit ASCII characters become their entity equivalents.
As to the rest, it’s pretty much the price you pay (that plus your immortal soul) for sending HTML in e-mail, which is, by definition, text.
Try that, I’m not guaranteeing that all of these characters will be
magically encoded, but most of them should be. You can test other
encoding options, and see which one works best for your content.
Well you can eliminate step 4 (or make it less arduous) by changing your character encoding to Windows Latin 1 or similar using the Output tab of the Page Inspector. That should make all of the high-bit ASCII characters become their entity equivalents.
Nope, that doesn’t make any difference when using the ‘email ready html’ action. Max has already told me that I need to edit the html text afterwards. The same thing applies to the absolute references. I tried using the ‘remote resources’ action but that doesn’t play nicely with the ‘email ready html’ action either!
For reliable quickly editable html email use the box model to build
your email templates. Dan Jasker has a great tutorial on the method
On Jun 22, 2010, at 5:12 AM, neil.west1 wrote:
I’m pretty new to html emails and I’m picking things up, but I
appear to be using quite a (IMO) convoluted method of creating
them. I will list below the route that I take, which does produce a
finished email, but I would like to know if this method can be
refined to make it any less arduous OR whether any of you far-more-
experienced readers can create a set of guidelines/tutorial that
would be of help to a lot of us.
doc setup: IE compatibility: normal. html 4.1 transitional
create using tables, no divs, no layers, no background images,
580px wide. When finished, apply ‘email ready html action’
upload to web server
check in browser for problems(I also use emailonacid.com testing)
It now starts getting arduous:
open the html file in Textwrangler and replace the pound signs/
bullet points etc with html equivalents. Also replace the
‘locations’ of linked files with absolute references (i.e. the full
web address of the files ON the web server)
copy the new html file onto the web server using an FTP client
import web-based html file into distribution software (I use
Direct Mail) then send email to client for approval.
If the client makes changes, I then need to go back through
steps 1 to 6 again. And again. And again.
Is this really the way everybody does it? I haven’t even touched on
what I have to do with mailing lists/subscription lists/unsubscribe
links etc.
For reliable quickly editable html email use the box model to build
your email templates. Dan Jasker has a great tutorial on the method
Thanks for that Ginjg, but I don’t have a problem creating the email itself, it’s the processes I need to go through AFTER creating it. Besides, I thought the box model was CSS and I’ve read that you need to create them using tables - or am I getting mixed up?!
Perhaps it’s considered “inline css”. For me, I found it works
better than tables in the two mailing programs I use (Acymailing and
ListMessenger for Joomla) for consistency across all browsers and
mail clients. I couldn’t get tables to behave the way I wanted. It
also was effective when I used to import custom layouts into Constant
Contact.
I design to the least standards compliant email client, which,
according to email-standards.org, is gmail.
After the email is in the mail program, I send it to check-
email@hidden for spam check. You can get more info
about that at port24http://www.port25.com/corporate/
corp_news_authenticator.html
I didn’t know there was an ‘email ready html action’ I’ll have to
give that a try.
On Jun 23, 2010, at 12:56 AM, neil.west1 wrote:
For reliable quickly editable html email use the box model to build
your email templates. Dan Jasker has a great tutorial on the method
Thanks for that Ginjg, but I don’t have a problem creating the
email itself, it’s the processes I need to go through AFTER
creating it. Besides, I thought the box model was CSS and I’ve read
that you need to create them using tables - or am I getting mixed up?!