I was recently asked about setting up a campaign in Sitecore and having it go live at a specific time. It's not overly obvious in the documentation since you need to combine versioning and publish restrictions, so we'll go over it here.

In the last article I introduced the Sitecore Auto Dictionary Module, explaining the benefits of using it over the out of the box Dictionary. Today I'll talk to those who are interested in the technical approach to this feature, covering the configuration and use of pipelines it employs.

I'm excited to release this module, because it has the power to save your team a great deal of development time. By using this in our last Sitecore project I saw a reduction in 220 hours of overall effort, which besides the cost savings incentive, gave us a big win by making things easier for the developers and content team. Introducing, the Sitecore Auto Dictionary!

Ok so you have your page templates created, and standard values are set up so desired components are default. Pretty standard stuff. So, what happens when you're using dynamic placeholders, sometimes many at once, and you want to have components in each in the template? It's a simple trick, so here we go.

To remove an item from your site you need to first publish it as unpublishable or publish its parent with all subitems opted in. We'll go through these steps plus a way your Administrator can help you if all else fails. 

With any project there comes a time when we grant access to the client's authors. I guess that's the whole point of a CMS, right? But during this transition period I always keep an eye on the Content Management instance's performance to ensure everything is running as it should be, and excessive publishing is a common issue we have to address.