A relatively unknown feature of the Tridion CMS product is the GUI extensibility framework.
This is actually a fantastic feature which allows us to create and supplement the user interface with just about any type of addition we can think of.
It is pretty unknown because of the lack of documentation but with a little bit of investigation work it is possible to find all sorts of treasures we can use to extend the current GUI.
Here’s one example that is already available on the SDLTridionWorld website’s Community eXtensions section: “Republish from publish queue”, this nifty extension gives users the ability to republish items directly from the queue instead of the normal way of locating the item within the folder or structuregroup hierarchy.
The extension framework is quite robust (not without limitations of course) and allows us to add toolbar items, context menu options, tree nodes or simply run scripts that can do just about anything.
In this article I’m focusing on the latter, adding a scripted extension to do different tasks.
jQuery’s CSS selectors and methods for DOM manipulation are exactly the tools to help us create Tridion GUI extensions quickly and with relative ease.
The way the extension framework is built allows us to create a jQuery extension that can be reused by other extensions.
Continue reading “Using jQuery for Tridion GUI Extensions”
Quite a while ago I internally blogged about creating a custom Sitemap provider in ASP.NET. Even though its been a while I believe its still relevant, especially the SQL caching example I added. Hopefully you can still get something out of it.
With ASP.NET 2: Microsoft introduced a few services which are built on top of the provider model.
Services such as the membership or sitemap rely on providers to supply them with the actual information. All the providers are derived from the ProviderBase class.
The default Sitemap provider is the XmlSiteMapProvider which is used by ASP.NET to retrieve the website’s navigation structure stored in the Web.sitemap file.
The cool thing about this is that we can easily extend these providers if we need different functionality than what Microsoft provides. So As long as we keep inline with the providers’ interfaces the services will work with our own customizations just fine.
A benefit of creating a sitemap provider that reads from a database should be obvious: Its pretty easy to add custom navigation where needed to new or existing sites by reading ready information from our application data store. The information in many cases will already be structured in a hierarchy so its easier to retrieve it for a navigation structure. This allows us to create the main site’s navigation, breadcrumbs, or specific structures for different sections of our site in a pretty easy way to implement, no need to write additional files on to the webserver’s file-system and the caching mechanism shown in this article gives a boost for performance.
Continue reading “ASP.NET Custom Sitemap Provider”
In this article I would like to concentrate mainly on extension objects; a little bit on what they are and how to make use of these in conjunction with the XSLT Mediator. Continue reading Implementing the XSLT Mediator – Part 2