PSA: Puget Sound higher education web professionals dinner

I sent this to some of the email lists that I’m on, but I thought I’d mention it here, too.

Along with Deirdre Peters at North Seattle Community College and Susan Bustetter at Evergreen, I’ve organized a dinner for higher ed web people (managers, designers, etc.)….

Friday, March 4 at 6 p.m.
Costas Greek Restaurant
4559 University Way N.E.
Seattle, WA 98105-4510
Phone: 206-633-2751

There’s no particular agenda planned, just an opportunity to talk to peers and such. (I’m assuming that those attending the CASE conference will have information to share from that experience.)

I will be making reservations, so if you’re interested, let me know! (A comment on this entry will be fine, or you can use my contact form.)

a long ramble

Last night I went to C’s nonprofit capstone (think senior project) class to talk weblogs, accessibility, and whatever. It turned out to be a fascinating experience, talking all over the map; lots of talk about syndication, which is still not being well expressed outside tech circles.

One woman uses My Yahoo and had seen the RSS thing, but had no idea what the hell it meant. Also, she had already heard of blogs through her college-age son. (Apparently, it’s what all the college kids are doing these days.)

Why blog? was the big question, and I found myself coming back again & again to: let the tech/tools get out of the way so (a) non-tech people can be involved and (b) they can focus on content instead of technology.

Another woman is working on a local hospital for her project, and I mentioned Keith’s work with Seattle Children’s and Mike Kelley’s work with wherever it was he used to work. (Should probably link that stuff.)

Talked about advantages of blogs over Blackboard: pretty much all the students complained about not being to access (BB) resources from previous classes, and that they’d want to be able to get at them as professionals after they graduate. C brought in the idea of integrating BB & a blog.

He had a lot of good stuff to say, and it was kinda cool for me to see him jump in with things that I think he’s acquired by osmosis from me. 🙂 And then synthesized with his own intense thought process, experiences, etc. to form really quite powerful ideas. Someday I’ll get him blogging, I swear.

Accessibility ended up being sort of a sidebar…covered the basics of what 508 and WCAG *are*, but with much less tech than if they were, say, a web design class. 🙂 Talked about some of the specifics of technologies used, wished I had the demos that the keynote speaker at HEWD had had. Made most of the points that I wrote down yesterday re: reasons for accessibility. This was an audience for which “it’s the right thing” really resonated, which is nice. The Joe Clark quote got a chuckle, but also nodding of heads in re: professionalism and cache of having that additional thing.

A little bit about the role of weblogs in developing communities of practice: C tried to bring it up early in re: nonprofit orgs, but got garbled in his own thoughts (his comment, not mine), and I brought it up again at the end in re: web designers, mentioned meeting Keith at WebVisions. (which was darn cool.)

Demonstrated how to blog with WordPress: the ease of adding a link got oohs and ahs. 🙂 Same deal with categories. Some confusion about how does it know where to publish, talked about setup, user accounts, the group blog.

Didn’t get a chance to mention The Kitchen as I wanted to. 🙁

All in all, it was a bit of a ramble, moving back and forth over various subtopics: not a bad thing, but I wish I’d had a tighter presentation ready beforehand. I think I can be more flexible if I’m more prepared up front, oddly enough. (I don’t have C’s gift for extemporizing.) But I’m very happy with the experience. It’s energizing to be able to talk about the things I love with people who are engaged.

interlocking pieces of accessibility

consider this a rough version of my thoughts on accessibility and the reasons why. hopefully will fill out as I go.

The worst reason: lawyers
The law in some countries is very clear on Web accessibility. (At least that it’s required, whatever the standard itself may look like.) The United States isn’t one of those countries. If you’re a federal government agency, it’s clear: Section 508. But does 508 apply to other sorts of things that get federal money (like state agencies, schools, non-profits)? Maybe. Does the ADA apply? Maybe.

But that’s a crappy reason, anyway. Here are some better ones:

Google will like you better
Most of the things that get in the way of visually-disabled people get in Google’s way too. Add alt attributes, don’t use frames, make JavaScript unobtrusive: better for both.

Get the benefits of standards
“Web standards” and accessibility are often found intertwined, and with good reason. It’s easier to make a page accessible if it follows standards. Using valid code has some interesting benefits of its own: done well, it’s easier to maintain and saves bandwidth.

