If you plan to make a sophisticated site I recommend to use FreeMarker - you can read the sources of the STK and modules (they are written in freemarker) and benefit from them more easily - separate the template script and template logic (model), hence you can create variations of you paragraph (or vary one of ours) - you can render such paragraphs and templates without having a request/response (one of the main driver for our decision) -- isolated caching, indexing -- rendering while workflow is executed -- storing templates (and snippets) in the repository
The switch is rather easy if you follow this document: - http://documentation.magnolia-cms.com/reference/templating/freemarker.html note: freemarker is a bit like velocity++, the rest is Java ;-) Cheers - Philipp On 17.03.2011, at 14:57, <[email protected]> <[email protected]> wrote: > > 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]> ----------------------------------------------------------------
