The ability to react to and evolve with both the market and our customer base is one of the many reasons TDS is considered best of breed. Sitecore created the Helix architecture as a recommended way of building websites and created Habitat to demonstrate it. Habitat is a modular architecture, an approach to take to achieve an easily maintainable solution over time. TDS takes Habitat to the next level.
We're often asked if TDS is compatible with Sitecore Habitat. The answer is: absolutely! TDS and Habitat work very well together. When Habitat was released, we created a TDS branch of the Habitat demo site which is freely available in Github. This branch also uses some of TDS's other features, removes the reliance on gulp and NPM, and leverages many of the features available in TDS 5.5.
Delta Builds only includes items in deployment/package if they are changed after the specified date.
Cloud Builds adds the TDS build components using a NuGet package.
Auto Deploy deploys content files as they're edited.
Sync New Features employs Sync Using History across multiple projects in a single Sync operation.
Auto Sync picks up changes from Sitecore and syncs the project automatically.
Post Deploy Steps creates custom steps to be executed after deployment and package install.
Local databases prevent collisions, while continuous integration and automated deployments have been made easy. Developers can employ a full audit trace on Sitecore items, reverting changes is simple and quick, and Sitecore items and source code move together. Leveraging Source Control means that the constant changes made during the course of a project merge seamlessly, and that new additions to your team are quickly brought up to speed.
Collisions and other issues are caused by sharing a common database. There is no clear item ownership, and audit trace is missing. Reverting item changes is difficult, especially since code and items don’t move together.