File this under Things I Might Do: I might knock together a new blog page to my own specs using the DNN XML/XSL module.

Sure, I could easily install one of the tried & true open source solutions. WordPress deserves its fine reputation, based on prior experience, and it would give me all the functions I'd want. (In particular, I want the ability to apply subject tags, which this DNN module for some reason does not do -- a nearly incomprehensible blind spot.) But WP would also force me to manage a separate site under a completely different technology platform, including monkeying with the theme and futzing with lots of admin (because we know, giving the operating parameters of my brain, such as they are, that OOB just ain't gonna cut it). WP would, however, give me a place to start building a portfolio for school, which I need to be starting like *right now* and separating off the school/information professional stuff from this stream o'  semiconsciousness is a major driver of the idea.

Now the XML/XSL solution would be a bit of a technical challenge. Yes, I know that 'a bit' is likely an understatement. Shut up. But I could do it, and it would be an interesting challenge. Maybe I could get credit for the project in my XML class for the current quarter. And maybe it would constitute a pretty kick-ass portfolio piece in its own right. I gotcher XML right here, yo! The biggest downside I see (now, anyway -- ask me again when I'm up to my ears in the stoopid project) is that I'd somehow have to draft or transfer entries into XML to update the data file.

I'm fairly sure I could build the XSL transform to get the entries into the format I'd want. I could even start to accommodate that portfolio function (or add it at some point). And it'd be staying in one technology platform, still with its own URL and page skin. Gonna give this one some more thought.