With the release of SDL Tridion 2013 SP1, we get a lot of new functionality. One of the interesting features I found was the ability to decommission a Publication Target. This feature is added to the Core Service, and currently not directly available from the UI. Which sounded like a good exercise to make a UI extension, with which you can call this new method.
December is the time to look back, and if you have been doing a sprint of 365 days, now is the time to start to think about the retrospective. That is exactly what the MVP Selection Panel is doing right now. To select the new MVP’s for the SDL Tridion MVP Award program, we need to evaluate each nominee’s voluntary contribution to the SDL Tridion community over the past 12 months. Which is why I would like to mention, it is not too late.
I was recently working on a Content Delivery syndication piece for a client so that they could pull various components of varying schema’s based on a variety of metadata values. The client requested that they be able to pass in a list of metadata keys, with each key having an accompanying list of meta-values to be searched on. Continue reading
Does publishing a Component linked to many Dynamic Component Templates lead to publishing performance issues?
I recently ran into a scenario where, due to an update to business requirements, I had to change Component Templates from statically embedded to dynamic. In my case there were 14 different CTs linked to the same Schema. This means that when 1 Component is published there are 14 Component Presentations being rendered and sent to the Broker. The question then arose, does this kind of a design lead to publishing performance issues?
The SDL Context Engine Cartridge is a Content Delivery cartridge that integrates with the Ambient Data framework of SDL Tridion. The Context Engine essentially provides a huge amount of information about the device, browser and operating system of your website visitor. This seemed like a perfect cartridge to integrate with SDL SmartTarget, so after immediately doing so, I thought I’d share my configuration.
The open source SI4T (Search Integration for Tridion) project allows you to pass through 3 levels of control over what content gets indexed: Firstly, the default, zero-configuration behaviour. Then there is fine-grained configuration via metadata and parameters, and finally total extensibility by coding your own indexing TBBs. This article talks through how you can refine your indexing strategy by passing through these levels. Continue reading
In my previous post about ECL, I’ve discussed querying ECL Metadata in the Broker, by making it available as part of the Multimedia (stub) Component Metadata. Now in that post I explained how it could be copied at Publishing time and the “evil” twists that process came with. In this post I’ll discuss an optional approach, using the SDL Tridion Event System which makes the process of copying external metadata to (normal) metadata less evil (just the process, not the fact that we do it ;o).
So tonight I geeked out and created a boilerplate Java project with debugging properly enabled for Tridion Storage Extensions when publishing Pages to the filesystem. There are a couple tutorials out there explaining how to do this for ComponentPresentation and for a custom type, but not how to do this Pages. There are a couple of interesting points with this exercise that aren’t really explained elsewhere, so I thought I’d highlight them with this post. Also, some copy-paste boilerplate code should be handy.
Myself and fellow MVPs Alex Klok, Angel Puntero and Mihai Cadariu came up with an open source framework for Client-side templating during the recent MVP retreat in Portugal. Apart from giving us the chance to mess around with some fairly new technology I like to think that we were putting some solid thought into an area that I expect to see more and more traction in Tridion implementations in the coming couple of years.
This post talks through my thoughts on why you might want to execute templates in the browser, and describes the elements we pulled together for our framework. Continue reading