Olaf iLink ha scritto:
Hello Matteo,
thanks for your reply. The thing is that our company designs websites
from scratch on our (interaction) design department, which are then
ported from PSD's to HTML and CSS files. So we need to develop our own
Magnolia templates from scratch to have the website identical to the
designs. The STK is interesting, but working this way is
counter-productive to the goals we focus on, as our produced html needs
to be really identical to the original designs, and not a rough estimate.
Olaf
Hi Olaf,
I understood your need, AFAIK there are no limits on STK usage: maybe
there is a little work overhead at the beginning to better understand:
1) How many templates do you need
2) How to decompose templates into subtemplates
3) How to organize CSS / JS files
Once you have 1..2..3 point done, you need to map your decision to STK
configuration and use it.
I think that STK documentation can really help users at the beginning of
Magnolia... It should arrive, isn't it? ;-)
Anyway, STK and FreeMarker is not the only possibility you have. You can
also use standard JSP pages (even Coldfusion!) to produce your HTML.
But the template structure should be done despite of the template format
you choose.
HTH,
Matteo
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
