Opera Web Standards Curriculum

Opera recently released a set of succinct educational articles on the foundation of the web, standard technologies and well-written introductions to vital web design topics, aptly titled the Opera Web Standards Curriculum (WSC).

At first I asked myself why something like this was necessary in the year of 2008—don’t students get taught web standards through college and univeristy these days? If not, aren’t there already are number of good resources available, free and commerical? I had a bit of a read, starting right at the beginning and found partially the answer in the fifth article:

“…The general feeling I get from looking at numerous university courses is that web languages like HTML, CSS and JavaScript are below the technical threshold of most computer science programs, and above the technical threshold of most MIS/New Media programs.

What I’m getting at here is that many educational courses don’t cover this kind of stuff in any great level of detail. I would be willing to wager that if you ask 10 developers that work with web standards where they learned how to use web standards that 9 of them would reply that they are self-taught (the other 1 won’t answer you because she’s too busy trying to get her site to render properly in IE6).”

Previously defined acronyms earlier in the quoted text have been redefined.

I started an IT course in college that focused on publishing content onto web-based mediums in early 2006. I was told we would not touch CSS until the end of the second year, and mention of web standards was not to found in the entire curriculum document. I promptly left the course. As Jonathan Lane points out, most standards-based web designers and developers are probably self-taught—I am.

But why another set of articles ontop of the many resources that already exist? Because commonly it’s scattered across the Internet or because you’d need to purchase books (and in the case of students, those university text books can be quite pricey). The neat thing about web design and developement is that articles like those from the WSC appear in the same canvas we work on and consequently offer interactive examples—and best of all are freely accessible. Books can be nice—particularly well set ones—but for someone just starting with web standards beginning with the WSC marks a good beginning.

The WSC doesn’t go into great technical detail. Instead, it offers the background information that is often omitted from the more technical articles on developer blogs or on related publications. Something like this would have been great in place of the IT course I entered a few years ago.

Apart from being an introduction to the creation of the Internet, how it came to be what it is now and why standards are good for everyone, the WSC also features introductory articles on information architecture, accessibility, usability and content context, colour theory, wireframing, assorted mockup tips and last (and best of all), an article on web typography.

The Opera WSC will probably be my future recommendation for newcomers to web standards, HTML, and the selected articles above. I would even recommend them to the experts—pick a topic you haven’t dealt with in a while and make sure you’re up to scratch (there are a few questions at the end of each article).

Kudos to Opera.

3 comments

  1. 1. J Lane
    Jul 18, 13:55

    You hit the nail on the head. Chris Mills, the man that drove this initiative forward, should be commended for his efforts in this field.

    Any (formal) courses that I took about web production were so full of misinformation and garbage. When I finally discovered “the Zeldman book” it was such a breath of fresh air.

  2. 2. Tate
    Jul 19, 13:26

    This is excellent. I’ll certainly be forwarding it on to my 1621 ICT peers next semester!

  3. 3. Pascal
    Aug 02, 02:35

    @J Lane: Chris Mills definitely deserves a beer or three for this.

    I have to admit I haven’t read Zeldman’s book yet—something to add to the next round of my Amazon “to-purchase” list. Thanks.

Post a comment

Please share your thoughts or add a note if I missed something.

Required fields are marked by an asterisk (*). Your e-mail address is never published nor shared. You can use common text formatting XHTML elements (e.g. a, acronym, blockquote, code, em, strong, …). If you’d like to directly respond and link to another comment, you can do that using the Twitter-style @reply (i.e., @Randy Bender: …).

*
*