I do keep track of “static-site generators”. Yes, I hear about how awesome they are (and less resource intensive), but it transpires that it requires considerable effort to write a blog post.
Here’s for the context
Creating A Post Directly On GitHub
The other thing is there doesn’t seem to be a spell checker. This is important to me. I’m a horrible speller. I’m so bad that sometimes I confuse the spell checkers in word processors. They just throw up their hands and say, “I have no idea what you’re going for here.” It’s handy to have Mycroft on my desk so I can ask it how to spell words. I can say the word out loud and get the spelling back. It’s that bad. I may have to type out these posts in a word processor and then paste the text into GitHub later just to avoid looking like an illiterate dolt.
What’s the point?
RadOncNotes 
Spell checking isn’t that hard. There are spell checkers built-into browsers and operating systems if you work locally.
The problems with writing directly in a CMS, and in this context GitHub can be as much of a CMS as WordPress, go beyond spell checking.
I’ve tried the static sites and I’m running a test site at the moment, there are problems, but writing a post is not one of them. The main problem I’ve run into is the documentation is written by developers for developers – it’s hard to get a grip on the back end if you are not able to code.
LikeLike