Few weeks ago I was working on a sitemap implementation for a website still using Sitecore 8.2 and I decided to use one of the available modules on the Sitecore Marketplace. I chose the Sitemap XML module because I was already familiar with the tool and I had already verified that it was compatible with this version of Sitecore.
An important requirement, that I was looking for, was the ability to exclude all pages not accessible by anonymous users from the content of the generated sitemap file. It doesn’t make sense to have a search engine to crawl restricted pages of a website, if the content of the actual pages is secured and accessible only by authenticated users with specific roles. The search engine would just crawl the login page or a “no access” page where the web application would redirect the crawling bot to.
Have you ever experienced a blue screen of death on your computer? Probably yes, nobody is immune. IT systems that host a Sitecore website are not different and they are vulnerable to failures too. The impact of downtime can be devastating for a business, causing loss of revenue and loss of traffic, and damaging a company’s brand image as well.
Have you ever had to implement a custom routing for a Sitecore website? Sitecore has its own default mapping logic between an incoming web request url and a specific Sitecore item in the content tree. Few days ago I had to customize this default behavior and implement a custom routing to satisfy a particular request of one of my clients.
In my first blog post I am going to describe my approach to setup a Jenkins job to remotely synchronize Sitecore items with Unicorn. Continue reading “My Jenkins Setup with Unicorn”