I'm Bluffing

Introduction This page is meant to provide insight into what tools are available in an ootb installation of Sitecore with regards to specific administrative tools decoupled from the actual Sitecore Content Management System. * Update * - When you read through this document be sure to check out the update on more recent versions of Sitecore here:  http://kverheire.blogspot.be/2016/02/sitecore-hidden-gems-updated-admin.html These can obviously be expanded upon by installing additional modules and/or related tooling that creates new functionality in this Admin section. The pages described below are made available under the webserver that provides access to the "/sitecore/admin" URL. In other words : "http://company.domain/sitecore/admin/tool.aspx". Make sure that the aforementioned URL is protected and not accessible from the web or at least correctly shielded through authentication with Sitecore since a number of the tools described below can divu...

Multi-Site setup with Sitecore Sitecore is in my opinion one of the easiest CMS's out there to facilitate a multi-site setup. It offers a number of approaches to doing so. You can either create entirely different structures and implement it as such so that through security and configuration entire different structures can be disclosed while at the same time specific content can still be shared in one location. But you can just as easily decide that a specific node within your website should function as a seperate site with its own visualisation and behavior. For example, you might want the following structure within Sitecore : " Corporate Home > Tertiary pages > B2B > Support " to be disclosed under the following url: http://www.corporate.com/support/ In order to do so I tend to revert to the Virutal Site setup that is available within Sitecore How-To Siteore configures its mapping of the various path, hostnames, databases and so on thr...

Case A web editor has created a large amount of content that is ready to be published. However, in order to get the final 'OK' on this newly created content, he needs to get the buy-in of specific persons in the company. The default answer here would be to use the Sitecore preview mode or use well devised workflows within sitecore that are automatically notifying the correct group of persons by sending mails or updating their RSS coupling (in outlook for example). These notifications would in turn push the stakeholder into taking the right actions needed to ensure the content gets published in the correct form. However,  what is the best possible approach if your target audience has no knowlegde whatsoever of Sitecore? Users that don't have an account and can not (or should not) be motivated into adopting your well designed Sitecore content approval approach ? At that point the Sitecore Live Mode can come into play and offer a relatively elegant solution. ...