I have kicked off a couple of projects recently on D7 and am loving working with it over D6.
Admin UI is a big plus (hugely improved due to the great work on d7ux[1]) but for developers there are lots of under-the-hood improvements as well. Module-wise, yes I've hit a number of modules for D6 which hadn't been released or aren't prime-time ready for D7 yet. A good opportunity to help get some of them ported (I'll admit a minor addiction to that sort of thing) and also a great indicator of which modules are the ones you *want* to be using. So - my advice would be to try D7 initially for your project, then fall back to D6 if you find some killer feature which D6 has and D7 doesn't (and you can't, or won't, contribute to getting that feature into D7). This helps you (in a year's time you're more likely to be running the current Drupal version) and it helps the community you're pitching your lot in with, which in turn helps ... you! [1] http://www.d7ux.org/ On Feb 21, 11:51 am, Paul Bennett <[email protected]> wrote: > Hi Warwick, > > I'm not familiar with the intricacies between D6 and D7, but I did note that > a (long overdue) admin UI rewrite is / was a big part of the version release. > > Part of the beauty of Drupal is the massive dev community and Drupal's > modular structure. You'll literally find a module for anything except real > custom / edge case requirements - even then using hooks it's simple to > override module functions to get the functionality you need. > > I'd stick with 6 for now - there is a dev jump in terms of API changes > between version releases but I know that tools (and modules!) have been > created to ease the pain and automate module conversion. > > Regards, > Paul -- NZ PHP Users Group: http://groups.google.com/group/nzphpug To post, send email to [email protected] To unsubscribe, send email to [email protected]
