Re: Editing a navibar which appears on many pages

Hi,

Simon Rönnqvist wrote:
> On Aug 9, 2005, at 20:50, Matthias Dieke wrote:
> 
>> Simon Rönnqvist wrote:
>>
>>> I'm currently going to use Flux CMS as an updating tool for one of  
>>> my  clients' homepage.
>>> All pages would have a content-column and a navibar.
>>> I'd like my client to be able to add new pages and to link to them  
>>> in  the navibar. This brings up the question, how does one make  an  
>>> editable navibar which has the same content on each and every  page  
>>> (preferably including the blog and gallery sections)?
>>>
>>
>> As far as I understood your question correctly thats no problem ;)
>> When you are creating new "collections" or "resources" (xhtml)  within 
>> the Flux CMS they would automaticliy show in the navibar.
>>
>> For details have a look at:
>> http://docs.bitflux.org/en/user/collections/
>> http://docs.bitflux.org/en/user/resources/
>>
> 
>   Oh, thanx... I never realised it was automatic, never tried... ;-)
> How can I select in which order the collections are to be displayed  in 
> the navibar?

Right click on a collection or resourse (xhtml) and choose "edit in 
properties".

Display-order is the right value to define the order of collections and 
resources.

0 = won't be displayed
1 = fist in navi
10 = secand in navi
and so on...


less numbers are displayed at first in the navi.

Tip: use 10, 20, 30 for ordering your collections. So it is easier to 
reorder the collections in the future ;)

Matthias

> 
> 
> 
>>> Another thing I'm wondering is which template-language to use,  
>>> XSLT,  TAL or XSLTAL. XSLT is appealing since learning that can  be  
>>> beneficial later on with other systems than Flux CMS (or Zope)  too,  
>>> but if another is a much wiser choise then I might have to  go with  
>>> that one.
>>>
>>
>> IMHO, XSL is the right way ;) All Flux CMS themes (bxcms, 3-cols, 2- 
>> cols) which you get during the installtion are based on XSL-templates.
>> Hope that helps, otherwise ask again ;)
>>
> 
>   Oh, thanks... I wanted to hear that XSL was the best choise... :-)  I 
> like learning standards over more or less proprietary things (such  as 
> TAL), that's what I like the most about Flux CMS/Popoon too...  Most of 
> the stuff you learn about it is likely to be useful with  other systems 
> too later on.
> 
> And since the navibar stuff is rather automatic this should be really  
> easy... I might just as well take one of the Flux CMS themes as an  
> example.
> 
>   cheers, Simon
> 
> 
-- 
bitflux-cms mailing list
[email protected]
http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms