When mass publishing content from Tridion, the publish job is handled as a single transaction. Using the Alchemy Page Publisher plugin it’s possible to perform this task but create single items for publishing.
After the jump I’ve created a short video to demonstrate this functionality.
We’ve been quietly releasing some new plugins over at the Alchemy Webstore. As part of those releases I’ve made some quick demonstration videos as it’s far nicer to watch a video showing how to use a plugin than reading the description 
To crack things off, after the jump we have the first in the series dedicated to generating Tridion documentation automatically.
As announced by SDL earlier this week – it’s here!
Just in case you’re week’s still too busy to read the full-monty here’s a few snippet to highlight the main ‘changes introduced’ in this new framework:
One of our clients uses Tridion 2013 SP1, and has strict audit requirements for their publishing. We need to know what is on the site at any particular point in time. The auditors might ask, for example, what the user saw if they viewed the site two weeks ago last Tuesday at 3am.
We have to track what gets published, and make sure that we have no significant performance degradation while we’re doing that. Publishing for our releases already take several hours, and we can’t extend that by any significant amount of time.
These tests let us look at different options for this timing. Once the tests have been run, we will then have a better idea of which one to implement.
With a number of versions of SDL Tridion, SDL Web (and soon to be SDL Tridion Sites) out there with Alchemy users, our latest version of the plugin development framework contains some major updates for the core service.
Many of us are familiar with GUI extensions in SDL Web, as well as Alchemy plugins, which integrate into the GUI via the Aguilla JavaScript framework. With SDL Knowledge Center, the story is a bit different. At first glance, Knowledge Center appears to have a GUI very similar to Web’s, in terms of look and feel. Under the hood, however, it’s implemented differently. There is no Anguilla. Anguilla is more of a Tridion thing. And from my experience, the concept of a GUI extension does not really exist in KC. There is documentation on plugins and extensions. But there is no clear, simple approach to extending the GUI, as far as I can tell. In this post, I outline a simple technique for extending the GUI functionality of your Knowledge Center implementation.
This small blog post isn’t really something Tridion-specific. However, with SDL Web 8, installing or configuring the CMS or content delivery usually involves running a few powershell commands. Usually, we run these commands to install a database, or to create a topology, or install or manage the microservices.
The last few versions of Alchemy have allowed you to update it’s software directly within the CMS.  As we make improvements to the API and new functionality, it is key to update to the later versions.  To show you how simple this process it, i’ve made a quick recording to walk through the process.
With the advent of SDL Web 8.5, we’ve seen many nice improvements to the software. We’re able to move items in the blueprint hierarchy, we can now set up a whole content delivery environment with a number of powershell scripts, … but in our most recent upgrade, we’ve found a big problem.
