This is probably very obvious (and it should be - it's a clickable link in the Orchard UI!), but I had to go off and ask Google if there was a way to preview a blog post I'm writing. It turns out there is (and it's been in Orchard for quite a while).

I manage a website with multiple blogs and this issue brought to my attention that on the admin summary for a blog (not a blog post) it displays comment information that doesn't actually work. To be honest, I had never even noticed that it displays any comment information at all. After initially flicking this off as a useless feature and we should remove the broken code from the comments module (I still am leaning toward this not being needed for core), I actually figured that this could actually be a pretty cool feature so I threw together a little module for it. You can grab the source on GitHub.

In my other blog I've been writing up recipes for years now, albeit with varying frequency, with a combination of recipes I've found and tweaked and recipes that I've created from scratch (the latter are fewer and further between, more refinement time is required to get them right!). When I started looking at the Google Search Console for my site, one of the things that jumped out at me was a section called "Search Appearance" which contains two interesting sub-sections, "Structured Data" and "Rich Cards". These basically feed off additional metadata and are part of what allows Google to customise how it parses and displays different types of content. 

Things I've read recently that I want to keep track off, and perhaps comment on slighty.

When you have hundreds of tenants and you need to find the database or media folder etc. is always a pain. This super simple module just displays the tenant name and datatable prefix in the admin. Grab it from GitHub

Easily extracting .nupkg files with WinRAR

The steps involved in publishing a module to the Orchard Gallery, as documented, are somewhat out of date as trying to follow them didn’t match reality, unfortunately. As I’ve just gone through the process of publishing a module, I’m documenting the steps involved in the process so that (a) when/if I publish another module I can follow them, (b) others might find this and have an easier time of it than I did, and (c) once I’ve got the steps documented here, I can look at updating the Orchard documentation itself so that it reflects what’s actually there (i.e. my blog will be a first draft!)

As promised in my first post about writing a custom Condition for Orchard, I've published the source code to GitHub and the Orchard modules gallery: