I have a few pre-sales questions about the flexibility of the database and how the notion of members and member groups work.
Here is a my scenario, I will use a an analogy most everyone can grok rather than go into gory details of how our particular organizations/membership needs to work. Think of a local Little League organization. There are multiple teams. Every kid is a team member, but the site sections are broken up into different teams, and of course one kid can’t be part of more than one team, but they are part of both a team and Little League as a whole.
Can EE and the current multiple user/member groups concepts facilitate this or will we need to customize? If so how much?
Also, you can imagine how each team would have different calendars, email subscriptions, information that is private to that team. Like a mini-site within the über-site. Does EE manage this kind of concept and if not has anyone modified the base to do something like this?
Also, ideally there could be resources like say baseball fields, batting cages, shared gear, etc. that needs to be accessible and scheduled or allocated across all the teams. I doubt it, but are there add-on modules or some ways to work with resources in this way?
Finally, how does CodeIgnitor fit into all of this? I came across CI first and love it. I want to build the site using CI, then I saw that you guys do EE as well. EE may not be an exact match but, I would like customization to be as easy as using CI. Can someone speak to that a little too.
Sorry for the tome, just thought I would get it all out and see what people say.
Cheers