Hi Richard! Thank you for you input. I think your approach sounds very similar to what I think ours will be when we are done. We feel that we want to make use of the "STK" way and such great things as the DAM support and imaging but the templates and paragraphs will be made from scratch to fit our specific needs.
Regarding the JSP vs. Freemarker discussion we are discussing and investigating and might actually make a try with Freemarker to see how it treats us :). Regards, Tomas. ________________________________________ From: [email protected] [[email protected]] On Behalf Of Unger, Richard [[email protected]] Sent: Monday, March 21, 2011 10:42 AM To: Magnolia User-List Subject: AW: [magnolia-user] Setting up a site in Magnolia and usage of STK Hi Tomas! We're setting up an Enterprise sized installation of Magnolia for our customer. We decided to follow a "hybrid" approach: * Our template and template-model classes inherit from STK base models, we use DAM and imaging * We use the ETK multi-site and site definitions, template definitions and template prototype * We don't directly use any of the STK templates or paragraphs * We extend the base template, template-model, site and template-availability classes with some custom functionality We chose this path because: * In this way, we feel we have all the power and flexibility of STK, but hope to avoid problems with upgrades (changes in the templates impacting our sites). * Our customer's templates only approximately match the STK concepts - we found it easier to define our own templates and paragraphs, to more directly match the customer's needs. In particular, the STK does not suit us directly in the following areas: * the template availability concept * the "Singleton-Paragraph" generation * the Navigation In terms of freemarker vs. JSP, I would strongly recommend freemarker - being able to edit the templates inline (or even better, via Webdav) is a very compelling feature. Regards from Vienna, Richard -----Ursprüngliche Nachricht----- Von: [email protected] [mailto:[email protected]] Im Auftrag von [email protected] Gesendet: Donnerstag, 17. März 2011 14:58 An: [email protected] Betreff: RE: [magnolia-user] Setting up a site in Magnolia and usage of STK At this point JSP is our first choice because it is already being used while Freemarker is not. Although if it somehow came to our knowledge that we would greatly benefit by using Freemarker that could possibly change in the future. Do you have any thoughts on that? E.g. how is performance in Magnolia for JSP vs. Freemarker? ________________________________________ From: [email protected] [[email protected]] On Behalf Of Jan Haderka [[email protected]] Sent: Thursday, March 17, 2011 2:15 PM To: Magnolia User-List Subject: Re: [magnolia-user] Setting up a site in Magnolia and usage of STK On Mar 17, 2011, at 1:27 PM, <[email protected]> <[email protected]> wrote: > make of it. One issue though is that we most likely won't use Freemarker > making the pre-made templates unusable for us. Just curious, is it the corporate policy that forbids the Freemarker and forces JSP or do you have other reasons to not wanting to use it? BTW, Magnolia templates can be mixed, you can have some templates using Freemarker and others using JSPs, you can even have both types of the paragraphs on the same page. The decision to use one or the other templating language doesn't need to be site wide. At least not from the technical point, although I could understand if you don't want to have developers having to know both. HTH, Jan ---------------------------------------------------------------- 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]> ---------------------------------------------------------------- ---------------------------------------------------------------- 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]> ----------------------------------------------------------------
