I need to create a custom entry page for my DNN install.  Part of the entry page is a random image.  Currently the random image is pulled out of an array of images, selected randomly by javascript.  Currently the array is statically specified and I go into the module to change the images based on the season.  Awful, I know, but I lifted the code out of our current website.

I'm reworking the entry page to be a C# module and, what I would like to do, is have the user specify a base directory.  Once the user specifies the base directory, the module will then grab the next level of folders and allow them to set dates for when the images in that folder will display.  The server will then select the random image - rather than using javascript.

It occurs to me that this would be more flexible as a skin object, allowing me to use CSS to place it anywhere on the page - using XML to specify the dates and folders.  This would make it far less configurable for the end user (everyone who is not me), but far more flexible for the designer (hey, that's me, for another year or so).

On the other hand, though, while there's a 92% chance that I'll be the one specifying the base folder and dates, my goal is to get somebody to take on that responsibility.  If other people get used to doing this, it's one less thing I'll have to do.  In addition, the random image is only one part of the entry page.  So, since I'll be doing other programatic items on the entry page, it may make very little sense to split it off into a skin object.

Right now, I'm leaning strongly toward a monolithic (single use) module for the entry page.

Thoughts?