Can you explain what barriers are you talking about? I moved from a CMS to static blog only to reduce these barriers. For me, a new post is just three steps
$ hugo new <post>
$ vim <post>
$ git commit -am "new post" && git push
which is something I vastly prefer as I am in my text-editor. Even the live preview is easily made possible with livereload (pre-built in Hugo).The best use-case of hubpress, IMHO, is when I want to publish from mobile (or when my dev environment is not unavailable)
[0] - http://gohugo.io/
1. Start Emacs (I could use something else here, but I like Markdown mode)
2. Start eshell and run:
$ raco frog -n <title for a post I may still have in idea stage and don't know what to call it yet>
$ find-file _src/date+title.md
3. edit template tags.
4. write post.
5. save post.
6. run:
$ raco frog -bp
7. check the preview and make sure nothing's broken in the formatting
8. push to git.
9. check again and make sure nothing broke now that it's actually hosted (this has happened a few times)
It's not a huge burden, but it's occasionally a pain and the roundabout steps involved, and the weird bugs at times in code-block rendering, get a little old when I compare it to: 1. Click link to Blogger/Medium/Tumblr/ello/etc.
2. Click "new post"
3. write post.
4. preview/publish post. * A text editor, where I write the post
* A terminal, where I commit/push my changes
* A web browser, where I preview my changes
The constant switching between contexts makes it harder for me to focus. Of course, there are advantages (I can now write on the train and push everything afterwards), but I do feel the difference.The only place users have accepted a single tool for a single role seem to be mobile apps, because the interface is so limited.
At least that's my impression...
docker run -i -t -p 127.0.0.1:8080:4000 -v /home/xxx/xxx.github.com:/data kisenka/centos6-jekyll
HubPress seems interesting, but I do not want to give them my github credential.
I will push sources at the end of the month or in the first half of march.
In a nutshell it lets you email your blog, parses it and resizes attachments, interprets links (with plugins) and will also commit it to git and push for you. With guard you can autotrigger rebuilds as well.
I have Dropbox running on the server side. So I can edit files locally and they are immediately pushed to the server.
I might consider it without git, but Jekyll is really essential for me.
It's a minor inconvenience, but it's one that's been enough on more than a few occasions for me to just say bugger it and post my thoughts elsewhere or just not bother.