Slowing Down on Posts

This semester, my posting frequency will likely be less frequent than previous semesters due to two new responsibilities.

One responsibility is overseeing the establishing of a website that will support writing across the curriculum at Kean University. (At least we have someone, Alex Taner, on board who will design the website and its architecture and is a professional in this area.) Initially, we'll have a skeleton of writing concepts linked to other sites that already have the content for those ideas. Next fall, we'll begin working on our own content to fit our particular students' needs, and a year from now, we'll start working with other departments to integrate their writing needs into the site, so it will truly be "Writing @ Kean" instead of only writing in the English Department.

My other responsibility is related to our English Department becoming a National Writing Project site: I've been appointed the technology liaison--not because I know a lot, but my meager knowledge is more than most others (and others have their own strengths that lead them to other positions). That means I have to set up a website for us, become acquainted with our Summer Institute's technology expectations, and figure out how to help our participants and collaborators become more proficient in using technology in their classes. (I need to figure that out for myself, too, so I'll be hitting two birds with one stone.)

So much to consider, too. Do we want a blog hosted on Blogger or Wordpress, or our own blog installed on our own domain? Do we want static pages or dynamic ones controlled by a CMS? Do we want a commercial CMS like ExpressionEngine that provides support (and costs money) or an open-source CMS like Drupal, which has a community but a steep learning curve. The former items in those sentences are easy to accomplish, while the latter will require much learning on my part. I like learning, but sometimes there's just not enough time to do everything you want and keep up with your other responsibilities. Of course, we can take the easy path now and later move on the more powerful and flexible tools. What problems will that create?