anchor.diff:  TODO: ssl
   ////
   
  +[[gmail]]
   ==== Send email through GMail
   
   
  
positive.code: 
  
  
  
  ////
  TODO: default subject as property
  ////
  
  
  [[email-usage]]
  
negative.code: TODO: image inlining
  TODO: css inlining
  TODO: rewrite html
  TODO: you have control: attributes to enable/disable rules
  
  
  
  TODO: explanation from old README
  #### Working with HTML content
  
  To be sure that most of Email clients will handle an HTML content, there are many rules to follow when writing the content. They might be very complex and time consuming. The library do all this headache work for you.
  
  All these features can be either disabled or use another implementation instead of the default one.
  
  ##### Inline CSS and images
  
  For Web developers, it is important to write clean code and separate the concerns. So when writing HTML, developers want to externalize CSS files and images. This is also really important to mutualize the code of CSS files and images for reuse.
  
  However, email clients doesn't handle external CSS files. Styles can be included in a `style` tag but Gmail doesn't support it. So all rules provided in the CSS *MUST* be inlined directly in the HTML. Writing code like this is just awful and error prone. Moreover, images can be references externally but there are many constraints to use it this way. You have to know in advance what is the URL of the final image. And even then, the email client might block those images for safety purpose. Not mentioning offline issues.
  
  The library will automatically inlines CSS rules directly on the HTML tags. The images are either inlined as base64 encoded in `img` `src` attribute or images are attached with the email (with inline content disposition and references in the HTML).
  
  ##### Use expanded CSS properties
  
  CSS properties can be written using shorthand version:
  ```css
  padding: 4px 2px;
  ```
  This is equivalent to:
  ```css
  padding: 4px 2px 4px 2px;
  ```
  
  Some email clients do not understand shorthand properties. So all properties written in shorthand version must be expanded in order to work everywhere.
  
  The library will automatically expand properties from shorthand versions.
  
  ##### Add extra attributes for old email clients
  
  Several attributes must be added on some HTML tags in order to be compliant with email clients. For example, tables and images must have attribute `border="0"`in order to prevent an ugly border on some clients.
  
  The library will automatically add these attributes.
  
  ##### Use XHTML
  
  It is recommended to write XHTML instead of HTML due to some mail clients. The library do it for you.
  
  ##### Background images
  
  Background images are not correctly handled by several mail clients. And again, some workarounds to apply to fix this issue.
  
  The library will apply those workarounds to your HTML.
  
  ##### Use tables for layouts
  
  ////
  
  
  