I've spent the past few weeks properly researching which systems to use for the frontend (www). A few CMS systems was tested, especially Joomla! and Drupal enjoyed special attention. At the moment I'm not overly impressed with the CMS systems out there. Sometimes "boxed" systems aren't always the best of choices, especially if what you want isn't what the systems can offer. The SAGD 2010 frontend will be much simplified, more "dashboard"-like and with that in mind using a CMS like Joomla! or Drupal might be a tad overkill.
I won't make a secret of it... I'm not a huge fan of PHP, but I will say that there are systems out there built on PHP that are impressive. With the new SAGD 2010 design we will be making around 85% use of OSS. At the moment we are building the new SAGD 2010 frontend as a ASP.NET 4.0 web application. We are also busy configuring another OSS system that will be taking over quite a lot of typical SAGD frontend features, but that system will only be launched once the new SAGD 2010 frontend goes live within the next month.
The main driver for the process I've started during November 2009 up until now is NOT to build the new SAGD 2010 design from the ground up (unless theres no alternative), but rather leverage OSS systems where possible. One thing I'm slightly careful of is relying too much on too many OSS systems as it might end up becoming an updating nightmare. I would like to spend less time maintaining gamedev support systems, and rather focus on USING those gamedev support systems to help me (and my company) achieve our game development objectives. If the new SAGD 2010 design/structure works for us, it should work well for everyone.
I'm quite excited and theres exciting times ahead building our Unreal Engine 3 project once I got the SAGD upgrade behind me!

"There are two types of people in this world that will hate you. The envious and the stupid." - The Libertine.