Yes, it is odd. Whoever built it most likely didn't know a better way to add a "current" class to site wide menus.
My article (towards the bottom) discusses how to add an Editable Attribute to the Template's body tag and amend the attribute in child pages.
Ken, if you're going to follow Nancy's suggestion to include the persistent page indicator, I would also suggest replacing that menu from the template with an include. This will allow you to easily modify the menu without updating every page of the site (if they suddenly decided to add a dropdown etc). I would also do this for the footer content and the head section.
<!-- Begin menu include -->
<!--#include virtual="/includes/menu.ssi" -->
<!-- End menu include -->
<!-- menu.ssi content -->
<li><a href="#" class="current">Home</a></li>
<!-- End menu.ssi content -->
Ken Binney wrote:
Thanks Rik -
I LOVE SSI too, but site owner is pretty stretched... and is already committed to DWT
I'm not saying remove the template Ken, i'm saying use both template and SSI. If you are going to amend the menu and make it uneditable, you have nothing to lose by adding that content within an include. Same with the head and footer.