Moving from templating to software development

Tridion, Continuous Integration, Templating, Software Development

The way we're developing SDL Tridion websites is changing. We we're used to templating everything in Tridion and Tridion was our version control system. The web application we published were jsp pages, aspx pages, or pages based on some other technology. We're moving away from this way of working now and we're moving towards Software Development. We're hearing things like

read more

DD4T: Configuring multiple environments

DD4T, Tridion, Continuous Integration, MSBuild, MSDeploy

When deploying a .NET application on multiple environments you have to deal with multiple configuration settings for each server. This can be fixed by creating multiple packages, publishing from Tridion or creating parameter files. MSDeploy parameter files Multiple packages takes too long to finish and there are multiple files you might want to change. That will take multiple transform files.

read more

DD4T: Creating deployment packages

DD4T, Tridion, Continuous Integration, MSBuild, MSDeploy

Do you remember Tridion Deployments to be copy paste tasks, Running Content Porter to transport to your Test, Acceptation and Production environments? Always forgetting some dependency? DLL files, css, js files and other static dependencies need to be copied from one environment to another. Creating large installation instruction documents. It is deployment hell... Let's make it a bit easier This

read more