(Usually) make it more usable
Many specific techniques that are suggested for accessibility also make your site more usable in general. (no “click here”, clear difference in link color, clear writing) Sometimes the goals of usability for the non-disabled and accessibility for the disabled are in conflict, but those tend to be edge cases.

Do the right thing
If you incorporate accessibility at the beginning of every project, then it’s not (usually) any more expensive, so why not? (There are edge cases, mostly revolving around multimedia.) Would you be such a jerk as to not hold open a door for someone who had both hands full? Then why slam the door on someone who wants to use your site?

For non-profits and schools, it’s not just a matter of being polite; our missions are to serve, in whatever capacity. Our values are (usually) inclusive. Having an accessible website is an opportunity to live our mission and values.

Warm and fuzzy, efficient and effective: plus if the lawyers ever knock at the door, you won’t have to break a sweat. Sounds good to me.

Joe Clark also talks about reasons to go accessible in his excellent book…

Once you learn accessible design techniques, you heighten your sophistication, and may then stand taller in the saddle. ?You mean you don?t know about accessibility?? you may archly ask your inferiors, rolling your eyes and sharing a knowing grin with your compadres.

on weblogs

(some notes/talking points)

what is a weblog?
* asterisk
* eowyn797
* Talking Points Memo
* Metafilter
* Pierce College News
* (this!)

what services? (login where I have an account) big 4:
* Blogger
* LiveJournal
* Movable Type
* WordPress
* lots more, including “home-grown” (missouri! but the about missouri link is broken)

syndication
* specs blah blah blah
* easy to read lots of stuff
* oddball uses
* readers: Bloglines (show Dorothea’s feeds), Feed on Feeds (ouroboros, show mine), FeedDemon, NetNewsWire

why would you? (as org)
* easier to write
* Google likes ’em
* build communities (comments, syndication)

how to start
* figure out what you need & know
* budget? (0 to hundreds, depending)
* evaluate the tools (where’s that grid?!)

things to watch out for
* problems with comments (spam, flames, etc)
* writing becomes more important
* reinforces web as a process, not a product: are you ready for the committment?

resources
* books (essential blogging, we blog, rebecca blood’s handbook, genius strategies)
* sites (tool-specific, plus The Kitchen)

for the HEWD people

here’s my conference notes category: http://www.epersonae.com/ew/index.php/categories/hewd-2004

(I don’t usually use categories here, so there’s no listing for it in my archives.)

these notes represent my summaries, intuitions, inspirations, and opinions. they are certainly not either a transcript nor an authoritative record. oh, and I’m an opinionated bastard.

also, at some point, I’ll clean it up and post a version more like my webvisions notes from this last July.

best of track: a class (year) site

came in a bit late. 2 guys from URochester. I can see why this did so well in the reviews: they have a good presentation style, maybe one of the best I’ve seen all week.

establish unity, provide communication, basic resource.

URL sent with admittance letter. content added as needed.

first done for class of ’05, started in their sophomore year (was then an incoming student site). that would’ve been 2002, I think. class of ’07 was launched 4 weeks before start of school (2003); ’08 got the early date like they described up front.

this is definitely aimed at the four-year process; I’ll be listening for things we can do in *our* environment, which is significantly less uniform.

calculation of “creative hours” which is a growing trend, but levels off now, because they know what they’re doing. 🙂

benefits, started by calculating site traffic. drawing people back by adding info gradually.

used Yahoo groups, then converted to an inhouse message board where students’ user ids were the same as email addresses. nice.

quotes from faculty/staff on the success of the project. parents said it reduced stress. downward trend in phone calls with questions, quote from orientation staff. heading off questions before they’re asked.

going thru look/feel of various years. 2nd one had a calendar as the centerpiece.

they did some work to sell on having a look/feel that’s different from the main templates, with the goal of differentiating from previous/next years.

all done with Dreamweaver/Fireworks/Photoshop. no dynamic stuff. student/volunteer webmaster in coordination with “dean of freshmen” (?!) also head of orientation.

asked us what we’d wanted to know before we got here. (51% of their students are out of state)

then added more staff, brought in admissions office. lots more content, communication opportunities, downloadable forms.

then added orientation system using college-wide login for filling out forms electronically.

q: why not just use a portal? (so much obsession with portals!) most of their staff is focused on getting content. followup question: keeping it going after the start of school?

