Add troubleshooting section to the docs to talk about DOCTYPE + ESP interaction

diff --git a/docs/components/getting-started.php b/docs/components/getting-started.php
index 69da60ef560bef199350729602685a87f587784a..8201b76023a41134d3850e0adc7175e25299e02f 100644 (file)
--- a/docs/components/getting-started.php
+++ b/docs/components/getting-started.php
@@ -70,4 +70,9 @@
 <hr>
 <h2 class="light">Sending Your Email</h2>
 <p>Sending HTML email is a lot different than sending plain text email. While it may be tempting to just open the email in a browser and click &#8220;share&#8221; or to use the &#8220;Insert HTML&#8221; function of your favorite email client, this often strips off a lot of the styling and makes your email completely unusable on mobile devices.</p>
-<p>To get the best results, we recommend that you send your HTML email using an <a href="http://en.wikipedia.org/wiki/Email_service_provider_(marketing)">Email Service Provider (ESP)</a> such as <a href="http://mailchimp.com">Mailchimp</a> or <a href="http://campaignmonitor.com">Campaign Monitor</a>. If you&#8217;re just running a quick test and don't want to sign up for an ESP, sending from the command line using a scripting language like <a href="http://php.net/manual/en/function.mail.php">PHP</a> or <a href="http://ruby-doc.org/stdlib-2.0/libdoc/net/smtp/rdoc/Net/SMTP.html">Ruby</a> usually works fine.</p>
\ No newline at end of file
+<p>To get the best results, we recommend that you send your HTML email using an <a href="http://en.wikipedia.org/wiki/Email_service_provider_(marketing)">Email Service Provider (ESP)</a> such as <a href="http://mailchimp.com">Mailchimp</a> or <a href="http://campaignmonitor.com">Campaign Monitor</a>. If you&#8217;re just running a quick test and don't want to sign up for an ESP, sending from the command line using a scripting language like <a href="http://php.net/manual/en/function.mail.php">PHP</a> or <a href="http://ruby-doc.org/stdlib-2.0/libdoc/net/smtp/rdoc/Net/SMTP.html">Ruby</a> usually works fine.</p>
+<hr>
+<h2 class="light">Testing and Troubleshooting</h2>
+<p>Since targeting a <a href="#compatibility">diverse range of email clients</a> requires some specific and rather quirky markup, Ink doesn&#8217;t always preview properly in the browser. When doing browser tests, we recommend using the latest version of <a href="http://google.com/chrome">Chrome</a>, <a href="http://www.apple.com/safari/">Safari</a> or <a href="http://www.opera.com/">Opera</a>, since Ink doesn&#8217;t always display properly in Firefox or Internet Explorer.</p>
+<p>Testing in the browser isn't enough, however, and you should always test in actual email clients. If you don't have access to the actual clients you want to test, a testing service like <a href="https://litmus.com/">Litmus</a> or <a href="http://www.emailonacid.com/">Email on Acid</a> can help.</p>
+<p>If you're having trouble with an email, the first thing to check is the markup. Often times a simple error like a forgotten <kbd>&lt;tr&gt;</kbd> or a nested tag that's been closed in the wrong order can wreak havoc on your design. If that's not the problem, it could be an issue with your ESP. <strong>Some senders prepend an <kbd>&lt;html&gt;</kbd> tag to your message, which causes the DOCTYPE tag to not be interpreted by the email recipient.</strong> To see if this is what's happening, try sending a test email to yourself and using the "view original" or "view raw source" option in your mail client to manually inspect the code.</p>
\ No newline at end of file