Hi! We are in the process of evaluating Magnolia and are trying to figure out how to setup a web site in a good way that suits us and at the same time fits and utilizes Magnolia to its fullest. Currently I am in process of sorting out whether the STK is something for us or not.
One issue that I am struggling a bit with is that to what extent we can and want to use the STK. Some parts of the STK seems highly usable for where others will probably not be for us. So in a case where we want to be able to utilize parts of the STK such as the DAM support (e.g.. stk.getAsset), but probably won't use any the existing paragraphs, dialogs or templates but rather define and setup all this our selves. Is the "STK-way" of setting up the site with its definition and configuration an approach which will benefit us rather than going the more manual non-STK way? I guess what I am looking for is the "correct" way to setup and configure Magnolia sites at an enterprise level. Any input is welcome. Regards, Tomas ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
