> because of the barriers involved between writing something and actually pushing it
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)
Like I say, it's a minor barrier, but it's sometimes enough to not feel like bothering with unless it's very important. Every time I want to write a new post I have to:
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.
In my case, the main barrier is switching constantly between environments. When I was using Wordpress, I had everything right there in my browser. Now that I've moved to a static blog, I have
* 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.
Did the Unix philosophy ever win out for end users? As far as the eye can see there's only integration. Microsoft Office is the most popular office suite, Photoshop integrates probably 1000 tools, etc.
The only place users have accepted a single tool for a single role seem to be mobile apps, because the interface is so limited.
Mine get run on my VPS, launched by a git hook. But from what I've read, there are a few more "full featured" online editors like Nitrous.io which actually have a backend which can run such tools.
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
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/