Joseph Banks wrote:
> I recently installed Radiant and started playing around with it a bit.
> Since I only know html/css I've been looking at various CMS systems (the
> only other one to really catch my eye was Modx) to figure out if these
> could give me easy access to more dynamic features.
>
> I really enjoy how simple the admin interface of Radiant is relative to
> all the other CMS systems - deceptively simple even, when considering
> the underlying flexibility.
>
> I employ a rather simple (in my mind) 2 level tab-based navigation bar
> on many of my websites (example: www.ambitiouslemon.com note: not IE
> compatible). I was hoping Radiant could code this in a snippet that I
> could call from my layout. But one of the odd things I have noticed
> about Radiant is that it has all pages as children of the home page, and
> this screws up the built in <r: navigation> tag's ability to create the
> tab bar as I had planned. I have some other problems, but I suspect
> thats just because I don't understand the tagging language well enough -
> but the big issue is that I can't set up my actual page hierarchy in a
> way that would be properly reflected by this navigation system.
>
> Is there a conceptual reason for not allowing pages as siblings to home
> rather than children? Am I missing something here?
Here's an example of how I'm using the <r:navigation /> tag on
RadiantCMS.org:
<r:navigation urls="Home: /">
<r:here><strong><r:title /></strong></r:here>
<r:selected><a href="<r:url />"><r:title /></a></r:selected>
<r:normal><a href="<r:url />"><r:title /></a></r:normal>
</r:navigation>
<span class="separator"> | </span>
<r:navigation urls="Demo: /demo/; Download: /download/">
<r:here><strong><r:title /></strong></r:here>
<r:selected><strong><a href="<r:url />"><r:title
/></a></strong></r:selected>
<r:normal><a href="<r:url />"><r:title /></a></r:normal>
<r:between> <span class="separator"> | </span> </r:between>
</r:navigation>
<span class="separator"> | </span>
<a href="http://dev.radiantcms.org/";>Development</a>
<span class="separator"> | </span>
<r:navigation urls="Mailing List: /mailing-list/; Weblog: /blog/">
<r:here><strong><r:title /></strong></r:here>
<r:selected><strong><a href="<r:url />"><r:title
/></a></strong></r:selected>
<r:normal><a href="<r:url />"><r:title /></a></r:normal>
<r:between> <span class="separator"> | </span> </r:between>
</r:navigation>
As you can see you may sometimes need to use multiple <r:navigation />
tags in order to get the effect you want. It's extremely verbose, but it
works.
You could use this with:
<r:if_url matches="^/start_of_url">...</r:if_url>
and
<r:unless_url matches="^/start_of_url">...</r:unless_url>
In order to get the second level of navigation to work.
Ryan Heneis wrote an article on Art of Mission which outlines another
technique using HTML level IDs:
http://artofmission.com/articles/2006/06/06/radiant-cms
--
John Long
http://wiseheartdesign.com
_______________________________________________
Radiant mailing list
[email protected]
http://lists.radiantcms.org/mailman/listinfo/radiant
