I have nothing against Drupal but everything we need to do here is going have to be written from scratch anyway. It doesn't need to be pretty or have ay traditional features like galleries, fancy menus, etc. were just drawing a simple page. I guess I don't see the benefit of using druple or something similar in this situation. - Tom On Fri, Sep 12, 2008 at 1:15 AM, Jeremy <tclug at lizakowski.com> wrote: >> As for some of the other responses, I don't think Drupal is the right >> tool for anything other than eating up CPU cycles and bandwidth. There > > Drupal is awesome, if your site will look and function like a Drupal site. > Things like forums, image galleries, etc, are pretty much automatically > available with no coding. > > But, if you stray too far from what they do, and if you want it to look > certain ways, then you start to fight the framework. If you know Drupal > well, you can make it work, but then you're interfacing with code you didn't > write. If you're new, it might hurt. > > That's true for any framework. I do a lot of Ruby on Rails. It makes custom > web development easy, if you do it their way. And their way is slick. But > if you decided you didn't want a database-driven MVC webapp, rails might just > get in the way. -- Tom Penney