A while ago I blogged about running your custom deployer logic in a Java IDE. That article was based on my experiences with SDL Web 8.5 (aka Tridion 8.5) and the *.bat file and pom.xml that were given in that article were based on this version.
Total, I’m here to tell you that the same thing is possible in Tridion 9.
The process of creating components in Tridion has always been very different from creating pages. When you create a component you are guided by a schema, which provides strict guidelines. However, when you want to create a page, you start off with a tabula rasa – essentially a blank sheet of paper.
This changes with the introduction of regions and page schemas. Here’s how. Continue reading
The latest version of Tridion (SDL Tridion Sites 9) is now fully supported by DD4T for Microsoft.NET. Read here how easy it is to upgrade.
After playing around with installing SDL Tridion Sites 9 from scratch I wanted to know more about the database upgrade steps of this latest release when upgrading from an older version of Tridion.
SDL supports upgrading to SDL Tridion Sites 9 from one of the following versions directly:
- SDL Web 8.5 (also known as SDL Tridion Sites 8.5)
- SDL Web 8 with Cumulative Update 1
- SDL Tridion 2013 SP1 HR1 (Hotfix Rollup 1)
SDL Tridion Sites 9, part of SDL Tridion DX, introduces several changes and new features for managing digital experiences. Of course, we were eager to install the new version and play with it.
Here are some of the things we noticed when installing SDL Tridion Sites 9 that perhaps you didn’t know.