Download
2009-10-19, 02:38:13
I was wondering about this myself, and I ended up crafting a workaround for a client project.
Each primary section of the site has its own template. Within that template, I used a component that included the sub-navigation for that particular section.
So the "widgets" section includes a component called "widgets-nav", for example. And then "gadgets" gets "gadgets-nav", and so on.
It's not the prettiest thing (and definitely not scalable, but GS is for small sites, not large). If you're comfortable with the system and know that you won't be changing your navigation structure on a regular basis, it should be sufficient.
Each primary section of the site has its own template. Within that template, I used a component that included the sub-navigation for that particular section.
So the "widgets" section includes a component called "widgets-nav", for example. And then "gadgets" gets "gadgets-nav", and so on.
It's not the prettiest thing (and definitely not scalable, but GS is for small sites, not large). If you're comfortable with the system and know that you won't be changing your navigation structure on a regular basis, it should be sufficient.
