@rtretheweyMar 20.2013 — #Largely, HTML 5 is a further evolution into the separation of content and presentation. It brings new semantic tags that designate the purpose of the content, rather than focusing on how that content is shown to users. In addition, it brings new capabilities for graphics and media, and an inherently higher level of cross-browser compatibility. Search on "Dive into HTML 5". It's a great place to get acquainted with this technology.
@jedaisoulMar 22.2013 — #A lot of the glory of HTML5/CSS3 is being stolen because the browsers support many of the new features in HTML4/CSS2 pages. Another problem is the proliferation of browser-specific syntax which is messy and cumbersome. That said, HTML5/CSS3 removes some of the obsolete features from HTML that are already duplicated (often bettered) in CSS. So, in my opinion, it is better to learn and use HTML5/CSS3.
There is however a practical issue: the WDG HTML validator, which allows you to validate a whole site in one go, is HTML4 only. Whereas, the W3C HTML validator is HTML5 compatible, but only validates one page at a time. If you work methodically on one or two pages at a time, and validate regularly, this is not a major problem, but if you need to make similar changes to many pages, it can be a pain.
To partially overcome this limitation, I have written a front-end to the the W3C HTML, CSS and link validators. You can still only validate one page at a time, but you can validate the HTML, CSS and/or links in one go. In practice the links validator is significantly slower than the other two, so I often validate just the HTML and CSS, but it is still of benefit to be able to run both validators from one input. I've also added the facility to select the files to validate from pick lists. This requires some setting up but allows you to step through validating a sequence of web pages with minimal fuss. Pick lists in plain text or Sitemaps XML format are supported, so if your site is set up for Sitemaps, you already have pick lists! The facility is provided free, requires no registration, and is located at http://www.emberwebsites.co.uk/html/. So if you are interested, give it a try...
@johnny916authorMar 22.2013 — #I have no idea what you're talking about in regards to validing one page or the entire site?? Why do you need to do that? Don't we just test it in every browser?
@rtretheweyMar 22.2013 — #Testing in different browsers is always a good idea, but browsers are very tolerant of coding errors. So, routinely validating your code insures that it's actually correct and not simply that it "looks OK". Valid code is easier to maintain, and gives you the best chance that your site will display properly in browsers you didn't test. It also insures that search engines will parse it properly so they see everything that you want them to see.
@IT_GuyMar 23.2013 — #The big part of HTML5 for me was you no longer need to code for the different browsers. A lot of the tags became universal. I used to have to type a tag normal and then again with -webkit- and -moz-. Now I can type it the plain way and it will work on all the different browsers.
@johnny916authorMar 23.2013 — #I went on that site, W3C validator but it says Validation Output: 39 Errors and doesn't really reference which style sheets either.. Do I really have to clear all those errors to be considered a professional?
@IT_GuyMar 23.2013 — #I see thousands of webpages that do not use XML and are very professional. It's useless to me. Everything I do on a website can be done in HTML, CSS, and PHP. Sometimes even a little java for more client side interaction.
@jedaisoulMar 24.2013 — #I went on that site, W3C validator but it says Validation Output: 39 Errors and doesn't really reference which style sheets either.. Do I really have to clear all those errors to be considered a professional?[/QUOTE] To have only 39 errors on your first ever validation, deserves a round of applause! But yes, you should correct every error. Was this the HTML or the CSS validator you ran? If the CSS, you can run it against specific CSS files, if running it against the HTML is not clear. If you ran the HTML validator it ignores CSS errors. Hence why I've written a front end to validate both at once (and the links if required).
@jedaisoulMar 24.2013 — #I see thousands of webpages that do not use XML and are very professional. It's useless to me. Everything I do on a website can be done in HTML, CSS, and PHP. Sometimes even a little java for more client side interaction.[/QUOTE] I agree, I'm suggesting using HTML5 not XML.
@parthoApr 03.2013 — #HTML5 is the begning of the third age of the WEB in which HTML advances at a brisk pace towards becoming a true application delivery format.HTML5 is not only the limited to presentation, but it is also provides of new functions for Web and other types of applications.