a Tridion an SDL Web developer, you’ve very likely converted a single block of HTML design into appropriate Tridion Building Blocks. The idea of breaking a page into types of content, represented in Tridion as Component Presentations, is not new to you. But have you “sliced” a Component by sets of fields?
A few months back, Damian Jewett, explored the idea of multiple Template Layout Building blocks. I’m following up with a potential use case for this approach along with a parallel idea with Component Templates instead. We can call this slicing, where we have a consistently used subset of fields out of a collection of Component fields.*
*I first heard the term “slice,” in a slightly different context, from a French design agency after they learned how Tridion worked.
First read Damian’s post. Continue reading
I’m sure this is well documented somewhere, but I couldn’t for the life of me find it, so I thought I’d try to save someone some time and frustration.
Most people have probably used a WebDav URL to reference a Tridion object sometime in the course of their development. WebDav URLs are usually of the format:
/webdav/030C Account Center Content/Building Blocks/Content Continue reading
To be honest I had been a bit lazy. In all the conversations I had had on the subject of editing AJAX loaded content with Experience Manager I had been told it could not be done, so I didn’t even try. Until Jaime told me it was possible and I found out that its not even difficult. Continue reading
This post briefly introduces some tools for getting accurate estimates of running times for publishing pages when optimizing templates. There are certainly better ways to measure page publishing time than with a stopwatch!
My current project has the ambition to use almost every aspect of the SDL Web suite of products, from plain old Tridion through Audience Manager, SDL Mobile, SmartTarget and finally Campaign Manager – and of course all working via Experience Manager, to provide inline editing and contextual preview.
When looking at how these integrate, all roads lead to… The Ambient Data Framework. SDL provides a number of off-the-shelf cartridges which have varying degrees of mystery – this post aims to clear the mist and describe a little bit more than you get from the docs.
The whole idea of the reference implementation was to make your life (the life of a SDL Tridion developer) easier. But sometimes people make mistakes, and then the end result can be slightly more difficult than it was intended to be.
This blog post is not so much a confession of what I did wrong, but more intended to help you see how easy things can be changed when the tool you use was designed to be simple and modular.
After writing my post about having fun with experience manager last year, I think it is time for a small update. This time I’ll keep it short, but we will have even more fun with XPM!
Today’s story about the People website publishing an obituary of Kirk Douglas death (he’s still very much alive) made me instantly think of two things:
1. It’s amazing these websites have content like this backed-up and ready to go.
2. They should have been using Tridion, there’s a load of ways in which this could have been prevented.
So whilst I’d like to talk more about the content strategy around number 1 (it’s actually quite brilliant and I wonder who else is already written up), I’m going to be talking more how you can save yourself this embarrassment using SDL Tridion.
The SDL Tridion Reference Implementation (TRI) comes with out of the box controllers for loading and rendering pure content-based models. However, most web applications need to blend content with data from other sources before rendering. TRI is designed with this in mind, this post introduces the pattern for creating custom controllers which merge CMS managed content with external data.