Ok if that title isn't clear enough, let me try again. Our new site has a dedicated domain for each language, so we need to configure the language switcher to point to a FQDN instead of a relative path. There are a few ways to do this, like using configs, but I'm going to show you show to manage this using the site's root node. We're going to also redirect to the right language when context isn't available using IIS.

Sitecore won't handle a page request as a 404 if the context language is missing. So, what this means, is your Users will just see  a blank page should the item exist in English but there's no French version, and they're requesting the French page. We need to override HttpRequestProcessor and  ExecuteRequest to make this a friendly experience for your Users. Let's get started!

A good development team will always work to ensure Experience Editor is the preferred method for authoring a page's layout. Of course, this isn't always possible, so our clients need to know how work with Placeholders in the Content Editor, and the module Placeholder Dropdown is a good step in the right direction to improve this experience.

Today I was adding a project to our Helix solution, and was a little surprised to see the instance break after first deployment. The fix was simple but nowhere near straightforward.

Sometimes you don't have time to deal with problems and you've just gotta have a running instance of Sitecore. Today we had some certificate issues with xConnect that appeared out of nowhere, so after some time troubleshooting, I decided to remove the requirement, since we've already locked down network access to it. Temporary and non-Production, and in other words, nail meet hammer.