had to use school colors for the ’08 site.

(ugh. this is interesting on its own merits, but only vaguely related to our environment. and that spot inbetween my thumb & first finger is starting to ache. weird stuff with using the trackpad, I think.)

they upgraded to CSS2, but forced people to upgrade browsers. said nobody had problems, but I just don’t see any reason why they should’ve.

more technical & content improvements the next year. more connections between depts. moved to PHP/mySQL. selling the university…used article about the class site in promotional materials for prospective students.

class site hand-off…their goal is not for an incoming students site, but for a site that’s connected to the actual class. they hand it off on Sept. 1 to Student Activities. they get to keep the site until the very last person in the class *dies*. jesus christ on a crutch.

ew, he just quoted back the idea that gets slammed in “conference presentation judo”:http://perl.plover.com/yak/presentation/samples/slide001.html — which I used to some extent as my guide for my presentation.

some wireframes of what they’re looking at for next year. quick facts, live weather, rss (! “we don’t touch it, it changes daily, we like that”), hot topics (from the message board).

highed.dulongvanscott.com

q: who gave signoff on showing weather? wow, weather is a big deal here.

q: what about transfer students? a lot of info works for them, but they also can use the orientation site. (I’m not thrilled with their answer.)

q: what does your site look like now? (to one of the students) not too bad.

I’m finding the discussions related to non-standard students, not just transfers, but 5-year (engineering majors).

q: what about content policing? no administrators moderating. these two guys moderated. followup: student life questions, who answered? some other year students, but they gave some misinformation.

my q: were students informed of policy? yes, and it’s their basic acceptible use policy.

q: how did you find problem messages? he was just there all the time.

I’ll need to think about how/whether any of this has an application to us.

best of track: conversion to web standards

Daniel from UWisconsin Platt
http://www.uwplatt.edu/web/webstandards

talk about changes in methodology, along with concepts, reasons to make the switch.

zen thing: is standards, aren’t standards.
if you think of the W3C as the UN… if the countries in the UN don’t want to play well, they don’t. but the UN at least has an army; maybe the W3C should?

XHTML, CSS, DOM, ECMAScript 262 (he keeps pronouncing ECMA as a word rather than an acronym, makes me crazy)

“HTML is dead.” (okay, whatever.) if there’s no HTML, then what the heck is XHTML? (digression: SVG got merged into XML) huge freaking quote on what XHTML is.

how to convert to XHTML: doctype, lower case, quoted attributes, end tags everywhere, proper nesting, validation. “validate first before you ask me a question; it’ll save us both a lot of time.”

benefits? accessibility (at least more so), eliminate silly mistakes — works well in old browsers, because it’s tight (my word) no guessing needed.

XHTML is our future, moving from HTML to XML. now he’s tripping; XHTML 1.0 transitional/strict is doable I think for most people, but 1.1?! and talking about 2.0, you might as well be smoking crack.

q: why transitional? I don’t know about his answer.

HTML structure. most corporate is going to use table design (except not so much anymore): nice layout, predictable. hard to find stuff (although his example is faulty, I think, because it’s the kind of thing that would likely be drawn from a db). don’t do it.

div is alternative to table. huh? this sounds like the road to divitis. separation of structure from layout/presentation. divs as the skeleton.

*now* he says don’t overuse, talks about divs for major sections.

browsers: as long as we point back to W3C, we should be prepared. rant vis a vis WYSIWIG editors, the “hi mom” effect: HTML generated in word, which makes Baby Jeebus cry.

then CSS “skinning concept” like face plates for a cell phone. “we just swap out the CSS” — well, in the best of all possible worlds. 1st css design is painful, but then redesigns are easier, faster.

ah, the zen garden; he mentions Dave & Molly’s book.

suggests using lots of stylesheets: base, @import, layout “separate from skin” (huh?), print.

print view of Slashdot. didn’t the user just want the content? I wonder about print stylesheets: they’re a sweet idea, but do “average” users understand the idea?

“information superhighway” not “design superhighway” (photo of Al G) info should come first, design isn’t important. hrm.

backward/forward compatible. ready for the future!

he very briefly alludes to the slashdot makeover. (in ALA?)

bandwidth savings.

