Earlier quoted context omitted.
"I just finished building a Drupal system that stores content until a user with a particular email address logs into a site, then shows it to them." Interesting -- public code? "like so many Drupal problems, this will require some custom code" Yep -- that's what I mean, it's an itch to scratch, not a tool I can deploy today. I wish I could deploy such a tool; it would be useful w/ my graduate work, which involves lot…
your comment gives me some hope that if I were to try to implement this with Drupal, I wouldn't end up in a stinking morass. Oh, no, Drupal pregenerates the stinking morass for you. ;) Well, it's not really as bad as that. But the person in this thread who pointed out that Drupal development is the art of compromise was on the money. And the learning curve for Drupal 5 can be rather like scaling a sheer cliff. It all…
But, the 'stinking morass' thing gets to me -- maybe better to start closer to scratch w/ e.g. Rails or Django? Why did you decide to go the 'customize Drupal' route?
(for my own notekeeping: brought this idea up again, here: http://news.ycombinator.com/item?id=466673)