Displaying navigation for non 'homepage' urls only

(Dw Andrew) #1

Hi,




This is a scenario which I feel is pretty basic, I want to use a single design for a homepage and content pages. I only want content pages to have a navigation pane displayed, and the homepage will be blank/have some other content.



So the homepage should use the same design, but not display the navigation pane.



I have tried to use a metadata flag to identify homepage vs content pages to no avail. Using two designs seems too messy as changes will need to be kept up to date across them both. So can I use the metadata field to achieve what I want? Not needing to use paint layouts etc would be really good!

(Greg Sherwood) #2

You'll need to create a customisation of the inside design and customise the menu design area. Then you'll want to change it's "Print" setting to NO so that it doesn't show.


The design manual should get you somewhere or someone might be able to post some instructions.

(Scott Hall) #3

Hey


Having a separate parse file for 'home' versus 'inside' page designs may be a good way to go (usually helps when most home pages require specific 'real estate') and also gives you more flexibility between the two regarding markup and css control.



Having said that, there are also many cases where designs can work from the one parse file (to avoid redundant associated files), usually simple designs and small sites, as long as you don't foresee the site becoming quite large later on, or people wanting to throw all sorts of stuff into your home page?



If you go the one parse file for home versus inside then you have a number of options available:



  • Use a globals keyword to output and append asset ID into a class name within the body tag e.g. class="page-id-blah" where blah is the globals keyword for asset id. You can then use this class and the related home page id to control all containers within the body tags for the home page specific styles. This can all be done from your stylesheet, e.g. for all pages you might have [b]#content-main[/b] but for the home page you might specify an override using [b].page-id-blah #content-main[/b]. You can apply all sorts of css magic for page specific area using this method, e.g. hide containers, control dynamically etc.
    [*]As per Greg's suggestion, create the design parse file using your inside design as a guide and apply this to the whole site, then create a customisation of this design which 'turns off' the nav and apply that customisation to the home page only. As long as your MySource Matrix tags are correct within the parse file, you should be able to select the 'details' screen of the new customisation and then customise the nav area by changing 'print' to 'no'. Any containers for the nav that may still be causing grief can be controlled via CSS using the method mentioned in the first point (above).
    [*]Use metadata to output page specific stuff to class name similar to point one.
    [*]Use declared vars design area and a customisation to output page specific variable to classname.


I'd suggest the use of the first two options.