Thread

Hi -

We’re about to build a site for a client where one of the requirements is that they want to be able to manage ALL nav - primary, secondary and tertiary. This includes the nav naming and structure - and controlling the corresponding URL structures for all published pages.

As such, our first thought was to build the site with an add-on like navEE for ease of use of managing the actual nav - and then train them on publishing all entries as Pages so they can control the URLs they’re setting up in navEE. We plan on building out about 8 templates which should cover them off for all their potential content scenarios - and thus they’ll be using such templates all over the place.

However, we’ve never gone down the road of needing total nav and URL control. I’m not worried about the client learning curve in this solution - they’re site admin will be knowledgeable.

What I am wondering is whether this approach makes sense? Whether there are any significant pitfalls on running the whole site via pages?

Lastly, I’ve been looking at Structure and wondering if this presents any benefits over navEE in this scenario. I know navEE and like it but haven’t used Structure.

Any thoughts/advice would be greatly appreciated!!!

Thanks,
Mike

We have a similar inquiry.  We love Structure for our site.  It follows a logical interface for a large site and great control of the uri, but we’re not using it for navigation.. But we’d like to add NavEE and would appreciate any feedback on if there are any compatibility issues.  Thanks in advance.