TDS Blog: Sitecore Best Practices and Dev Insights
August 10, 2017 | Charlie Turano
Setting up Azure staging slots, so the next release of our project can be placed there, allows us to deploy the new code to a private website (the slot), and test it before pushing it live. We are going to script this process to make it easier for the devops team to automate.
TweetAugust 09, 2017 | Kliment Klimentov
There are certain systems and processes that you can put in place to make a TDS Classic project run more smoothly. We're highlighting the best practices that our team recommends for getting the most out of TDS Classic.
TweetAugust 03, 2017 | Charlie Turano
Modify the scripts so that the compiled LaunchSitecore site is also provisioned into the new XP environment.
TweetAugust 02, 2017 | Kliment Klimentov
Following TDS Classic best practices, like using Delta Builds and Delta Packages, can make the entire development experience run much more smoothly.
TweetJuly 26, 2017 | Charlie Turano
Modify the previous install so that the initial install contains the Sitecore Package Deployer module. It is an excellent way to enable continuous integration to the website.
TweetJuly 19, 2017 | Kliment Klimentov
TDS Classic can be used in many ways, but the goal is always the same: make development (and developers lives) easier. Whether it's using the Sitecore Package Deployer or using validators, following best practices can make your entire experience run much more smoothly.
Tweet