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.
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.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.
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.
Case in point -- this parody account that was shut down by Github (http://www.theregister.co.uk/2013/12/19/feminist_software_fo...) without any legal need for the same. You may think today "Oh, that's fine, they were assholes anyway", but in principle, the same thing could happen to you tomorrow if your blog conflicts with the Github values du jour.
Blogs are the simplest thing in the world to host - a $5 VM at Digital Ocean or similar all but eliminates any censorship concerns, and a static generator like Octopress ensures that you have an easily-rehostable backup of your words in case of the contrary.
Everybody laughed, I pulled out a lot of my hair, joking about sexist hammer and homophobic wrench. I can see why GitHub didn't feel like hosting a troll fest.
If it's leading to a "trollfest", then that is a separate problem. Taking down the repo is not the solution to trolling.
http://blog.hubpress.io/2015/02/06/HubPress-a-web-applicatio...
However, HubPress is powered by Asciidoctor (http://asciidoctor.org) which provide a compatibilty with Markdown : http://asciidoctor.org/docs/asciidoc-syntax-quick-reference/...
Prose is beginning to pick up after it changed maintainers, but there are still some hangups such as image upload that need to be fixed.
My solutions are called potion (discontinued) and Sazed (assembly.com/sazed)
https://github.com/msravi/msravi.github.io/blob/master/hubpr...
In your case :
{ "meta": { "username": "msravi", "repositoryName": "msravi.github.io", "branch": "master" }, "theme": { "name": "Casper" } }
""" AuthServices - login error Objecterror: 404path: "/repos/undefined/undefined"request: XMLHttpRequest__proto__: Object__defineGetter__: function __defineGetter__() { [native code] }__defineSetter__: function __defineSetter__() { [native code] }__lookupGetter__: function __lookupGetter__() { [native code] }__lookupSetter__: function __lookupSetter__() { [native code] }constructor: function Object() { [native code] }hasOwnProperty: function hasOwnProperty() { [native code] }isPrototypeOf: function isPrototypeOf() { [native code] }propertyIsEnumerable: function propertyIsEnumerable() { [native code] }toLocaleString: function toLocaleString() { [native code] }toString: function toString() { [native code] }valueOf: function valueOf() { [native code] }get __proto__: function __proto__() { [native code] }set __proto__: function __proto__() { [native code] }app.js:3544 (anonymous function) """
You can create a other github account and give him access to write on your repository, it's a kind of workaround if you want to keep the 2-fact auth on your main account