The purpose of this post is to elicit community feedback on the technological future of EphBlog. I have strong opinions about our future content, but limited experience for judging good technology, beyond a bias for open source solutions. Our current plan is to abandon Movable Type (our current blogging platform) and move to Wordpress (the leading open source blogging tool). In fact, genius EphBlog technologist Eric Smith ‘99 and I had breakfast last week and discussed these and other issues. Eric, because he takes the running of his business seriously, does not have endless time to spend on EphBlog. So, we had tentatively decided to give me (and my interns) admin authority over the new site. This allows me and my posse to do stuff for ourselves. The problem is that we may not have the skills required.
Ken Thomas ‘93 comments:
I may be a little bit late in the game here, but I’d strongly recommend Drupal over WordPress as it *can* do the former and so much more– before user-custom views, I’d suggest simply having different sections such as Tech and Sports and Politics, surrounding a main page with more general “front page” content. In fact I might even *volunteer* to do it, or…
If nominated, I would volunteer to create and host ‘88 and ‘93 websites prior to reunion, based on Drupal, on the presumption that it would work toward an alumni-driven, online alumni COI purpose.
Be careful what you volunteer for, Ken! Is Drupal the correct solution? Comments are welcome.
In terms of requirements, the key issues are:
1) We need to have a notion of “views”. A member of the class of 1988 needs to be able to bookmark a page that provides updates on just 1988 related posts and content. That page should have the standard EphBlog templates. Similarly, someone interested in just EphCOI:Finance related posts should be able to bookmark a page just for that. And the same for other views. There also needs to be one main view which aggregates everything.
2) We need the administrative hassle of adding new bloggers (or whate is the term for people who use Drupal? Drupalers?) to be simple. It sure would be nice to have other delivery methods like daily e-mails. How about a better comment system? I am giving serious thought to using the code from Slashdot, but wouldn’t that be a bother? Does that or something like it integrate with Drupal? Are there working examples we can check out?
3) Integration with other tools. It is just about time to move Willipedia over to alumni control. Current students are barely using it. I could imagine reunion alumni having a lot of fun with a well-run Wiki. Imagine one with a page for memories from each entry. How well do Drupal and Wiki software play with each other. 2008 may also be the year that I cajole some students into draining the Williams advising swamp once and for all.
4) We need a better, more automatic way of managing our Eph Blogroll, as well better integration with the Planet software we use for Eph Planet. Or does Drupal do all of that?
5) Our Eph News service is beyond pathetic. Here are my previous thoughts on the topic. Will Drupal make this easier to manage?
And so on. Two questions: First, what should our main platform be, given these goals? Second, is anyone willing to volunteer to be our technological lead, the person behind the scenes who makes EphBlog function? (I want Ken to have a chance to reflect a bit before he volunteers for this.) I will provide the content (mainly by recruiting the contributors) if you maintain the platform.
EphBlog turns 5 in January. Who wants to help take us to the next level?