Web 2.0 tools have changed the boundary lines between techies and program staff in many nonprofits over the past few years. At least, they should have, though I know of various organizations that haven't made the conceptual leap to the new roles.
OLD SCHOOL: Webmaster
Let me explain by talking about my own changing work role. Even a few years ago, I was a paid
staff webmaster. You could divide my work into two large categories. The first was techie: I managed
server accounts, set up required
databases, designed sites. I got into the
HTML code, the
PHP, the
Javascript,
CSS, etc.
The other was content: when program-oriented staff had new material they wanted on the website they would email it to me or walk it over. I would put in my work queue, where it might sit for weeks if it wasn't an organizational priority. When it came time to add the material I would boot up
Dreamweaver, a relatively expensive program that was only accessible from my laptop and I would put the material onto the website. Needless to say, with a process like this some parts of the website never got very much attention.
At some point I start sneaking in a content management system for frequently-changed pages. This seemed very hackish and not good at first but over time I realized it greatly speeded up my turn-around time for basic text content. But the organizations I worked for still relied on the old model, where staff give the webmaster content to put up.
NEW SCHOOL: Web Developer
Nowadays I'm a web developer, a freelancer with an ever changing list of clients. I typically spend about a month putting together a site based on a content management (like this) or automatic feed system (like I did for Philadelphia's William Penn Charter School). I do a certain amount of training and while I might add a little content for testing purposes, I step back at the end of the process to let the client put the material up themselves. I'm available for questions but I'm surprised about how rarely I'm called.
Here's two examples.
Steadyfootsteps is a blog by an American
physical therapist in
Vietnam. When we started, she didn't even have a digital camera! I gave her advice on cameras, started her on a
Flickr account, set up a fairly generic
Movable Type blog with some custom design elements and answered all the questions she had along the way. She went to town. She's put tons of pictures and embedded Youtube videos right in posts. Here's a non-techie who has contributed a lot to the web's content!
Penn Charter is a school that was already on Flickr and
Youtube but wanted to display the content on their website in an attractive way. I pulled together all the magic of feeds and javascripts to have a media page that showcases the newest material.
They're very different sites, but in neither instance does the client contact me to add content. They rely on easy-to-use Web 2.0 services: no specialized HTML knowledge required.
NEW TOOLS, OLD MODEL
I got an email not so long ago from an old boss who manages a monthly magazine. Her site has been radically rebuilt over the years. Dreamweaver is out and
content management is in. They use
Drupal, which my friend Thomas T. of the
Philadelphia Cultural Alliance tells me won the
recent popularity contest among nonprofit techies. This is great, a definite step forward, but what confused me is that my old boss was asking me whether I would be interested in returning to my old job (the successor who oversaw the Drupal upgrade is leaving).
They still have a webmaster? They still want to funnel website material through a single person? Every staffperson there is adept at computers. If a physical therapist can figure out Flickr and Movable Type and Youtube, why can't professional print designers and editors?
My hourly rate ranges from two to five times what she'd be likely to pay, so I turned her down. But I did ask why she wanted a webmaster. Now that they're on Drupal it seems to me that they'd be better off switching from the webmaster to the web developer staffing model: hire me as a freelance consultant to do troubleshooting, staff training and the occassional special project but have the regular fulltime staff do the bulk of the content management. I'd think you'd end up with a site that's more lively and updated and that the cost would about the same, despite my higher hourly rates.
I've heard enough stories of places where secretaries have come out of the shadows to embrace content management and have helped transform websites. I'm the son of a former secretary so I know that they're often the smartest employees at any firm (if you walk into an office looking for the expert on advanced
Excel features you'll surely find them sitting right there behind the receptionist desk).
FINALLY: WHAT'S UP WITH DRUPAL?
I'm trying to join the bandwagon and use Drupal for a upcoming site that will have about a dozen editors. But there's no built-in
WYSIWYG editor, no little formatting icons. Sure, I myself could easily hand-code the HTML and make it look nice. But I don't want to do that. And it's unrealistic to think I'm going to teach a dozen overworked secretaries how to write in HTML. The interface needs to work more or less like
Microsoft Word (as it does in Movable Type,
CushyCMS,
Google Docs, etc.)
Most Drupal sites I see seems from the outside like they're still old school: staff webmaster through whom most content funnels. Is this right? Because if so, this is really just an institutionalization of the content hack I did six years ago. Can anyone point me to lively, active Drupal sites whose content is being directly added by non-techie office staff? If so, how is it set up?
The Tract Association is venerable Quaker publisher dating back to the early part of the Nineteenth Century. They had a website but wanted a new one built with a content management system that would allow for easier editing. The new site is built in WordPress. Befitting the organization's ethos, the site is relatively plain but there's a lot going on underneath the surface.
When a user of the Google Toolbar visits a page with Sidewiki notes they see a small blue button of the left side of the page with two white chevrons (see screenshot on the right). Clicking on this opens the Sidewiki sidebar. Here they will see comments left by previous visitors. They are be able to add their own comments. 
A potential client recently came to me with an existing site. It certainly was slick: the homepage featured a 
