Cheers both.

The one thing I'd want to preserve is a single log-in across the site. I'm not really keen on using forks, which I think vbdrupal is? There are others like Drupaltin but I'm not sure how 'good' they are in terms of how efficient they work together.

The good thing about vB is I know we can style it to pretty much how I like - and I really see it as a base for a custom back end system. Drupal is more a 'cms' where it's easier to add new sections etc from an end users perspective (eg easier for an office admin to maintain and update the site content and new content sections).

Other things I want to keep is a standard Pm system throughout the site, all comments added to post counts, one userCp system etc etc - which can only really happen if vB is the base I guess.

The other factor is it'll prob take me a while to get my head around Drupal, so could add a few months to development time. Also, with Drupal I think you need to know more php to get even simple things like the styling done. Finally, I'm still concerned about how efficient it will be, I keep hearing people saying it's not good for logged in users - and my site is going to be very community orientated with almost every page commentable.

I guess if the site takes off I could always employ someone to port the content and comments into drupal?

__________________
PS3 Forums on GameSlurp - the site for gaming fans!