I prefer to have the full navigation on all pages; if some links aren't relevant to the current context, they can be 'removed' with CSS.
Additionally, especially with CMS's, caching of menu's is typical. If you did this with server side code, you would have to have a separate cache for each menu on each page. Doing it this way wouldn't necessarily result in a measurable performance hit, but it seems extraneous. On Tue, Feb 4, 2014 at 1:35 PM, Tom Livingston <[email protected]> wrote: > On Tue, Feb 4, 2014 at 1:31 PM, Colin (Sandy) Pittendrigh > <[email protected]> wrote: > > The original poster indicated he is generating his pages with PHP. > Others > > since have shown how the home link could be hidden on the home page only > > using CSS rather than PHP. But the same result *could* be accomplished > with > > server-side PHP logic. So perhaps the interesting question is "Which > avenue > > is better? CSS or server side scripting?" > > > > Is there something about the CSS only approach that adds measurable > value? > > > > > Seeing this is a CSS list, I answered with CSS. I'm sure PHP can do > this. Which is better? I don't technically know. > > > -- > > Tom Livingston | Senior Front-End Developer | Media Logic | > ph: 518.456.3015x231 | fx: 518.456.4279 | mlinc.com > ______________________________________________________________________ > css-discuss [[email protected]] > http://www.css-discuss.org/mailman/listinfo/css-d > List wiki/FAQ -- http://css-discuss.incutio.com/ > List policies -- http://css-discuss.org/policies.html > Supported by evolt.org -- http://www.evolt.org/help_support_evolt/ > -- Chris Rockwell ______________________________________________________________________ css-discuss [[email protected]] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
