Hey web devs! We knew you'd look under the hood. Please pardon the mess...we still have some clean up to do. If it drives you crazy and you want to help us get it perfect, maybe you should join our team! We could use another set of hands!
Steven Champeon pioneered the markup best practice of Progressive Enhancement that has been embraced by the web industry and adopted by organizations such as Microsoft, Yahoo!, and America Online. Steve is also the founder of the webdesign-L online community, founded in 1997 and 2300+ members strong. Champeon's widely respected status as a "web guru" is evidenced by his impressive list of publications and speaking engagements. Champeon is a contributor to Unix Power Tools, 3rd edition, Cascading Style Sheets: Separating Content From Presentation, now in its second edition, as well as the author of the groundbreaking Building Dynamic HTML GUIs.
As a technical editor, Champeon has contributed his expertise in XML, XHTML, CSS, Unix, MacOS X, Apache, and related topics for books published by O'Reilly and Associates, Apress, Macmillan/New Riders, John Wiley and Sons and several other publishers. He is also a frequent contributor to online and print magazines for Web professionals, including Webmonkey, the O'Reilly Network, Apple's Internet Developer, and many others.
A highly sought after speaker at trade conferences, Champeon has donated his expertise to the advisory boards of South by Southwest (SxSW) Interactive and the CMP Web conference circuit in addition to over a dozen speaking engagements at those and other conferences. Champeon has also been a guest lecturer at the University of North Carolina-Chapel Hill and is an invited guest lecturer of North Carolina State University's College of Management MSM program. Champeon is a graduate of Syracuse University.
Just as with the Web, standards (as well as widely-accepted conventions) are vital to the continued success of email as a medium. Many of the threats to email as a medium are rooted in a laxity and tolerance for failures to observe standards, or failures of, or weaknesses in, the protocol-defining standards themselves. By enforcing and enhancing existing standards, fixing the existing holes in those standards, and introducing various new standards, we can fix email.
Your corporate Web site…to you - an investment – and being such, you didn’t let the CEO’s nephew design it. You issued an RFP; you went through a formal vendor selection process; and then you hired a professional firm to ensure that your corporate site (often the first impression of your business) was both useful and usable, separating form and function from presentation and style. A real A+ job. And now that you’ve built it, they will come. Right? Wrong.
Tonight, when you get ready to retire for the evening, do me favor. Take your wallet — complete with social security card, credit cards, driver's license, and what the heck, throw in the family pictures — and leave it at the edge of your driveway. Then sleep well.
Spam, also known as unsolicited bulk (and/or commercial) email, is not only annoying, but costly - and the problem is getting worse. Beware, however: the tools we use to fight it often introduce new risks and costs. Recognizing the nature of the problem and its risks is necessary in order to minimize these risks and fight back effectively.
Back in March of 2003, Nick Finck and I stunned the Web design world at the South by Southwest Interactive conference in Austin. How? Well, despite a late night spent chowing down fish tacos and swilling Shiner bock, we actually managed to show up early Sunday morning to deliver our presentation.
Web design must mature and accept the developments of the past several years, abandon the exclusionary attitudes formed in the rough and tumble dotcom era, realize the coming future of a wide variety of devices and platforms, and separate semantic markup from presentation logic and behavior.
The average reader — one not raised by wolves, or, worse, by rabid advocates of Standard Generalized Markup Language during the heyday of SGML — may not clearly understand the concepts of Semantics, Structure, Markup, Content, Style, Transformation, and Presentation. Heck, I'm not sure many of us did back then either, but we've had a few years to think about it.