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