Friday, August 10, 2012

Extending the Content Manager

After a long time of silence I will start blogging about the different extension points of the SDL Tridion Content Manager.

Some of them are well documented, others are not, but with all of them there are best practices and issues to solve.

With this series I hope to share my knowledge with you, and help you get started. When you have questions, don't hesitate to ask for help, but please ask them on StackOverflow! Then your question, and its resolution immediately helps the entire community.

On the topic of community and knowledge sharing, I would like to take the opportunity to encourage everyone to commit to the proposed SDL Tridion Q&A website for Developers and Administrators on StackExchange Area 51! We’re currently (aug 8) at 66%, so we can use all the support we can get.

That said, let’s move on to the first extension point in this series, Search Indexing Handlers.

Extending the search index is a so called undocumented extension point. These points are not necessarily or primarily designed to be an extension point in implementations, but never the less the SDL Tridion architecture does allow it to, in practically the same way as the default elements of the system are implemented.

These extension points include:

  • Search Indexing Handlers
  • Resolvers
  • Renderers

Besides these points, Application Data is another useful feature to support you writing extensions.

Let me know when you have any topic suggestions or feedback on the articles.