When SharePoint's navigation doesn't cut the mustard

SharePoint implementation project involving multiple portals, WSS sites, non-SharePoint sites & MCMS 2002 integration. Lacks logical hierarchy

I’m in the midst of a big SharePoint implementation project. It involves multiple portals, WSS sites, non SharePoint sites, and integration with MCMS 2002. The whole project is for a single site, but is actually going to be a collection of numerous sites (as you can see with multiple portals and WSS sites). The problem is, even with Shared Services, SharePoint doesn’t organize all these portals under a logical hierarchy… they are all in a flat representation.

No user wants that… you want a central point with a hierarchial organization of all the resources… be it an area, subarea, WSS site, portal, or a non SharePoint site. Since the SharePoint navigation doesn’t provide this OOB, we’re building our own. I can already tell you it’s a tall task. If you’ve had experience creating custom user controls and adding them to the portal site definition files, I’d really be interested in talking to you… please contact me!

A recent post with my latest challenges: NNTP Post: Custom user control in site definition

Andrew Connell
Developer & Chief Course Artisan, Voitanos LLC. | Microsoft MVP
Written by Andrew Connell

Andrew Connell is a web & cloud developer with a focus on Microsoft Azure & Microsoft 365. He’s received Microsoft’s MVP award every year since 2005 and has helped thousands of developers through the various courses he’s authored & taught. Andrew’s the founder of Voitanos and is dedicated to helping you be the best Microsoft 365 web & cloud developer. He lives with his wife & two kids in Florida.

Share & Comment