[tags]zeldman, webstandards, bigthink, interview[/tags]
Bigthink.com/jeffreyzeldman is your BigThink channel for all your BigThink Jeffrey Zeldman needs. Now playing at that URL are three Zeldman interview clips for your pleasure:
- “Jeff” Zeldman dissects online journalism
- “Jeff” Zeldman outlines the history of blogging
- “Jeff” Zeldman discusses the future of open source
View early and view often. Happy watching and blogging.
[tags]bigthink, zeldman, jeffreyzeldman, interviews, internet, web, design, history, journalism, online, onlinejournalism, webpublishing, opensource, webstandards[/tags]
At corebasis.com, Henning von Vogelsang modestly presents his initiative to use an asterisk as a semantic reference for “source:”
Recent history taught us, if something is simple, makes sense and it is easy to use, it will most likely become a standard. … Through the increasing expansion of Twitter, the at-sign (@) has become a standard reference for a sender’s name. … Another change (introduced 2007) was the usage of hashtags (#). …
To help distinguish the source of information from a person, I propose we start using the following pattern:
[tags]semantics, micro, asterisk, proposal[/tags]
I discuss “open source design” in an excerpt from a long interview at Big Think. The full interview, with a complete transcript, will soon be available there as well.
BigThink’s Merrell Hambleton did a great deal of research prior to conducting the hour-long interview, and was thereby able, not only to probe typical Zeldman topics in greater depth, but also to ask interesting questions outside my comfort zone.
The interview was carried out via Interrotron, a fascinating device invented by Errol Morris.
[tags]bigthink, zeldman, design, webdesign, opensource, standards, webstandards, libraries, jeffreyzeldman, interview[/tags]
Fred Gates interviews me and we take your calls, live, on Blog Talk Radio tonight.
Visit blogtalkradio.com/IGMRinFOCUS between 6:00 and 7:00 PM ET and phone in with your questions. Design. Writing. Client and career management. Web standards. DWWS 3e. Nothing’s off the table. Sound off and share. See you on (virtual) radio.
Update – download the interview
[tags]fredgates, IGMRinFOCUS, BTR, BlogTalkRadio, live, interviews, podcasts, zeldman, jeffreyzeldman, microstardom[/tags]
The complete schedule for An Event Apart Boston is now online for your reading pleasure.
Join Eric Meyer and your humble host with truly special guest speakers Jason Santa Maria, Jeremy Keith, Joshua Porter, Whitney Hess, Dan Cederholm, Daniel Mall, Derek Featherstone, Aarron Walter, Scott Thomas, Heather Champ, Andy Clarke, and GoodBarry’s Brett Welch for two days of design, code, and content.
An intensely educational two-day conference for passionate practitioners of standards-based web design, An Event Apart brings together thirteen of the leading minds in web design for two days of non-stop inspiration and enlightenment. If you care about code as well as content, usability as well as design, this is the one you’ve been waiting for.
Educational discounts and group rates are available, and everyone saves $100 during the early bird registration period.
[tags]aneventapart, AEA, webdesign, conference, webstandards[/tags]
DOM whiz and loyal-opposition/web standards advocate Peter-Paul Koch has been working overtime preparing detailed findings on CSS and DOM compatibility in modern browsers, including:
- CSS in all new browsers
- W3C CSS Object Model in all new browsers
- DOM Events in Opera 10a and Chrome 1
- DOM CSS module in Opera 10a and Chrome 1
- DOM HTML module in Opera 10a and Chrome 1
It’s a great resource from an expert who really cares, and who has the time and expertise to find things out for the rest of us. Thanks, PPK!
Join me on Blog Talk Radio at 6:00 PM Eastern Time on Wednesday 1 April 2009.
We will interview best-selling author, designer, and web standards evangelist Jeffrey Zeldman will about his career, his books, and the future of the internet and social media.
Join us live. Bring your questions about web design, web standards, client services, independent publishing, blogging, book authoring, DWWS 3e, or anything else you’d like to talk about.
[tags]design, webdesign, zeldman, radio, interview[/tags]
[tags]tim murtaugh, mike pick, seed, seedmagazine[/tags]
While working on the third edition of Designing With Web Standards, I decided to visit Alexa’s Top 100 US Sites to see how many of the top 100 use valid markup, how many nearly validate (i.e. would validate if not for an error or two), and which DOCTYPEs predominate. Even with a fistful of porn sites in the mix, it was dull work: click a link, load the home page, run a validation bookmarklet, record the result.
I had no expectations. I made no assumptions. I just clicked and tested.
Such tests tell us little
I make no claims about what I found. If all the home pages of the top 100 sites were valid, it would not mean that the pages beneath the home page level were valid, nor would it prove that the sites were authored semantically. (An HTML 4.0 table layout with no semantics can validate; so can a site composed entirely of non-semantic
divs with presentational labels.)
Validation is not the be-all of standards-based design; it merely indicates that the markup, whatever its semantic quality may be, complies with the requirements of a particular standard. Conversely, lack of validation does not prove lack of interest in web standards: ads and other third-party content can wreck a once-valid template, as can later third-party development work.
Moreover, nothing causal or predictive can be determined from these results. If 25% of the top 100 sites validated in my test, it would not mean that 25% of all sites on the web validate.
And I got nothing like 25%.
Enough disclaimers. On with the test.
Seven percent validate
On this day, in this test, seven out of 100 “top US” sites validated:
- MSN (#7 in Alexa’s list) validates as XHTML 1.0 Strict. Who’d a thunk it? (Validation link)
- Craigslist (#10) validates as HTML 4.01 Transitional. I’ll buy that! (Validation link)
- WordPress (#22) validates as XHTML 1.0 Transitional. The power of the press, baby! (Validation link)
- Time Warner RoadRunner (#39) validates as XHTML 1.0 Transitional. Meep-Meep! (Validation link)
- BBC Newsline Ticker (#50) validates as XHTML 1.0 Strict. Cheers, mates! (Validation link)
- The US Internal Revenue Service (#58) validates as HTML 4.01 Transitional. Our tax dollars at work! (Validation link)
- TinyPic (#73) (“Free Image Hosting”), coded by ZURB, validates as XHTML 1.0 Transitional. (Validation link)
Also-rans (one or two errors)
- Wikipedia (#8) almost validates as XHTML 1.0 Strict (two errors).
- Apple (#29) almost validates as HTML 4.01 Transitional (two errors).
- Linkedin.com (#45) almost validates as HTML 4.01 Transitional (one error).
- AWeber Communications (#83) almost validates as XHTML 1.0 Transitional (one error: an onClick element)
The Pirate Bay (#68), “the world’s largest BitTorrent tracker,” goes in and out of validation. When it validates, it’s a beautiful thing, and it belongs on the list. But when it goes out of validation, it can quickly stack up ten errors or more. (Validation Link)
Google (#1) does not validate or declare a DOCTYPE.
Yahoo (#2) does not validate or declare a DOCTYPE.
YouTube (#3) does not validate but at least declares that it is HTML 4.01 Transitional. Progress!
A surprising number of sites that do not come close to validating declare a DOCTYPE of XHTML 1.0 Strict. For instance, Twitter (#93) is authored in XHTML 1.0 Strict, although it contains seven errors.
This preference for Strict among non-validating sites suggests that at one point these sites were made over by standards-aware developers; but that any standards improvements made to these sites were lost by subsequent developers. (It doesn’t prove this; it merely suggests.) Another possibility is that some developers use tools that are more standards-aware than they are. (For instance, a developer with little to no knowledge of web standards might use a tool that defaults to the XHTML 1.0 Strict DOCTYPE.)
Some sites that used to validate (such as Blogger.com, previously designed by Douglas Bowman, and Reference.com, previously designed by Happy Cog) no longer do so; maintaining standards or design compliance may not have been important to new owners or new directors.
[tags]validation, webstandards, alexa, test[/tags]
Sorry I haven’t written much here, lately, but I’ve been working on the third edition of a book you may know.
[tags]dwws, designingwithwebstandards, 3rdedition, 3e, DWWS3e, newriders, peachpit, zeldman[/tags]
Web designers and developers power the global economy, but almost nothing is known about who we are, where we live, how we work, what tools we use.
The A List Apart survey (2007 survey, 2007 detailed findings, 2008 survey) of over 32,000 full-time, part-time, and freelance web designers, developers, and related user experience professionals began answering questions about who works in this field, where we are located, which kinds of businesses and organizations employ us, under which titles we work, what we earn, how satisfied and secure we are, and so on.
Complementing this information, in 2008 Web Directions North conducted a State of the Web 2008 survey of designers, developers, and other web professionals to find out more about our philosophies, technologies, and best practices. The findings include details and analysis of all responses to over 50 questions. You can read all the questions, download the complete (anonymized) set of responses, read detailed analysis, and more.
[tags]webdirections, survey, webdesign, webdevelopment[/tags]
What better way to begin 2009 than by looking at the future of web design? In Issue No. 275 of A List Apart, for people who make websites, we study the promise and problems of HTML 5, and chart a path toward mobile CSS that works.
by DOMINIQUE HAZAËL-MASSIEUX
by JOHN ALLSOPP
The BBC’s dropping of hCalendar because of accessibility and usability concerns demonstrates that we have pushed the semantic capability of HTML far beyond what it can handle. The need to clearly and unambiguously add rich, meaningful semantics to markup is a driving goal of the HTML 5 project. Yet HTML 5 has two problems: it is not backward compatible because its semantic elements will not work in 75% of our browsers; and it is not forward compatible because its semantics are not extensible. If “making up new elements” isn’t the solution, what is?
[tags]HTML5, mobileCSS, webstandards, alistapart, johnallsopp, W3C, Dominique Hazael-Massieux[/tags]