On Feb 11, 2014, at 10:47 AM, Paul Tansley wrote:
Noob question probably. But what version of HTML should I be designing for nowadays (2014). My website had HTML 4.01 Transitional, as the setting and I thought that was fine until recently.
Any new site should be started in HTML5. HTML5 is compatible with all browsers (even broken old IE versions back to 5) and is the way forward for anything new.
I’ve started checking how valid the code is using Google Chrome’s SEO Site Tool and W3C Markup Validation website. It throws up loads of errors, that I don’t really understand at all. But many refer to things like - you can’t use that for this type of Document.
If you don’t paste in any extra code, or use Actions to modify your page, then your page should validate out of Freeway without any reservations, no matter what version of HTML you set your page/site to use. Freeway doesn’t write invalid code, as a rule.
But if you copy some line of code out of an example you found on Google or something like that, and paste it into the Page / HTML Markup dialog, it is certainly possible to end up with invalid code. Even something as simple as mixing XHTML and HTML syntax in the same page will throw off a strict validator.
<link rel="stylesheet" type="text/css" href="path/to/stylesheet.css">
is not the same as
<link rel="stylesheet" type="text/css" href="path/to/stylesheet.css"/>
Or, if you find a bit of script that looks like this:
<script language="JavaScript">...</script>
when it should be
<script type="text/javascript">...</script>
for any version of HTML better than 3.2
Just remember, if you change the output format in the Document Setup dialog, you also need to change each existing page in the Page Inspector, because the Document setup dialog only governs pages you make after that point, not existing pages.
Which makes me wonder, if my document type is wrong to begin with? I presume if my code has HTML errors, google won’t want to rank it very high.
I’ve never heard that one. I don’t think Google does anything like that at all.
That’s not good for a photographer 
Hence, I’m trying to clean it all up.
You should clean it up, but the reason why is that browsers silently auto-correct invalid pages to valid ones before they try to display them. Trouble is, no two browsers (or versions of those browsers) agree on just how to make those corrections. The result is that while it may look okay in one browser, it will probably not look the same (or even similar) in another.
Walter
Any guidance would be much appreciated. This is driving me nuts.
www.stylishweddingphotography.com
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options