“…Jeffrey Zeldman\'s Web Standards Advisor is a $49.99 extension for Adobe Dreamweaver. It includes two major interface
- The Web Validator validates your HTML and CSS and verifies the proper use of microformats, including hCard and hCalendar, for single pages or entire websites.
- The Web Standards Advisor checks for subtleties of standards compliance in nine different areasâ€”everything from structural use of headings to proper ID, class, and
element use. Nonstandard practices are flagged and reported in the Dreamweaver Results panel for quick code correction. A full report with more details and suggested fixes is also generated.”
“The definitive resource list for anyone designing, developing, marketing or maintaining websites.”
“Test your knowledge of HTML! This includes only HTML 4 Elements defined by the W3C. (Sorry, no blink or marquee tags).” (Thanks Jon!)
btw, you can see some work XPLANE has been doing for Salesforce over at the Successforce blog.
“You\'d think that as a result of open-source development practices, blog architectures would be pretty close to perfection in areas like Web standards and maximum SEO impact.
You\'d be wrong.
Unbelievably, nearly every WordPress, MovableType, or TypePad theme that I\'ve come across in the past year fails a simple test for truly semantic (and Google-recommended) XHTML markup. Now, I\'ll be the first to admit that these failures are by no means fatal flaws. At the same time, though, I find it extremely unsettling that an inferior markup structure is prevailing in the face of an absolutely correct way of doing things.”
“If you’re a web developer, you’ve probably heard about XHTML, the markup language developed in 1999 to implement HTML as an XML format. Most people who use and promote XHTML do so because they think it’s the newest and hottest thing, and they may have heard of some (usually false) benefits here and there. But there is a lot more to it than you may realize, and if you’re using it on your website, even if it validates, you are probably using it incorrectly. I should make it clear that I hope XHTML has a bright future on the Web.”
“In the time it took the closed and secretive XHTML working group to release a new version of this specification which did not fix one of its simplest problems despite that problem being reported multiple times, the open and transparent WHAT working group wrote an entire HTML specification, more detailed than any previous such effort, and fixed the problem in the process.” (Thanks Daring Fireball!)
“Why does it matter which form of encoding we choose? What happens if we choose the ‘wrong’ one? The choice of character encoding affects the range of literal characters we can use in a web page. Regular Latin letters are rarely a problem, but some languages need more letters than others, and some languages need various diacritical marks above or below the letters. Then, of course, some languages don’t use Latin letters at all. If we want proper — as in typographically correct — punctuation and special symbols, the choice of encoding also becomes more critical.”