That's the theory, yes. But the CSS still uses `#page-about #header .about a`. So if you create an 'about' page for mentors (for example), the 'about' menu item will be selected.

Also, it might be worth adding a (pseudo-)property/method to the `page` model (something like `root`) which would return the highest-level page in the tree. This way, `section-X` would be consistent even when you have nesting more than one deep. Right now, `/a/b/c/` would be in a different section to `/a/b/`. Of course, that might be the idea, but I'd have thought both being in `section-a` would make more sense.