Hi there, Well, to add a bit more context, yes that's exactly how the data module used to work. We actually migrate former data types to content apps since magnolia 5.2, although the default company app is not visible by default for fresh installs (data module is deprecated in 5 after all).
As a side note, you may notice it involves quite some boilerplate configuration to control actionbar appearance based on these several node-types, and to create detail subapps for each type (+ a routing default editAction to forward to the right detail subapp). Alternatively you could probably manage these types in different apps or browser subapps in a more 'relational' way. This would probably be a bit more simple but in the end it's your call. :) Cheers, Mika -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=3f8c91a2-d32b-4682-9d48-5cf5d658249d ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
