On Jun 10, 2009, at 2:36 AM, Matteo Pelucco wrote:
Hi all,
I will be short.
I have 3 question about STK and Extended STK.
1) Imagine I have a footer content which must be managed by editors.
I create a paragraph, nodeData... and make it working for /home .
Now, I want to inherit that paragraph on below pages footer, like
sitedesigner, do you remember? On one project we have created a
custom taglib capable of inherit paragraphs, but I am wondering if
this behaviour has been covered by STK module.
2) On extended STK I can create more than one configured site
definition. I think to have understood that we can add a nodeData
"site" to a page in order to use into the relative page template the
site definition, like model.site.css..... but model.site is created
by STKTemplateRenderer. How can a custom site definition be loaded
for a certain page? I would like to know how Magnolia can call the
ETKSiteManager.getAssignedSite() method, I can not find out (it can
be the time, it is 02.34!!)
can you wait until Monday? It will be much clearer then ;-)
3) jQuery is the "preferred" JS framework by Magnolia?
JQuery is incredible. It has taken web dev to a new level.
--- side note --
With Magnolia STK you get a clear separation of concerns:
Content: JSR 170
HTML: Template
Business Logic: Java
Styling: CSS
(Client-side) Functionality: JQuery
This separation of concerns proves to be extremely beneficial. You
decide what area you want to change and can leave everything else
untouched. Look at the HTML before CSS and JQuery is applied and you
will understand just how powerful and elegant this approach is. Or
look at the templates and see how they can just rely on information
that is provided by the model instead of mixing business logic with
html (arghhh). Remember that you can use your own classes to overwrite
model functionality - without ever touching the templates. Or use a
different video player? JQuery will do the job.
STK is SEO optimized, accessible, tested, easily extensible, pixel
perfect customizable, supports mobile devices and is maintained by
someone else than you.
Have a look at it - especially after we release 4.1, where we have
made configuration options explicit by introducing default (or
"prototype") definitions on every level of STK.
Regards
- Boris
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
