8
Granted -- for a single site it's trivial. But I'm considering XOOPS as a tool for maintaining (potentially) many sites.
Don't get me wrong -- I love what I'm seeing so far (I've spent the better part of the past week tinkering with PostNuke, and before that others, and XOOPS is the most intuitive by a good margin). A good OS CMS like XOOPS can be an awesomely empowering tool for organizations on a tight budget, and everything that can be pulled away from code tweaks is a plus.
Sorry -- I'm starting to make a mountain out of a molehill here. Didn't mean to get off on a rant. Time for me to shut up.