Web Standards and Maintenance
November 13, 2003 |
4 Comments
It’s one thing to design and build a forward-thinking, valid, and Web standards based site. It’s quite another to keep that site forward-thinking, valid and Web standards based. It defeats the purpose entirely if you can’t maintain your site and keep it up to standards. Pardon the pun.
It takes work and lots of it. You might be in a position to do that work yourself, or you might have had to hand the site of to others. Either way, you need to prepare for the extra discipline that maintaining a valid Web standards based site needs.
I’m still learning what this entails myself, as I’ve just begun to have to work with a large and (almost) fully compliant standards based site on a day to day basis. Let me tell you, it’s not all it’s cracked up to be. At least not yet.
I do have a few pointers and tips:
- Validate on a regular basis. Run your as much of your site through the validator as regularly as possible. Checking your updates in the browser isn’t always enough. You’ll catch all sorts of little things. You might want to do as I’m going to do and make a regular schedule for validation checks.
- Beware cut & paste. Always double check anything you are cutting and pasting into your pages, regardless of how you serve content. This is where I’ve noticed the majority of validation errors cropping up.
- Create a list of “gotchas”. These are things that you may easily forget when coding pages. It’s easy to revert back to a non-standard way of coding by habit and a list, or better yet — a checklist, can help.
- Share common issues. Make sure that everyone involved with maintenance is aware of the possible errors that can creep in. Down at the hospital we’ve started a K-log to track the bits and pieces of standard XHTML.
- Train your content contributors. This is far easier said than done. If possible, provide cheat sheets and detailed instructions about ways validation errors can creep in. Double checking their work would be a good idea as well. After all, you can’t expect most content contributers to master this stuff overnight.
- If you are handing a site off, make sure you set up to succeed. This could be providing documentation, in as much detail necessary, what needs to be done to keep a site valid, or it could be a simple training session. Depending on who is taking over you could go many ways, just make sure everyone is on the same page.
Maintaining a standards based site takes discipline and may seem like an added load or hassle, but it has to be done. I’m sure once you get into the habit, it’ll become like second nature and the overall quality of you site will improve.
Filed under: Web General
Comments
1. Simon Willison said:
There’s a lot to be said for using technology to support the production of valid code. I’ve learnt a great deal about this just from running my blog as XHTML 1.0 Strict with an application/xml+xhtml content type, which forces me to keep things valid because invalid XML just won’t render in my browser on pages with that content type.
If your editing tool for updating the site involves editing HTML in textareas, the bookmarklet described on this page http://simon.incutio.com/archive/2003/08/27/textareaValidation is an absolute God send.
Posted on November 13, 2003 12:05 PM | #
2. Keith said:
That Blogidate book marklet is awesome! How did I miss that one??
The thing is, depending on you situation, there maybe be reasons why you wouldn’t want to be too rigid.
For example, if you are using a distributed authorship model you probably won’t want to use anything that could actually break the page on minor validation errors.
I mean, for the most part the errors I come across at work actually don’t effect the site as far as display and functionality, and I’d hate to put in a system so ridged that it broke every-time someone other than me made an update.
Tools like the bogidate can be a great help though. Thanks Simon.
Posted on November 13, 2003 12:30 PM | #
3. Josh said:
I found a great resource for getting people who are not as into standards up to date on the basics of making a good, forward thinking page. It might help some people:
http://labs.silverorange.com/local/solabs/include/styleguide/
I find it very useful.
Posted on November 13, 2003 10:16 PM | #
4. Simon Willison said:
“For example, if you are using a distributed authorship model you probably won’t want to use anything that could actually break the page on minor validation errors.”
I couldn’t agree more. That’s why I’m not a big fan of XHTML (where validation really is critical - an invalid XHTML document probably isn’t valid XML, so what’s the point?) for sites which are frequently edited by multiple authors. It’s possible to build a CMS that will enforce XHTML validation but it comes at a cost of ease of use and flexibility for authors.
Posted on November 14, 2003 01:48 PM | #
Comments are now closed