Just to clarify the licensing once more: the Standard Templating Kit is not only templates, it is the best practice framework to build templates. If you use it with your own templates, you still need to display the badge. If you don't like to support our work in this minor way, either don't use the STK at all (do not install any of it, don't copy any bit of template code etc.) or get an Enterprise license (and support further Magnolia development for real).
Thanks - Boris On Jul 22, 2010, at 6:01 PM, Alex Cougarman wrote: > > Thank you, Ruben and Gregory. It's becoming clearer now! A few follow-up > questions/thoughts; please correct me: > > - It's only when we use the built-in templates that we have to show the > Magnolia logo. > - We can use the STK to build our own templates; we can use the Freemarker > technique and don't have to worry about the file system. > - These custom templates don't have to show the Magnolia logo. > - If we use JSP, we do have to worry about the file system and it becomes > trickier. > - If going the STK/custom template route, we create the templates in the > "Templating Kit" > Templates area of the AdminCentral online tool, outside > of the default "templating-kit" folder, maybe in its own "unctv" folder. > > I think for our needs, the Freemarker method is the way to go; we don't > have to worry about file permissions on the file system, etc. It can be > easily done via the web by anyone -- the person doesn't have to know JSP. > > But where do we put the CSS files, images, video files, JavaScript library > files that are then used by that custom template? I don't see any of those > under the default "templating-kit" folder. > > P.S. Thanks for continuing to help me understand this system :) > > > Sincerely, > Alex Cougarman > > UNC-TV > Web Applications Developer > 919-549-7823 > > ---------------------------------- > “I believe that unarmed truth and unconditional love will have the final > word in reality. This is why right, temporarily defeated, is stronger than > evil triumphant.” -- Dr. Martin Luther King, Jr. > > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Grégory Joseph > Sent: Thursday, July 22, 2010 11:01 AM > To: Magnolia User-List > Subject: Re: [magnolia-user] Question about STK licensing terms > > > Hi Alex, > > > On Jul 22, 2010, at 16:43, Alex Cougarman wrote: > >> Hi, >> >> Based on my limited understanding of Magnolia thus far, I think the > following is true; please correct me if I’m wrong: >> >> - If I use the STK (Standard Templating Kit) via the web interface, the > system automatically creates the necessary JSP template files. > > The STK templates are all FreeMarker-based, but that's unrelated to the > discussion at hand ;) > >> However, the free version of Magnolia requires that when you use the > STK, you must display the logo on each page: >> >> “Briefly, the CPAL license means that the STK is free and open-source, > but you need to have a link to Magnolia on each page. If you purchase the > Enterprise Edition, this requirement is dropped.” > (http://documentation.magnolia-cms.com/templating/stk.html) > > Yes; so in short you're free to alter the existing STK templates, so long > as you don't hide/remove the "badge". > >> - If I use the file system method of creating templates (create the JSP > and put it in the right folder, etc.), no logo needs to be displayed but > then we have to manually keep the author instance and the live instance in > sync, which can be a mess. > > You can still create your own templates in the repository directly, not > using the filesystem; either with FreeMarker and using the > inplace-templating module, or even still in JSP. Ruben will probably shime > in soon, as he wrote a module that does something similar to our > inplace-templating, but for JSP (which is trickier since JSP mandates the > usage of the filesystem). > > Now, whichever way you go, doesn't mean you have to maintain anything > manually on the filesystem. If you use the module mechanism, your > templates will be part of your module, so all you'll have to do is update > your module(s) on all instances. (if using JSP for example, the MM will be > able to re-extract your jsp files to the filesystem) > http://documentation.magnolia-cms.com/reference/module-mechanism.html > > Hope this clarifies a bit. > > Cheers, > > -g > >> >> Is this true? >> >> Sincerely, >> Alex Cougarman >> >> UNC-TV >> Web Applications Developer >> 919-549-7823 >> ---------------------------------- >> “I believe that unarmed truth and unconditional love will have the final > word in reality. This is why right, temporarily defeated, is stronger than > evil triumphant.” -- Dr. Martin Luther King, Jr. >> >> >> >> ---------------------------------------------------------------- >> 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]> ----------------------------------------------------------------
