Emails and E-Newsletters
SPECS provides solicitation and stewardship emails and e-Newsletters as service to the development community. Emails and email newsletters are currently available at no cost to members of the development community. Please use the links below to review our existing templates which can be tailored to your department:
Emails and E-Newsletters
Emails
Examples are available below, please click to enlarge.
Please click the link below for our Email Request Form
e-Newsletters
Examples are available below, please click to enlarge.
More examples available on DevNet
Please click the link below for our Email Newsletter Request Form
Best Practices for Webmasters
SPECS Template Specifications:
Banner: 680 pixel width; 125 pixel height
Standard e-mail image: 150 pixel width; 225 pixel height
Newsletter thumbnails: 100 pixel width; 100 pixel height
Our existing templates have been designed and rigorously tested across dozens of combinations of operating systems and browsers. For new SPECS projects, we typically require the use of our templates since testing has already been completed. If your department has in-house web developers, or you're working with a design consultant such as Michigan Creative, several hours of testing will still be required in order for us to deploy your email.
Since web-safe guidelines are constantly changing, even a well-seasoned coder can create something that doesn't render properly across all email clients and browsers. If you are working on a new template with an external consultant, you must let us know in advance so we can make time for additional testing. Our standard turn-around time is 10 business days for a template that is already validated; if you're considering an alternative template please be prepared to provide the HTML a month in advance of your desired drop date. This doesn't mean necessarily mean your content needs to be ready, but we will spend 5-10 hours validating the code and don't want that to collide with your publication schedule.
Additional HTML guidelines and eCommunications best practices can be found below.
https://docs.google.com/document/d/1_HFJEVS0SAkLjBdCdEo2LFJ5cgC_vQlm5RqACR2F_pI/edit
