JoshTango

Ok lets rename namespace to subdomain because thats what this is really about: Domain Driven Design.

Actually lets just stick with PACKAGE as the field name. There is no need to show the entire heirarcy in the Admin UI. Just one level for the package name...

I guess I can settle for category now. @sebastienros In the future I would like a discussion on domain types.

I also wanted this and found your post while searching.

Drupal Views is your version of Lists. I think you should keep Lists as a query and not allow one by one selection. This is only if you do create...

ok

I think I read that you are storing an array of Id's if they choose multiple content items. This is maybe fine for the implementation if you do it for...

Well it would depend on where you accessed it. In a template typically it would be Color[I].value if it were in a loop to display. If you defined the template...

Also if someone switches back to 1 field only after having chosen multiple you should display a warning on the UI explaining the data will be lost. This is assuming...

Here is another perspective. We are thinking inside the box rather than outside the box. If this was a normal .Net project we would have object and List. So ContentType...