CMS and Shopping Carts? (from the view of a web developer)
SwellJoe: I've been through the CMS selection process five times now, and it's always turned out bad, until the most recent selection.  I've heavily used (as in, built and launched a site used by thousands of people every day) Zope, Plone, OpenACS, Joomla, and now Drupal, and experimented with (as in, installed and tinkered with for a few days just to get a feel for) a half dozen others.  I think Drupal is actually going to work for us for years to come; while every other CMS I've ever launched a site on has immediately shown itself to be really problematic once it was being used by a lot of people.  It is the least frustrating, the best supported by its community, the most actively developed by competent developers (Joomla seems to have a lot more third party developers, but they seem to predominantly be web designers turned developer, and their inexperience shows in the extremely poor quality of most modules for Joomla).  We've had it in service for a couple of months now, and I spent a lot more time evaluating and developing for it before choosing it than any other CMS I've deployed, and its flaws are the least offensive and the easiest to fix or workaround of any of the ones I've used, so far.Ubercart is the nicest to customize and extend of any of the CMS shopping carts I've used, and also seems to be developed and maintained by competent, friendly people.Getting commercial support for the code from competent core developers has also proven much easier than for any of the other CMS I've used (with the possible exception of Zope/Plone; the Zope people are top-notch and fantastic to work with, though not cheap, and I found I needed help a lot more than I liked because the docs were out of date and inaccurate and they've reinvented every wheel so existing knowledge, like of relational databases, doesn't map to Zope/Plone).Anyway, our new site is also the hardest working of any CMS-based site I've ever built.  It is expected to do more: forums, ticket tracker, ecommerce with quite a lot of customization for license management, documentation, extensive and heavily used email notifications (we send thousands of notification emails every single day, and while it's not perfect, Drupal is the most flexible and generic of all of the notification systems I've used).It's probably worth mentioning that I don't like PHP as a language (I would choose Perl, Python, Ruby, or pretty much anything else, over PHP, if I were only selecting based on the implementation language).  Despite that, Drupal is what I selected.  I guess that's a pretty ringing endorsement.I'm not even going to try to tell you what to do on question 2.