Understanding TOM.NET Before Using TOM.NET

Coming from a mix of business analysis and ASP.NET development on the content delivery side, I've typically looked at the Tridion Object Model's API as that "next hard step" in my technical development and understanding. 

After working with it a bit more, I realize my hesitation was unfounded. As my colleague, The Huizard, might say, "it's just an API." Though he was actually referring to the Core Service, functionally-wise, the Content Management APIs, tools, and editors follow the same underlying rules (more or less--feel free to share your favorite "gotchas" in a comment below).

So if you understand this...



And this...

Then with some practice, TOM.NET, the Core Service, or even Content Porter are not as challenging as they might appear. Especially if you consider the Content Manager Explorer has used the same APIs to do its work (now fully through the Core Service in SDL Tridion 2013).

Understanding the separation between managed content and display or between the content management system and content delivery is key to understanding Tridion functionality. I also suggest that understanding Tridion functionality forms a strong starting point in understanding its Content Manager APIs.

You're Too Close to Your Expertise

I'm surrounded by highly-qualified, problem-solving coworkers and friends that are sometimes blind to their own strengths and expertise. I think we have more to share than we realize.

A theme my company promoted this year was "Climb Higher." I like how the phrase evokes a challenge, we're scaling scenarios and reaching new heights. Maybe with all this work, I'll lose some of the "consultant gut" my technical account manager jokes about.



I'm ready to climb! But I also want to be sure we don't become victim to the "curse of expertise" by losing our audience. Should we chase expertise while ignoring what we already know and what we can individually contribute?

I'll Share When I'm an Expert...

I'm seeing this less among my immediate peers. Most share when they can and have ideas on what they'd like share. The challenge now is finding/making time or narrowing down topics (to which I point out you're already answering and helping customers all the time).


False Dichotomies...

It wasn't until one of my colleagues admonished me to "never apologize for not being technical" (guess who gave those encouraging words) that I started noticing Tridion expertise isn't all or nothing. It's not even functional versus technical. There are so many aspects to content management, in general, that it's challenging to really know it all (my post on the seven places for markup hints at this).

The landscape looks more like this, which means there is a lot of room to share what you know that others might not know.

Don't Shrink the Ring of Online Expertise!

Combining the two ideas from above, inspired this visual. As we each progress in our careers and development, we may forget what was hard or challenging. We may never be satisfied on the autodidact's path, but you know people need what you know every time you get those same basic questions specific to your expertise.

Rather than waiting to share deep knowledge and expertise when you're ready, maybe it makes sense to start from where we are? Or even better, start from where your audience needs you?


Climb Higher by Making the Climb Easier

So rather than just climbing higher, let's leave hints and guide posts behind for those that follow our paths. Or better yet, let's construct the easy paths ourselves and that we wished we had when we started.


Let's continue to craft an easy-to-follow landscape. Let's go higher not just not by climbing, but by building or growing mountains.

These cartoons were inspired by Dan Roam's Back of the Napkin (I know I should have done drawings instead), which was mentioned in The Art of Explanation (another excellent, recommended read). I'm using the SDL Buddy as a stand-in proxy for Tridionauts (Tridion practitioners), but any icon representing a member in your community will do.

Places to Get Started with SDL Tridion GUI Extensions

I was asked today how the PowerTools group learned about the client-side API (aka Anguilla) for SDL Tridion 2011 GUI extensions. Much of the PowerTools base functionality was created by key members like Peter Kjaer and Albert Romkes with input from several contributors as described in June 2012 and February 2013 Tridion Community Webinars.

Others (mostly Robert Curlette) have written extensive guides and examples for SDL Tridion GUI Extensions, specifically covering the entire setup.

In addition to the API docs, be sure to check out some additional examples from the community.



In case you’re also looking for Core Service examples, check out a Core Service client example on Yet Another Tridion Blog.

Sometimes I forget that although we have much more Tridion information online, sometimes it's missing a curated touch and context. Have any other useful guides or examples you'd like to share? Leave a comment or better yet, share your thoughts, insights, or examples.

Discover the Power of SDL Tridion 2013

I last made a "training plug" for the 2012 Summer discount (Trained and Untrained). The latest and greatest offer from Global Education is the SDL Tridion 2013 Discovery Course.

Best Parts of Discovery

After having taken and delivered the "bootcamp" precursors to this training, I think the best parts for Tridionauts like you will be:

  • Hands-on practical time with a built 2013 Tridion environment
  • The chance to engage with your favorite SDL CMT consultants (or give your least favorite ones a hard time) :-)
  • Understanding the biggest 2013 features (hint: it's not all technical)
  • Connecting which features will be benefits for your organization or clients

Inspired by this year's and previous Bootcamp sessions, this type of course combines the exploratory free-flow sessions typical of the Bootcamps with the structure and format we normally have in formal training.