Split Auto-Nav
Permalink 1 user found helpful
I'm learning C5 in a trial by fire on a real project... I know, I must be nuts.
Is there a way to give each page a class/property/what-have-you that can then be used to filter the links generated by the auto-nav block. (I've seen the controls that allow selection of top-level/sub-level pages for auto-nav, but that's not quite what I'm after.)
Most of the sites I design have two kinds of top-tier navigation - main and utility. The utility pages are at a peer level with the rest of the top-level pages, but their nav links are separate and de-emphasized from the main nav (see image attached to post)
Utility: Home, In The News, O Blog, Swag, Wholesalers
Main: Breads & Loaves, Pies & Treats, Events & Festivals, Where To Find Us, Our Bakery, Our History, Contact Us
Is there a way to give each page a class/property/what-have-you that can then be used to filter the links generated by the auto-nav block. (I've seen the controls that allow selection of top-level/sub-level pages for auto-nav, but that's not quite what I'm after.)
Most of the sites I design have two kinds of top-tier navigation - main and utility. The utility pages are at a peer level with the rest of the top-level pages, but their nav links are separate and de-emphasized from the main nav (see image attached to post)
Utility: Home, In The News, O Blog, Swag, Wholesalers
Main: Breads & Loaves, Pies & Treats, Events & Festivals, Where To Find Us, Our Bakery, Our History, Contact Us
Thanks for the suggestions, unfortunately those solutions won't work for me.
In digging a bit more I can see precisely what I'd like to do to alter the /concrete/blocks/autonav/view.php but I don't want to just go changing core files and end up breaking the site after a future upgrade.
I also noticed there are two templates listed and I think that might be the best approach for me, but again, I'm not sure I should go changing files in the /concrete/blocks/autonav/ folder.
So, what is the proper way to overload/extend core components?
In digging a bit more I can see precisely what I'd like to do to alter the /concrete/blocks/autonav/view.php but I don't want to just go changing core files and end up breaking the site after a future upgrade.
I also noticed there are two templates listed and I think that might be the best approach for me, but again, I'm not sure I should go changing files in the /concrete/blocks/autonav/ folder.
So, what is the proper way to overload/extend core components?
Answered my own question.. I'm getting there... thanks for the help...
http://www.concrete5.org/documentation/how-tos/developers/change-th...
http://www.concrete5.org/documentation/how-tos/developers/change-th...
You can also exclude pages using attributes.
http://www.concrete5.org/documentation/how-tos/designers/how-to-hid...
If you want a more complex split, have a look at the Manual Nav block. Mos autonav templates can be adapted to work with it.
Also consider creating menus using the page list block.