I've had a blog on MSDN.Microsoft.com ever since I started at Microsoft in 2005 and I've just recently migrated to my own website for lots of reasons. This article explains why.
Wednesday 28 Nov 2018
This article was written on GitHub. You can raise issues, create pull requests or even fork the content... its open source
I started work at Microsoft in 2005. Some of you may not have even started school at that time, which makes me feel either very old or very experienced depending on my mood!
I have maintained a Wordpress blog at https://blogs.msdn.microsoft.com/martinkearn/ ever since I started at Microsoft and have published many posts there over the years covering SharePoint, Office, Windows, Azure, AI, Bots and a bunch of other stuff.
My most popular post has always been about configuring Kerberos for SharePoint 2007 which I published in 2007 and has had over 225,000 views. I have no idea why, I was completely blagging it and have never really understood Kerberos to this day!
In this article I'l explain why I decided to move my blog, how the new system works and why I think it is better.
I've just finished the initial phase of a project to migrate my blog to my own website: http://martink.me/articles which is hopefully where you are reading this now.
I've migrated the past year's worth of content and will continue to migrate the historical content over the coming weeks.
Going forward all new content will be hosted on MartinK.me.
So why did I move away from a Wordpress blog hosted on one of the worlds most well known domains (Microsoft.com)?
There are three big reasons why I moved my blog:
When I started my MSDN blog in 2005, most blogs were exposed as RSS feeds. You'd subscribe to feeds you are interested in via an RSS viewer application. When an article was published, the RSS viewer would automatically download the content to your device and alert you so you can read it.
I don't think people consume content like this any more.
The way people subscribe to content now is via Twitter, YouTube, Facebook, LinkedIn etc or they discover content via Search.
In recent years, I've generally published an article and then tweet'd it so that my followers hear about it. I've then relied on Google and Bing to make it available to folks that are searching for answers that my articles may contain.
A lot of the technical features that an blog system provides are now redundant which means that blog content is really nothing more than regular web content now. This aligns well with SEO guidelines from all major search engines that you should make sure your website has rich, impactful content.
I've always felt that my articles are slightly disconnected from the rest of my content which includes details of talks, presentations, contact details etc. I've wanted them to be in a single location for a while and now they are.
For the past few years, I've used GitHub as my main authoring repository for all my blog articles. I do this for several reasons:
I have to credit my friend Martin Beeby who originally came up with the idea of using GitHub as a sort of CMS for blog content. I've not used any of his code, but have stolen his idea.
Writing in Markdown is great from an authoring perspective, but at some point the article needs to end up as a HTML document which is readable in a browser
To address this, I built a serverless system for exporting content from GitHub and making it available on my website. I'm planning a much more in depth article (or series) on how I built this system, but in general it follows these steps:
I'll write more on this in a future article.
The way we consume long-form content has changed and a lot of traditional blog functionality is no longer needed.
Going forward, all my new articles will be hosted on http://Martink.me. I'll slowly migrate historical articles too.
The underlying system for my new GitHub-based content management system has an interesting serverless architecture which I'll write about in the future.
All my articles are written and managed as Markdown files on GitHub.
Please add an issue or submit a pull request if something is not right on this article or you have a comment.