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.
UPDATE: you can now run the Tridion deployer in your IDE if you are on Tridion 9 also! Instructions below have been modified to show the differences between SDL Web 8.5 and Tridion 9. Now on to the story.
Whenever you publish a page, component or another type of item in Tridion, the item is first published, then transported and finally deployed. SDL offers various ways to extend or modify this deployment process. All you need to do is write some custom java code. The most commonly used extension points are deployer modules and storage DAOs. You can find more about this here and here.
In this post I’m not going to explain what these extensions are and what you can do with them. Instead, I will focus on how to develop this type of extension effectively. As always with Java (in my experience at least), the code is easy but the environment is hard. But if you follow these instructions, you will be able to run your customizations locally, make sure they get triggered, and even perform step-through debugging on your code. Pure bliss!
SDL is conducting a series of webinars ahead of the release of SDL Tridion Sites 9 later this year. Recordings of the webinars are made available by SDL. The upcoming release is an important milestone for SDL Tridion DX, which integrates SDL Tridion Sites (formerly known as SDL Web) and SDL Tridion Docs (formerly SDL Knowledge Center), to define digital experiences on a global scale.
In version 2 of SDL’s Digital Experience Accelerator (mostly referred to as DXA), SDL introduced the DXA resolver. Customizing the resolving process can be used to manipulate the list of items to publish that results from a publish action.