TDS Blog: Sitecore Best Practices and Dev Insights

September 22, 2015 | Charlie Turano

When implementing Sitecore websites, we sometimes run into a situation where the Content Editor wants to personalize or A/B test components that are common to multiple pages in the site. A good example of this is the header and/or navigation components. The problem we run into is that the components need to behave the same on all pages and it would be very difficult, if not impossible for content editors to maintain these components on all pages on the site. I have seen a few ways of solving this problem, but most solutions had some drawbacks that limited the capabilities of the content editor.

Tags

4.0 acquisition avtor azure best of tds 2015 back end best practices builds bulgaria charlie turano code generation code connection content editor content management delta deploy continuous integration deployment datasources development feature features feydra front end front-end guest post how to habitat hedgehog helix jenkins jenkins build miscellaneous kliment klimentov launch sitecore live chat mvc mvc rendering placeholders post deploy step press release preview nuget package rainbow razl razl 4 razl 4.0 sitecore development schackathon sean holmesby sitecore rocks security sitecore roles seo sitecore sitecore user group sitecore 9.2 sugcon sugcon anz sugcon eu sxa sync vibert trahan tds tds 5.0 visual studio visual studio online tds 5.6 tds 5.8 tds classic webinar tds classic 5.6 tds classic 5.7 wellness tds classic 5.8 wffm tds classic best practices tds validators yaml technology tfs tom kamin una verhoeven