Tridion Developer Summit 2014 – part 2

In this follow up post I mention 3 other sessions of the afternoon of the TDS.

Lightning Talk Sessions - Ingmar Umans - Stop!


This lightning session from HintTech colleague Ingmar was about better interpretation of the customer needs: ‘STOP building what the customer asks’. We as developers tend to start running in solution mode when a customer is asking you to solve a problem. Ingmar had several good examples in which this could be the wrong solution for the wrong problem. You could better ask the customer ‘Why?, why?, why?’ several times to get to the bottom of the customer business purpose and the real customer needs.

So spending more time in analysis of the customers business / budget / politics / mindset or habits will result in a better project delivery in the end.


There were some other sessions which are also great, but I didn’t take notes of those...

Media Manager Templating: Tips, Tricks and Tools for using Tridion to show Media Manager videos (Frank Taylor)

image Fun presentation about SDL Media Manager. Frank showed us his personal (front-end) experiences with MM and the quirks he encountered. He started with explaining the basic components of Media Manager. In short:

  • Assets: the raw media file (image, video, audio or a generic file)
  • Programs: a collection of one or more Assets.
  • Outlets: the presentation of the Program. This is something like a Tridion component template
  • Distributions: the combination of a Program and a Outlet. This is published and used by the end user.


After showing the various options that MM have for each components, Frank showed us multiple ways of putting videos on a page. Some links:

Frank has shared his html-based presentation on his site:

Automated unit testing of assembly template building blocks (Bjørn Van Dommelen)

Embedded image permalink

This session from HintTech colleague Bjorn was the last of the day, but very interesting! Bjorn showed us another way (than Dominic) for unit testing the Tridion Building Blocks by faking Tridion using a Custom Rendering Engine. This enables us to do unit testing without having a full SDL Tridion installation on a developers machine. The (test) data still comes from an external Tridion database.

The presentation showed us the requirements and installation steps for enabling such a setup:

  • setting up app.config with a valid Tridion config
  • copying of required .xsd schemas from Tridion installation
  • copying of required assemblies from the Tridion GAC
  • don’t forget setting up TRIDION_CM_HOME environment

After explaining all the details of his endeavors, he should us that it works like charm. Important to note: Since it’s not supported by SDL, it could be that every Tridion version 2009, 2011, 2011SP1 can have different obstacles to overcome.

The presentation and code used during the demo is available on Github.