Recently I had the pleasure of traveling to Portugal for the SDL Web Most Valued Professional (MVP) retreat. While this was my first opportunity to participate in one of these events, I have seen the results of having some of the brightest and most willing-to-share minds in the SDL Web community brought together for the opportunity to collaborate. Often times in the past this event has helped to shape the future of SDL Web development, and this year was no exception. Continue reading
In this forth Alchemy Training Video I’ll show you how easy it is to create a popup window for your plugin.
When building a GUI extension it’s best to only show your functionality when relevant, this behaviour starts with the buttons you add to the Ribbon Toolbar and the Context Menu.
If you’ve still not given Alchemy a shot, I’ve created a couple of videos to show how easy it is install (and un-install) the framework within your SDL Tridion / SDL Web Environment.
I’m going to be presenting a session at the Tridion Developer Summit next month that walks everyone through the creation of an Alchemy Plugin, so I thought I better get some practice! I also thought it would be useful to record this practice into a series of mini videos, so here goes with the first video of the series.
One of the features of Alchemy that I think will end up being the most helpful in the future is the way it lets you build a plugin and never have to worry about whether it’ll stop working with future versions of Tridion. This is because Alchemy provides helpful wrappers for the Anguilla framework used to interact with the CMS. If Tridion ever moves on from Anguilla (as has long been rumoured) Alchemy will update the wrappers to support the new technology and if your plugin is using these wrappers you shouldn’t even have to think about it. Continue reading
I’m in the process of creating my first Alchemy Extension that uses custom configuration settings and I thought I’d share some learning as I go as I think it’s safe to say a good chunk of all extensions will use some sort of custom configuration.
As a general rule, installing an Alchemy plugin is a simple one click process, outlined at the Alchemy Webstore. This opens up Tridion to all kinds of configuration by people who would have found the DLLs, XMLs and config files ordinarily associated with Tridion customization off-putting.
But wait! What if you really like configuration and don’t feel like you’ve accomplished anything until you’ve had to update an XML or two? Well, it turns out that Alchemy will still meet your needs, weirdo. You see, some plugins still require configuration, even if it is quite simple. Take DXA Page Preview or Where Used Plus for example. Both plugins include references to settings in their a4t.xml file. This file will always contain a plugin’s configuration settings and will always be found at
So, if you ever find a reference to a plugin’s settings and want to know just what you can configure for a given plugin, check out it’s a4t.xml. Most often it won’t have anything you need to think about, but sometimes you’ll find some important settings there. If you’re developing a plugin and want to know more about using the a4t.xml file, check out the Alchemy documentation for details.