We recently rolled out a new Sitecore implementation where GeoIp was used. I'm proud of this one because we developed a neat geospatial lookup with caching that was quite efficient. All went well through QA, UAT, and even Production environment testing. Once live though, it was a different story.

Out of all the Sitecore projects we've rolled out, I've never had an issue around hard drive space. Our latest client launched their MVP phase a couple months ago, and to my surprise I got a drive space alert in Azure Managed Cloud. After a few checks it turns out the mediaIndexing folder is the offending party, and at 150gb+, that's a big offense!

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.

Apologies to all who have been messaging me over social media, looking for some feedback on an article or guidance here or there. I've contracted a virus and it's been about 3 months now of bedrest, tests, hospital stays, and a 9-1-1 call just to spice things up (no, really, I needed an ambulance). With Covid it's not easy to get help, and I've been tested for that sucker more times than I care to share. I'll be posting again with a couple light articles before a full return to work.

A common question I get from new Sitecore Authors, is, “What will this page's URL be? The Sitecore Content Editor provides Item Path, and that can be enough at times, but leaves a lot to be desired. A multilingual implementation for instance will use Display Name and even at times a different domain. To help with this I created the Published Page URL Module, which will provide your content's calculated, final URL in the Content Editor interface.