I would never include menus in a sitestructure, why don't you have a logical structure and give pages a true-false checkbox for each menu like:
* include in topnavigation
* include in quicklinksnavigation
* include in sitemapnavigation
Better:
But an ever better question would be, why you are doing this? normally the top navigation should reflect the actual structure of the website, an optional leftnavigation can then include all children of the current section.
- footerlinks can be selected using a true/false property added to the document type of the page. (then you create a second navigation xslt that only shows nodes with footerlinks=true)
- umbracoNaviHide can be used to hide pages from the top navigation (terms & conditions, privacy statement etc)
I have never created a site structure in function of different navigation elements, as this is reflected in the URL and goes against a lot of the ideas behind "usability" research...
To make my way of working a bit more clear, here is a site structure:
And here the navigation:
You see a top navigation, and a left navigation. There is no need to structure the pages in the backend according to different navigation elements.
All pages appear in both, but the leftnavigation filters out so it only shows the children of the current top level site.
* if i want to hide a page in the top navigation, i also want to hide it in the left navigation, so i just add the property "umbracoNaviHide" to the to the documenttype (true/false) and check it. The page no longer appears in the navigation.
* The top navigation is made out of 3 seperate "NavigationFromSource.xslt" macro's, inserted in the template next to eachother
Managing folders and URLS
Hi,
I would quite like to organise the backend using folders for certain menus ie:
Top Link
Main Navigation
Footer Links
I am not sure if there is a better way to do this and still keep it nice and simple in the backend.
I am aware that this might mess up the URLs as we would have things like:
mysite.com/main-navigation/about-us.aspx
which just looks silly - is there away around this?
Any thoughts or suggestions would be much appreciated.
Thanks
Scott
You can kill the "/main-navigation/" via UrlRewriting. Take a look into the UrlRewriting.config in the config folder
And check out the documentation on http://www.urlrewriting.net
Also you can use UmbracoUrlAlias I think: http://our.umbraco.org/wiki/reference/umbraco-best-practices/umbracourlalias
hth, Thomas
I would never include menus in a sitestructure, why don't you have a logical structure and give pages a true-false checkbox for each menu like:
* include in topnavigation
* include in quicklinksnavigation
* include in sitemapnavigation
Better:
But an ever better question would be, why you are doing this? normally the top navigation should reflect the actual structure of the website, an optional leftnavigation can then include all children of the current section.
- footerlinks can be selected using a true/false property added to the document type of the page.
(then you create a second navigation xslt that only shows nodes with footerlinks=true)
- umbracoNaviHide can be used to hide pages from the top navigation (terms & conditions, privacy statement etc)
I have never created a site structure in function of different navigation elements, as this is reflected in the URL and goes against a lot of the ideas behind "usability" research...
To make my way of working a bit more clear, here is a site structure:
And here the navigation:
You see a top navigation, and a left navigation. There is no need to structure the pages in the backend according to different navigation elements.
All pages appear in both, but the leftnavigation filters out so it only shows the children of the current top level site.
* if i want to hide a page in the top navigation, i also want to hide it in the left navigation, so i just add the property "umbracoNaviHide" to the to the documenttype (true/false) and check it. The page no longer appears in the navigation.
* The top navigation is made out of 3 seperate "NavigationFromSource.xslt" macro's, inserted in the template next to eachother
* The leftnavigation is a custom variation of the "navigationfromSource" xslt. I wrote about making this navigation here: http://our.umbraco.org/forum/developers/xslt/10946-creating-multi-level-navigation-in-45-schema
Footernativation could be really simple based on another property...
is working on a reply...