oh, hey, he’s the guy who *wrote* the article about redoing Slashdot with web standards. he’s talking about that now, but then again, I read that article when it first came out. talks benefits: not originally impressed with bandwidth savings 2-9 K…but it adds up. 14GB daily.

personal bandwidth story. freakout by server people because of drop in load with CSS implementation. y’know, we’ve done this so gradually, and without ever really having done a big-ass table design, that I can never show those kinds of numbers. sigh.

a journey not a destination, not a quick fix, but lots of benefits.

tells how he ended up writing the story for ALA. “I thought you were kidding.” and getting slashdotted. 🙂

recommends Meyer’s definitive guide to CSS, talks about speaking with Eric. more books, Zeldman, More EM on CSS.

he has 12 minutes, so he’s going to…demo the FIR technique. I mentioned the negative margin technique. (Dave Shea has a whole page full of techniques.)

demo also of a student project, another rework, playing with firefox web dev extension. (which rocks my world)

nap

instead of going to session #10, I went up to my room to get a nap. best thing I could’ve done, even though some of the presentations sounded quite interesting. now I feel like a real live human being again, even with just an hour’s sleep, washing my face, and putting up my hair.

I think I even figured out a design for the IT Kitchen wiki while I was dozing; when I woke up, I had a very clear image of what I want. now I just need to see if I can actually do it.

cms 9: content mgt best practices

asking who’s using a CMS, satisfaction.

wacky graphics showing a messed up navigation system.

slide with teeny tiny font. she’s lost her microphone, and she’s not not quite loud enough. hey, she’s asking and now holding the mic…I can hear her!

what it can’t do: write the content (sounds silly, but…. ah, it sounds like our issues with the workforce dev people.), convince reluctant content providers to use the software, set up a workflow/process, stop mission/scope-creep. or do anything about web site governance.

content is the weak link, either missing or duplicative. or just bad writing. providers who don’t know what the hell they’re doing or are too busy. knows just enough to be dangerous. turnover problems. (the longer I work in this biz, the more I see problems as being social rather than technological.)

treat it like a publication, but expected that it’s *always* up to date.

in a perfect world, you’d have writer-editors.

q: but I missed it…oh, who decides on the info arch? (she called it a “no-brainer” but it’s not when you’re trying to develop it…what she meant is that it’s a nobrainer that you need one, but not to create.) should be created by a team. (gah. committees!)

her freaking slides have too small text and she talks too fast.

give web projects equal priority & budget with print.

design should take back seat to content, standards, accessibility.

“dynamic running calendar” — our calendar is crufty and weird, but it does work for that, at least.

she keeps coming back to that one point: keep content managers focused on content not design. but HOW? also suggests outsourcing programming project “black holes” — odd.

mentions the Krug book. that’s definitely the classic of the genre.

I wish I’d gone to take a nap instead of this, esp since my hands are just tweaking out.

asked if people had web governance, and I don’t know what she means by that term. I think there was a question about governance committees with people who don’t know anything…you’re doooooomed.

switched to a guy; dude he has a loud voice.

Veen quote; but of course. this is all part of the CMS meme of the day.

they have a home-grown CMS.

cmswatch, which I haven’t followed in a while.

he’s going to be covering requirements definition. again with the tiny font, reading his damn slides. nothing annoys me more.

don’t start by researching features of exisitng products. interview users/stakeholders, once you know who they are.

6-9 months from starting analysis to selecting a product, if you build your own, give 20%-40% of dev time to analysis.

I’ve been warping off from the presentation…boring boring boring. Victoria, Aus., cms requirements definition report/tool, tho, that might be worth looking into.

there’s a lot of info on their site, but the presentation isn’t all that engaging. or maybe I’m just too brain-dead.

susan mentions a book called “software requirements”

a little fresh air

I’m sitting out on the patio in the middle of the hotel, and yes, the wifi reaches out here. the laptop is a little hard to read, but it’s worth it just to get some sun & fresh air.

Susan & I went for a quick walk around the hotel during one of the breaks earlier today, and I realized it was the first time I’d been outside since I got here Sunday evening.

I hear of other people skipping stuff to nap or whatever, but I just don’t want to miss anything, even though my brain is totally melting. I told someone at lunch that I was just madly taking notes in the hope that I’d remember and learn something later. hey, it worked for webvisions, right?

(oh, quicktags turned back on when I re-enabled javascript. fascinating.)