Delivering The Sitecore Experience

Recently, in a discussion with the team regarding how to structure content in Sitecore brought up some very interesting theories which I thought would be useful to share. So, my theory was that enterprise content should be grouped reflecting the business structure, as I discuss it here ) and taking it one step further, using the same logic to structure content within a site. But this idea was promptly met with rejection. The counter theory offered was that the content should actually follow navigation paths used by visiting user personas. This immediately brought to light a rather large assumption:       Do we assume that the content tree structure in Sitecore dictates the navigation paths for end users? The answer is, not necessarily. In my view, the minimum requirement should be to facilitate logical grouping of content that always avoids content duplication. I think there are two primary ways of implementing navigation paths: Create navigation components such as Primary Nav and Left

This post is my humble attempt to share what I have discovered from my experience to be a best practice in implementing IA (Information Architecture) and content hierarchy for an enterprise implementing manage sites within a single Sitecore instance. As this is my first Sitecore blog, not to mention my first blog post ever, please feel free to comment and critique my approach as I attempt to contribute to the incredibly talented Sitecore developer community. So let’s just jump into it, consider the following scenario: an enterprise has just acquired Sitecore as their CMS platform and wants to strategize on how they should implement IA and content hierarchy so that they maximize reuse and have a Sitecore instance that scales really well. It is unsurprisingly common for businesses to decide to manage the entire company’s content within a single Sitecore instance and why not, since this is one of the easiest selling points for Sitecore, “Buy a single instance and you can build any many we