A fancy CNAME and Jekyll layout might make your "blog" look professional and polished but that is subjective to the readers, and they won't add much to the content.
A simple github repo + README.md is quick, flexible and easy to maintain for years in the future. We can leave the style to GitHub guys. :-)
As the author of content, I want my content to utilize best practices and publication standards so that it has the best chance of getting read and distributed.
A "simple" GitHub repo ReadMe isn't going to have any of the right tools for sharing or distributing content, it won't allow you to capture signups, or A/B/n test; doesn't even allow you to put in analytics to see if people are reading your content, you can't build domain authority for your other work... It's pretty much the modern equivalent of stapling your flyer to a telephone pole.
You'd be better off with a properly configured WordPress, or other CMS-based, site.
There have been a bunch of posts today about scanning content, but here's a great pre-launch checklist. Do as many of these as you can, as fast as you can. Ha.
A simple github repo + README.md is quick, flexible and easy to maintain for years in the future. We can leave the style to GitHub guys. :-)
Here is an example:
https://github.com/steam-maker/steam-maker-forum/tree/master...