Hi Tomas,
> I guess what I am looking for is the "correct" way to setup and configure > Magnolia sites at an enterprise level. i checked your problem a while ago. You can go the whole way and even incorporate the structures of the ftl templating and the predefined 'areas' in your templating project. You also can do this in part. I am sure this is not feasible for any website project, if you start from a finished html prototype or intend a technical migration from one cms to another, it is even unlikely. You can also mitigate the reuse of the stk structures, skip the stk ftl and limit the usage of the stk to the def and model classes and only some features of them, but then you are also bound e.g. to use site definition classes, that is the whole convenient stuff to configure your templating and your sites. In both cases imo you have to respect the license, i.e. render the badge on any page. You also have the option to draw on the stk as a best practice demonstration without reusage. I view the stk as a feasible and approved way to use magnolias possibilities - read the code anyway, and maybe find even better concepts with that insight. If you plan to use magnolia more often, you may want to come up with your own 'tk'. Regards j ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
