Hi all:
Asking around in IRC as well, but here's the deal:
I started a role on a large, big-budget, high profile social networking project here in NYC. I'm making the case for Drupal, they want to decide today. Some code is already built from the ground up, but the case for Drupal is still valid as much of that code can be brought over, plus Drupal will handle so much else that would otherwise need to be built from the ground up.
This project is more complex than a lot of Drupal sites. Some big questions:
One issue is node relationships. This project has a lot of nesting, i.e. a parent content type has a bunch of children to be nested in that node (page), while each of those children is its own node as well. We need to be able to pull all the children (associations) at many different points. Different assets (pieces of content) are associated with different users and parent items, and we need to pull these associations at different points. Put simply, there might be a "main project", with multiple users applying to be in the project in some way, and they'd bring certain "assets", or pieces of content (say, the promotional poster) -- so we need to be able to pull the users on the project and the assets they've submitted to the project and more.
Anyone here used Node Family or considering it for big projects? Other relationship modules to consider?
Anyone here know of some real complex Drupal sites that utilize relationships or have a more complicated structure/hierarchy? I don't believe that mtv.co.uk (Lullabot) did this kind of stuff, but maybe someone here knows.