Plaidophile

So, I've had an idea for a site pinging around in my head for a while, and I'd like to program it up, but I'm being a virtuous (i.e. lazy) programmer about it, and I was wondering if anyone had any recommendations for things that would make my life easier.

What I'm looking for is EITHER: an extensible CMS which allows for custom per-item fields and queries on those fields and has some sort of moderation queue functionality, OR: a web services authentication framework which makes it easy to support multiple login schemes (local account, OpenID, OAuth, Facebook, etc.). The extensible CMS would of course have to include something like the second bit too.

Drupal is kinda-sorta on the right track as a CMS (and it at least has modules to provide lots of the things I want to do), but it seems to really want things to all behave like a Drupal site, and I don't really have the patience to learn how to wrangle yet another CMS right now. All the other community-oriented CMSes I know of (Movable Type, WordPress, Slash, Scoop) are basically just rigidly-structured glorified blog engines. Obviously, MT and WP are both pretty flexible if you want to spend a lot of time on it, but it'll never be convenient to provide custom data fields and queries thereof.

Auth frameworks are in an even sorrier state; I've seen very task-specific ones like TypeKey and Disqus which seem fine for posting comments, but not so much for anything else. But in this day and age there seems to be absolutely no excuse to make a site that requires Yet Another user account, but there's so many different protocols each with their own weird security implications to worry about and it seems like there should just be a bunch of libraries that aggregate all that functionality and just provides a few API calls like "give me the data of the currently-logged-in user" and "provide a login form" and whatever.

I guess I could just start out by making a database schema for the main item stuff and then growing my own CMS from there. What I have in mind isn't too complicated from a data standpoint, at least. I just don't want to have to deal with crap like user wrangling and data sanitizing and so on. (At least there's plenty of libraries for HTML sanitization now.)