Don't really know what my definition of correct is in this case. Thats is also the main reason why I asked you guys.
I mainly want to get a feel for what other users/developers of Magnolia thinks about how a web site is to be setup in a good way. Reading your reply I get the feeling we should give the STK a try and see what we can make of it. One issue though is that we most likely won't use Freemarker making the pre-made templates unusable for us. Regards, Tomas ________________________________________ From: [email protected] [[email protected]] On Behalf Of Nils Breunese [[email protected]] Sent: Thursday, March 17, 2011 12:08 PM To: Magnolia User-List Subject: Re: [magnolia-user] Setting up a site in Magnolia and usage of STK Tomas wrote: > 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. That all depends on your definition of 'correct'. We are running a pretty large Magnolia EE installation with already a couple dozen of sites, some containing tens of thousands of pages. We were skeptical about the STK at first, but we decided to try to use it as much as possible and haven't regretted doing this. We use the STK paragraphs we like, we sometimes extend STK classes to extend functionality and sometimes add custom paragraph and template models from scratch. Magnolia is pretty flexible in this regard and I wouldn't know why you wouldn't want to use all that's already there. Nils Breunese. ------------------------------------------------------------------------ VPRO www.vpro.nl ------------------------------------------------------------------------ ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ---------------------------------------------------------------- ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
