Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Well consider this:</p> <p>When serving as text/html, all you need a doctype for is to trigger standards mode. Beyond that, the doctype does nothing as far as browsers are concerned.</p> <p>When serving as text/html, whether you use XHTML markup or HTML markup, it's treated by browsers as HTML.</p> <p>So, really it comes down to using the shortest doctype that triggers standards mode (&lt;!DOCTYPE html>) and using HTML markup that produces the correct result in browsers.</p> <p>The rest is about conforming, validation and markup prerference.</p> <p>With that said, using &lt;!DOCTYPE html&gt; now and trying to make your markup conform to HTML5 is not a bad idea as long as you stick to stable features that work in browsers now. You wouldn't use anything in HTML4 or XHTML 1.x that doesn't work in browsers, would you?</p> <p>In other words, you use &lt;!DOCTYPE html&gt; with HTML4-like markup while honoring things that have been clarified in HTML5. HTML5 is about browser compatibility after all.</p> <p>The downside to using HTML5 now is that the spec can change quite often. This makes it important for you to keep up with the spec as it actively changes. Also <a href="http://validator.nu/" rel="nofollow noreferrer">http://validator.nu/</a> might not always be up-to-date, but <a href="http://validator.w3.org/" rel="nofollow noreferrer">http://validator.w3.org/</a> isn't always up-to-date either, so don't let that stop you.</p> <p>Of course, if you want to use XHTML 1.0 markup and conform to XHTML 1.0, then you shouldn't use &lt;!DOCTYPE html&gt;.</p> <p>Personally, I always use &lt;!DOCTYPE html&gt; for HTML.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload