Last week I attended TDS 2014. It’s the first time that it has been organized, most of it by Robert Curlette. Great job! There was a huge reply of the community. Some stats of TDS:
- 85,753 miles travelled
- 17 speakers
- 12 countries
- 45 companies
That’s pretty impressive for a 1st time conference, wouldn��t you think? Everybody had a good time and enjoyed in-depth sessions given by developers from the Tridion community. Below my impressions, notes and links.
The day started with a welcome speech and after that SDL announced the new MVPs for 2014. Everybody was invited on stage to receive their MVP trophy. Some nice stats about that:
Nuno Linhares from SDL showed the latest Tridion developments and future plans: ‘10 things you did not know about SDL Tridion 2015’. Quick list:
- #1 - You will be able to load AppData from multiple items in bulk
- #2 - We will have a new item type (4096 - Business Process Type)
- #3 - Content Delivery will be able to load configuration from a repository (rather than File System)
- #4 - Content Delivery will expose a discovery endpoint to CM
- #5 - SDL Tridion 2015 will trigger Events on lists
- #6 - SDL Tridion 2015 will allow code to temporarily elevate a user's privilege
- #7 - SDL Tridion will let you create "Site Types"
- #8 - SDL Tridion 2015 will introduce a Topology Manager
- #9 - SDL Tridion 2015 will have a default website and reference implementation
- #10 - Publication Targets will be deprecated in SDL Tridion 2015
Great stuff to expect in the next edition! For more details see Nuno blogpost or slideshare deck. After keynote, there where two tracks with session. Below my selection of sessions I visited.
The quest for Continuous Integration with SDL Tridion (Ryan Durkin and Rob Stevenson-Leggett)
Rob and Ryan from Building Blocks showed us how you can implement CI with Tridion. They used Team City as build server with Nant as task build runner. Nant is using XML for configuration. The basic outline of the CI setup:
- Pre: Build gets triggered by a commit in a Version Control system. Can be anything, like SVN or GIT.
- Build step 1: Build Web. Run unit test. Compile the .NET code that is used as CD application.
- Build step 2: Deploy Web. Deploy the assemblies and related stuff to the Content Delivery server.
- Build step 3: Build Tridion Items. Compile the C# TBBs.
- Build step 4: Deploy Tridion Items. CSS/JS/etc are copied via WebDav. Compiled C# TBB’s are deployed via the TcmUploadAssembly.
- Build step 5: Publish CSS/JS Structure Groups. This was done by a .NET console app that uses the CoreService (tcm-id’s, credentials and end-points where configurable via app.config). Alternative would be to use a powershell script to trigger the publish.
Besides unit tests they also showed some automatic security testing tool called NetSparker. See ttps://www.netsparker.com/communityedition/
Agile Tridion Development (Dominic Cronin)
Agile Tridion development could be anything. Former colleague Dominic Cronin had several topics which turned out to be lot about testing! In one of the first slides he pointed out that there is Tridion Practice hosted on Google Code which offers a collection of useful Tridion recipes.
Dominic also demonstrated T-cubed which is a Tridion Template Testing Framework. The Framework itself can be downloaded as a Visual Studio solution. After downloading, you have to fix the references to the Tridion assemblies. The framework gives you a structured way to:
- modify the content of a package
- make assertions about the content of the package.
In more detail: what T-cubed basically does is that it connects to Tridion via the Core Service. Then get some ‘fixed’ Test component run it against a Component/Page template. After running the outcome is asserted in the unit test by verifying the variables on the package with the coded expected values. Very nice idea. The only downside –if i may say so- that it heavily relies on test components in Tridion, which can be changed and then your test breaks. Also those components ‘pollute’ Tridion in a way, although you can hide them via security. And you probably never content port them further in the DTAP delivery street.
Another demo was about using Selenium WebDriver for creating unit test for web pages. You could instruct the WebDriver to retrieve a webpage by url and then use CSS selectors to dig into the html to search for a certain element and test the value. A nice extra touch was his demo to have a local HTML validator installed and unit test if the webpage was still HTML5 compliant and did not contain TCDL tags in the generated output.
Lightning Talk Sessions - Will Price - Cook up a search with SI4T
The lightning sessions where fast, short & fun. The best example was the session from Will Price.
As a masterchef he showed a nice recipe to ‘Cook up as search with SI4T’. When setting up search for SDL Tridion and Solr it’s a matter of doing things right and in the correct order, so that’s how he came up with the cooking and ingredients:
He shared his complete recipe as a blog post on http://www.tridiondeveloper.com/cook-up-a-search-with-si4t. The SI4T can be found on github.
I will pick some session for the next blog post: TDS 2014 part deux…