Like many ProfHackers, I’m constantly tinkering with my syllabi and assignments, looking to improve the experience for the students (and for myself). For many of my writing assignments, this tinkering has meant that the guidelines have grown longer and longer (as I address specific issues that have come up in previous iterations). However, in my senior undergraduate seminar, Adventures in Digital History, I’ve taken the opposite approach, giving students the broadest of guidelines and providing them with the opportunity to create their own assignments for their group digital history projects.
[A note about the course [2008 and 2010 iterations] and my goals for it: it is focused on digital history concepts and methods, and explicitly offers an alternative to the semester-long research paper that allows students to create something fun, interesting, lasting, and important,...

[Editor's Note: Although this is a
post by ProfHacker author Jeffrey McClurken, we would like to
acknowledge the assistance of super friends-of-ProfHacker
As with the two previous posts in this series
(
The department website, standardized
across an institution, has become a common feature of the digital
landscape of higher education. Although it is possible to create
something useful with a great deal of work, passionate advocates,
and skilled people, in most cases the static, limited department
site, often with a single gatekeeper or two, restricted formatting
options, and limited multimedia usage doesn't do a good job of
meeting the main goals of a department site.
The Problem: I schedule at least five
office hours per week. [I'm there a LOT more, but these are
scheduled hours, the same from week to week throughout a given
semester, when people can more or less count on me to be
there.]






