+1 to Nuno's point, the instructions, examples, and access to someone that's done it before makes training well worth it.
SDL Tridion Compound Page Templates are not written in C# alone, but use a combination of Template Building Blocks. Template Building Blocks (TBBs) consist of a layout part (typically DWT) as well as C# TBBs.
Alternatives
Template approach depends on the developers, development process, and available technologies. I've seen programmers struggle with Component Templates, not because of Tridion, but simply because of the languages involved. Be sure to get a good fit for your customer.
XSLT Component Templates may make SDL Tridion's inline editing features harder to implement. Though you have the flexiblity from XSLT's <template match="">
, you lose some things you get "for free" such as:
- resolving links and publishing binaries
- a programmatic content model and access to the Tridion Object Model (at least at the CT level)
- the package
- separation of code from content
An alternative would be Compound Component Templates (modular templating). But again it depends on your environment.
Resources
- SDL Live Content has high-level background information and examples. The first page and diagram under SDL Tridion 2011 shows the big picture and extension points.
- SDLTridionWorld.com is another excellent resource for examples and descriptions, customers also have access to the API documentation. The forum especially has a lot more examples for XSLT CTs than StackOverflow (for now).
- The community-driven Tridion Cookbook has examples and explanations as well, but across the entire Tridion API stack.
Reach out for training through SDL.com.
Basic Introductions
I've written some basic introductions and example for XSLT CTs and C# TBBs, but these aren't a substitute for training.
You mention being familiar with XSLT, I find using basic XSLT functions to help understand component details.
I've attempted the excercise Nuno describes as well (video included).
The biggest risk in skipping training, IMO, is getting either BluePrinting or the content model wrong. Definitely come back to ask questions as you go along.