1. - After programmer finish his work on simple template - designer starts
make this template good-looking and current node sequence is very complex
for him(I know - I worked with such designers :)))).
- I've just understand why we have misunderstanding
-"contentNodeCollectionName" is child node of page, but I thought that it is
paragraph attribute :))) I Magnolia developers will change
"contentNodeCollectionName" to paragraph attribute - it will be easy
to move paragraph to another zone - in this case we only should change
this paragraph property.
In current realization to change "contentNodeCollectionName" you should move
paragraph node (in "Tools"->"JCR Browser (Website)") to another zone
2. I didn't suggest to remove current tags - I suggest to replace current
examples(in User Guide) to simplest.
3. :) At current point I am looking for free Java based CMS.
Magnolia is good CMS at first sight. But it doesn't have enough paragraph
types. It doesn't have news list, guest boot, test block, subscribe block,
forum etc. Actually I can write it but it takes a time :(((
4. I am not sure, but in documentation I saw:
<cms:newBar
contentNodeCollectionName="mainColumnParagraphs"
paragraph="samplesTextImage,samplesDownload,samplesLink"/>
where "paragraph" attribute contains possible paragraph types.
But (I don't know realized such possibility or no) it would be better
if we didn't set up this attribute - Magnolia will return possible paragraph
list from repository.
I'll try to visualize all that I say:
-------------------------------------------
zone="top"
-------------------------------------------
zone="left" | zone="center" | zone="right"
| |
| |
-------------------------------------------
Zone="bottom"
-------------------------------------------
In this case page template will be more and more simple.
Designer can easy to change them(or create) and he shouldn't know
JSP or Java - he should know only one tag <cms:zone name="zone_name" />
and content team already can fill such templates by paragraphs.
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 10, 2006 4:25 PM
To: [email protected]
Subject: Re: [magnolia-user] Simplify templates
Hi Andrew
1. Well, flex your mind on that one.
One example I can think of is changing a top menu to a side menu.
2. Custom tags, like <cmsJon:PublishToPublicSite> (made that one up =).
Again flex your mind.
3. Yes, these are all fine solutions.
The bottom line is: Why do want to add another layer of complexity?
As a Magnolia-beginner your level of reading jsp tags has to be able to
coupe with and understand what happens in those 11 lines. (Not saying
that you are a beginner :) )
4. Ex.
<cms:newBar contentNodeCollectionName="contentParagraph"
paragraph="samplesTextImage"/>
to
<cms:newBar contentNodeCollectionName="contentParagraph"
paragraph="primetimeTextImageVideo"/>
Can't do that when only dealing with <cms:zone name="leftColumnZone"/>
Jon
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
