Web Standards
0 views
Skip to first unread message
Jack Brighton
Aug 15, 2008, 11:14:17 AM8/15/08
to Public Broadcasting Open Source Best Practices
What are web standards and why should we care? Lately I've been
thinking that many of us (most?) at this point understand the
importance of building our sites based on valid (x)html and css, with
correct structure (using header elements properly for example). We
know these things, but too often we just don't follow through and
apply that knowledge.
Me too: deadlines, a large number of projects, and the extra labor
involved get in the way of the quest for code perfection. Plus when I
talk about web standards to other managers at my station, they get
that telltale glazed look. So what can we do about this?
How about we talk about it frequently at every opportunity? Focusing
on web standards doesn't have to be boring. Really it fits within
conversations on Open Source and Best Practices, and every effort to
improve public media websites. We need to elevate everyone's
understanding and practice, and web standards are a baseline. After
all, we're building things that we hope will persist in the online
future, so let's make them future-proof.
Then we can talk about more interesting things like microformats,
AJAX, and scripting for API integration...fun and powerful
applications that totally don't work unless we've laid a solid
foundation based on valid and well-structured code.
Anyone game?
thinking that many of us (most?) at this point understand the
importance of building our sites based on valid (x)html and css, with
correct structure (using header elements properly for example). We
know these things, but too often we just don't follow through and
apply that knowledge.
Me too: deadlines, a large number of projects, and the extra labor
involved get in the way of the quest for code perfection. Plus when I
talk about web standards to other managers at my station, they get
that telltale glazed look. So what can we do about this?
How about we talk about it frequently at every opportunity? Focusing
on web standards doesn't have to be boring. Really it fits within
conversations on Open Source and Best Practices, and every effort to
improve public media websites. We need to elevate everyone's
understanding and practice, and web standards are a baseline. After
all, we're building things that we hope will persist in the online
future, so let's make them future-proof.
Then we can talk about more interesting things like microformats,
AJAX, and scripting for API integration...fun and powerful
applications that totally don't work unless we've laid a solid
foundation based on valid and well-structured code.
Anyone game?
John Tynan
Aug 25, 2008, 10:13:10 AM8/25/08
to pbo...@googlegroups.com
Jack,
I would say that web standards, microformats and ajax etc. are all fair game and that there is not really a progression from talking about one topic first, before talking about the other. While a lot of things break down if the html code is not valid, I think the value of the discussion arises from the particular relevancy and need.
For instance, I've been doing a lot of work in javascript lately. And so talking about the document object model would be relevant to me. Talking about firebug as an aid to scripting would be relevant. And does anyone use a javascript debugger... If so, what tool do you use, Aptana, the Venkman extension for Firefox? What does it mean to set a breakpoint and why? What effect does this have on the code that I write? Do you mean I can stop writing alert(yourvariablehere);?
Jack, can you tell me the best way to evaluate if your pages are well-structured and valid? Do you run them through a text browser like lynx? Do you use a validator? Do you validate your overall template and then go off on your merry way? How does valid html improve searchability, usability, etc? Do you have a specific issue or process around web standards that you would like to mention?
Thanks for being vocal about this. Best regards,
John T.
I would say that web standards, microformats and ajax etc. are all fair game and that there is not really a progression from talking about one topic first, before talking about the other. While a lot of things break down if the html code is not valid, I think the value of the discussion arises from the particular relevancy and need.
For instance, I've been doing a lot of work in javascript lately. And so talking about the document object model would be relevant to me. Talking about firebug as an aid to scripting would be relevant. And does anyone use a javascript debugger... If so, what tool do you use, Aptana, the Venkman extension for Firefox? What does it mean to set a breakpoint and why? What effect does this have on the code that I write? Do you mean I can stop writing alert(yourvariablehere);?
Jack, can you tell me the best way to evaluate if your pages are well-structured and valid? Do you run them through a text browser like lynx? Do you use a validator? Do you validate your overall template and then go off on your merry way? How does valid html improve searchability, usability, etc? Do you have a specific issue or process around web standards that you would like to mention?
Thanks for being vocal about this. Best regards,
John T.
Reply all
Reply to author
Forward
0 new messages