There seems to be an increasing enthusasim for static sites recently. If you're not familiar with the term, a static site is one that consists only of resources that can be delivered directly to a client such as HTML pages, images, CSS files, etc. In other words, static sites don't require any sort of compilation or interpretation on the server. To satisfy this interest, many new static site hosts have sprung up. These hosts specialize in delivering static sites without any ceremony quickly and efficiently, often by pushing some of the resources to geographically distributed content delivery networks or otherwise optimizing delivery for static resources. Perhaps the most well known of these hosts is GitHub Pages. I recently moved this blog and my other sites such as Wyam from there to Netlify, another such host. Normally a site host change wouldn't really be cause for a whole post. In this case, however, I feel that spreading the word about Netlify may help other folks who are looking for a good static site host. I swear this isn't a sponsored post or anything (though they do have an awesome free plan, so I'll admit to an interest in paying it forward).
I recently launched a new static site generator, and I figured what better test of whether it's ready for widespread use than to convert my entire blog to use it. Given that this blog was originally built with ASP.NET MVC, it should be a good fit for converting over to a Razor-based static site generator. The process was actually easier than I thought it would be and suggests that Wyam is already ready for production use on personal sites, blogs, etc.
It's been a little while coming, but I'm finally launching my new blog. It's built from scratch in ASP.NET MVC. Why go to all the trouble to build a blog engine from scratch when there are a gazillion great engines already out there? That's a very good question, let me break it down for you.