I chose https://jekyllrb.com/ as the framework mostly becase it seems quite popular and looke easy. The blog posts are in markdown which makes the editing very simple. I ended up using http://deanattali.com/beautiful-jekyll/ which has a nice clear readme on how to get it up and running https://github.com/daattali/beautiful-jekyll#readme which amounts to fork the github project, update the url and go.
After the fork, clone the repo local to add posts locally before posting to github.
Once the project is forked go into the repo settings down to the GitHub Pages section. Enter the custom domain, in my case krisrice.io
The gotcha with the custom domains is there’s no option/feature yet to upload a custom SSL cert to accompany the domain. Github will still host the pages but with their SSL Cert which is browsers will flag as a security issue. So best to no reference your new site with HTTPS. There’s a looong list of people asking for this to be built https://gist.github.com/coolaj86/e07d42f5961c68fc1fc8
Up and running
That’s all it takes to get up and running.
The migration mostly just works. I hit a bug in the migrate code because I had some draft blogs that had / in the title of the blog. The problem is that blogger escapes those for published posts but not for drafts. The bug is that in Jekyll the postname is the file name so having a / in that didn’t work out. I just edited those titles to remove the slashes. The Jekyll team is adding a fix for it here: https://github.com/jekyll/jekyll-import/issues/321#issuecomment-331204992
Step 1 - Export Blogger
Export the Blogger posts. Blogger doesn’t make it obvious where/how to export as it’s in Settings -> Others
Step 2 - Migrate
This is just run the migrate code on the Jekyll page.
Test and Publishing
Here’s gotcha #2 always test the post local before just pushing the markdown file out to github. I had an edit that failed on github to publish and all you get from github is the equivalent of an ORA-660, something failed. So always build and verify. https://jekyllrb.com/docs/usage/
There’s a number of Markdown desktop tools like MacDown which I normally use. So far I’ve instead been using prose.io to edit new posts like this one. It’s quite easy to use and posts/commits straight into github.