10 ms·

GitHub is one commit away from being the ultimate blog engine

168 points by bcardarella 15y ago

I just realized the title might sound like I'm putting down GitHub, that's not the point. I love GitHub.

deleted 15y ago
[deleted]
kellysutton 15y ago
If they put a more consumer-friendly face on it, they could probably go toe-to-toe with many other platforms out there. Not quite their core business, though.
- bcardarella 15y ago
  definitely not their core business, but it seems like it is such a short distance to get there from where things currently stand. And I really like Jekyll and using GitHub to host.
todd3834 15y ago
I don't think GitHub is planning to nor should compete in that market. The Jekyll/blog hosting stuff has been a neat side effect and I am glad that GitHub hasn't gone out of their way to prevent that type of use but I'm sure they have no desire to be a blog engine.
- bcardarella 15y ago
  I'm not advocating that GitHub should compete in the blog space. This is more of a convenience request for the sake of making the most out of GitHub Pages.
- nknight 15y ago
  If I'm understanding correctly, the request may be in the context of blog-like usage, but the function is of much more general applicability. I think he's just asking for the ability to create a new file from scratch in github's web interface.
- nosequel 15y ago
  If they have the talent, time, and funds (they have all three btw), why shouldn't they? The might have not a lot of competition right now, but that will change in the future I'm sure. Any competitive advantage is a plus IMHO. As a developer who uses github everyday, I love that I can use my normal workflow to post to a blog if I so wish.
kam 15y ago
Creating new files from the web-based editor is a little feature that should really be there. There's another good use-case, which I've suggested to them: Their "We recommend adding a README..." message could just link to a markdown editor, making it really easy to put up some documentation.
swanson 15y ago
I started down this path before they even added Ace to the site. My idea was a little bit different: I would drop in a single file to my Jekyll repo that adds a "Create a new post" page on my blog. There is a text field with a live markdown preview and a "Commit" button that would make the calls (via javascript) to the Github API to create a new commit in the repository. This commit triggers the hooks that rebuild the blog. The main hurdle was authentication, since Github OAuth doesn't support any client-side flows (which is understandable since it's not a completed spec, to my knowledge). So I would have to pass my user/pass in everytime. But I got the API calls all working (after Github support helped me get CORS working), but I lost interest in the project and it's just sitting around collecting dust The code: https://github.com/swanson/lanyon/tree/gh-pages https://github.com/swanson/lanyon/tree/gh-pages Demo that doesn't quite work: http://swanson.github.com/lanyon/ http://swanson.github.com/lanyon/
grandalf 15y ago
In other news, google docs is one commit away from being the ultimate blog engine.
daniel_levine 15y ago
While GitHub is great I think it is more likely that DropBox becomes a dominant blog engine. Already there are things like TiddlyWiki and DropPages that do this and it's much more approachable for the average user. I also think as DropBox teams improves and iterates it will be interesting to see more people using Dropbox for basic version control, probably not a good idea but I think it'll happen.
- mmahemoff 15y ago
  Marco Ament (Instapaper) started working on a Dropbox blogging engine, where you can just maintain a drafts directory and copy it into a pending directory. It was discussed on his podcast (Build and Analyze), don't think he's published it though.
- alexcabrera 15y ago
  See my comment above. We've built and launched this at http://droptype.com http://droptype.com. Would love to hear your thoughts.
  - chipsy 15y ago
    This sounds like something I want to use. Some impressions: The first thing I did was edit my profile, but I found that it doesn't give me enough feedback about errors. I tried changing everything all at once(of course) and then got greeted with the previous defaults. It took some trial and error to figure out that it wasn't accepting the RGBA PNG I had picked out for a profile picture. I'd also like a direct link to the markdown formatting docs, or even just a quick summary, on the profile editing screen. My profile finished, I proceeded to look in my Dropbox folder. The README is not formatted for Windows Notepad and appears as one long line of text. I switched to NP++ and continued to write a "hello.txt" containing a link and an image. It shows up, so I go back and edit the README, too. Everything is in order, but what is this "cloud+arrow" button? Inspecting it reveals it's publishing, but I don't feel confident about whether I've published hello.txt until I log out and check. I might continue using this. Some last thoughts: I will probably want options to organize posts. There isn't enough documentation to know if I already have them. I found myself wondering if there was a shortcut for marking up the image that would let me point to a folder inside Dropbox without tabbing out to find the public link. I may not want the displayed title of README to be README.
DanielRibeiro 15y ago
Github's founder Tom Preston Werner had a similar article]1]: Blogging Like a Hacker [1] http://tom.preston-werner.com/2008/11/17/blogging-like-a-hacker.html http://tom.preston-werner.com/2008/11/17/blogging-like-a-hac...
taylorbuley 15y ago
I'm a coder at a big media company. I would die to find a gaggle of people who want to work with me on a simple CMS on top of Git.
- alexro 15y ago
  Who you see as your primary audience for this type of thing? I just don't think developers do CMS a lot
  - taylorbuley 15y ago
    It would definitely have to be designed for the kind of crowd that's never installed Jekyll. As paleolithic as it sounds, I think a CMS build on flat files would be a lot easier to manage than a CMS built on a relational data store. If you don't need accounts and personalization, or can just do that all client side, you could simply load balance across micro AWS instances pulling from the git repo and stick everything behind Cloudfront -- all for a few quarters an hour.
    - wyclif 15y ago
      The CMS on flat files thing has been done before, for example with a Perl script: http://www.blosxom.com/ http://www.blosxom.com/ Nevertheless I think the concept has potential if done right (and with Github or Dropbox).
- endian 15y ago
  I've been wanting to do this. I'm in NYC. I'll be less busy soon. This should be done.
metra 15y ago
A major feature that Jekyll is missing is commenting. Relying on Disqus, a closed source platform, is not ideal because it slows down page load times, does not contribute to SEO, and it does not let you host and search for comments in your git repo. Some people argue that adding a dynamic commenting system contradicts the static html goal of Jekyll. Going along those lines, critics say that a conversation is best carried out on 3rd party sites like HN. However, for technical blog posts specifically, a two-way conversation helps illuminate finer points in the original blog post. Googling around for 'jekyll comments' or 'disqus open source alternative' reveals many people who would use such an idea. However, aside from some quick-and-dirty projects, I see no compelling open source alternative to disqus that will include features such as OpenId, spam prevention, comment threads, etc. Does anyone know of such a project?
- mechanical_fish 15y ago
  Are you thinking of some kind of hybrid system, in which there's a Disqus-like web app to serve recent comments and enable the commenting infrastructure, but the comments eventually (on a timescale of hours) get rendered into static HTML in my git repository for long-term archiving, SEO, searchability, faster page loads, etc? That sounds interesting. My next question is: Does Disqus's API let me do this via... Disqus? Surfing through the API docs suggests that the answer may be "yes".
  - thedz 15y ago
    Yup, the API lets you do that. You can pull our your comments and sync to a local datastore.
    - thetylerhayes 15y ago
      Guide: http://docs.disqus.com/help/58 http://docs.disqus.com/help/58 (though it's already automatic in our WordPress and MovableType plugins).
- swanson 15y ago
  What about a form that lets someone submit a comment and it appeared as a Pull Request in your repository? Once you merge in the change, Github will rebuild your blog and it will appear. That would be kind of cool. Or you could just have a comment link that uses the github website comments - if you are really interested in technical discussion it's probably fair to assume the poster has a github account
freshhawk 15y ago
That's an incredibly low bar to set for something to be "the ultimate". I can smell the fanboyism from here!
mmahemoff 15y ago
A problem with this approach though is you end up having to manage a directory full of files called MyAwesomeBlogPost.html etc. Or perhaps using a date or sequence based prefix to keep them in some order. A little tricky to manage once you have dozens of posts...so you'd want some front-end...but these days, it could be a TiddlyWiki or some other pure JavaScript app based on CORS (like swanson mentions in the present thread http://news.ycombinator.com/item?id=3235457 http://news.ycombinator.com/item?id=3235457)
mwsherman 15y ago
I think version control and content management are complimentary in some ways, but how is serving static files an “ultimate blog engine”? I feel like we’ve had that for a few years. What might actually happen is that Git or Dropbox become the interface through which we “put files on the web”. One’s blog is just a subset of files that one is maintaining anyway. That’s nice, and a consolidation of tools. But not, um, advanced.
- btucker 15y ago
  http://pages.github.com/#using_jekyll_for_complex_layouts http://pages.github.com/#using_jekyll_for_complex_layouts So while it is just serving static files, it's static files pre-processed by Jekyll.
- bricestacey 15y ago
  What might actually happen is that Git or Dropbox become the interface through which we “put files on the web”. There are some tools that exist already. Here is one that I recently discovered. http://www.kissr.co/ http://www.kissr.co/. There was another one also posted on HN recently, I forget its name.
alexcabrera 15y ago
We recently launched an app - http://droptype.com http://droptype.com - that tries to do static site generation using Markdown files over Dropbox. It's still very much a proof-of-concept and we're retooling to make it a bit more full-featured; but the eventual idea is to let you let you publish web content by just arranging files on any cloud storage platform. Again, it's still very early and this is more to prove that the idea is doable, but we'd love to hear any input. We're working on some commonly requested features like customized designs, cname redirection, rss feeds. The idea is to have a very hacker friendly publishing tool that doesn't require very much work to set up.

168 points by bcardarella 15y ago

I just realized the title might sound like I'm putting down GitHub, that's not the point. I love GitHub.

deleted 15y ago

[deleted]

kellysutton 15y ago

If they put a more consumer-friendly face on it, they could probably go toe-to-toe with many other platforms out there. Not quite their core business, though.

bcardarella 15y ago
definitely not their core business, but it seems like it is such a short distance to get there from where things currently stand. And I really like Jekyll and using GitHub to host.

todd3834 15y ago

I don't think GitHub is planning to nor should compete in that market. The Jekyll/blog hosting stuff has been a neat side effect and I am glad that GitHub hasn't gone out of their way to prevent that type of use but I'm sure they have no desire to be a blog engine.

bcardarella 15y ago
I'm not advocating that GitHub should compete in the blog space. This is more of a convenience request for the sake of making the most out of GitHub Pages.
nknight 15y ago
If I'm understanding correctly, the request may be in the context of blog-like usage, but the function is of much more general applicability. I think he's just asking for the ability to create a new file from scratch in github's web interface.
nosequel 15y ago
If they have the talent, time, and funds (they have all three btw), why shouldn't they? The might have not a lot of competition right now, but that will change in the future I'm sure. Any competitive advantage is a plus IMHO. As a developer who uses github everyday, I love that I can use my normal workflow to post to a blog if I so wish.

kam 15y ago

Creating new files from the web-based editor is a little feature that should really be there. There's another good use-case, which I've suggested to them: Their "We recommend adding a README..." message could just link to a markdown editor, making it really easy to put up some documentation.

swanson 15y ago

I started down this path before they even added Ace to the site. My idea was a little bit different: I would drop in a single file to my Jekyll repo that adds a "Create a new post" page on my blog. There is a text field with a live markdown preview and a "Commit" button that would make the calls (via javascript) to the Github API to create a new commit in the repository. This commit triggers the hooks that rebuild the blog. The main hurdle was authentication, since Github OAuth doesn't support any client-side flows (which is understandable since it's not a completed spec, to my knowledge). So I would have to pass my user/pass in everytime. But I got the API calls all working (after Github support helped me get CORS working), but I lost interest in the project and it's just sitting around collecting dust The code: https://github.com/swanson/lanyon/tree/gh-pages https://github.com/swanson/lanyon/tree/gh-pages Demo that doesn't quite work: http://swanson.github.com/lanyon/ http://swanson.github.com/lanyon/

grandalf 15y ago

In other news, google docs is one commit away from being the ultimate blog engine.

daniel_levine 15y ago

While GitHub is great I think it is more likely that DropBox becomes a dominant blog engine. Already there are things like TiddlyWiki and DropPages that do this and it's much more approachable for the average user. I also think as DropBox teams improves and iterates it will be interesting to see more people using Dropbox for basic version control, probably not a good idea but I think it'll happen.

mmahemoff 15y ago
Marco Ament (Instapaper) started working on a Dropbox blogging engine, where you can just maintain a drafts directory and copy it into a pending directory. It was discussed on his podcast (Build and Analyze), don't think he's published it though.
alexcabrera 15y ago
See my comment above. We've built and launched this at http://droptype.com http://droptype.com. Would love to hear your thoughts.
- chipsy 15y ago
  This sounds like something I want to use. Some impressions: The first thing I did was edit my profile, but I found that it doesn't give me enough feedback about errors. I tried changing everything all at once(of course) and then got greeted with the previous defaults. It took some trial and error to figure out that it wasn't accepting the RGBA PNG I had picked out for a profile picture. I'd also like a direct link to the markdown formatting docs, or even just a quick summary, on the profile editing screen. My profile finished, I proceeded to look in my Dropbox folder. The README is not formatted for Windows Notepad and appears as one long line of text. I switched to NP++ and continued to write a "hello.txt" containing a link and an image. It shows up, so I go back and edit the README, too. Everything is in order, but what is this "cloud+arrow" button? Inspecting it reveals it's publishing, but I don't feel confident about whether I've published hello.txt until I log out and check. I might continue using this. Some last thoughts: I will probably want options to organize posts. There isn't enough documentation to know if I already have them. I found myself wondering if there was a shortcut for marking up the image that would let me point to a folder inside Dropbox without tabbing out to find the public link. I may not want the displayed title of README to be README.

DanielRibeiro 15y ago

Github's founder Tom Preston Werner had a similar article]1]: Blogging Like a Hacker [1] http://tom.preston-werner.com/2008/11/17/blogging-like-a-hacker.html http://tom.preston-werner.com/2008/11/17/blogging-like-a-hac...

taylorbuley 15y ago

I'm a coder at a big media company. I would die to find a gaggle of people who want to work with me on a simple CMS on top of Git.

alexro 15y ago
Who you see as your primary audience for this type of thing? I just don't think developers do CMS a lot
- taylorbuley 15y ago
  It would definitely have to be designed for the kind of crowd that's never installed Jekyll. As paleolithic as it sounds, I think a CMS build on flat files would be a lot easier to manage than a CMS built on a relational data store. If you don't need accounts and personalization, or can just do that all client side, you could simply load balance across micro AWS instances pulling from the git repo and stick everything behind Cloudfront -- all for a few quarters an hour.
  - wyclif 15y ago
    The CMS on flat files thing has been done before, for example with a Perl script: http://www.blosxom.com/ http://www.blosxom.com/ Nevertheless I think the concept has potential if done right (and with Github or Dropbox).
endian 15y ago
I've been wanting to do this. I'm in NYC. I'll be less busy soon. This should be done.

metra 15y ago

A major feature that Jekyll is missing is commenting. Relying on Disqus, a closed source platform, is not ideal because it slows down page load times, does not contribute to SEO, and it does not let you host and search for comments in your git repo. Some people argue that adding a dynamic commenting system contradicts the static html goal of Jekyll. Going along those lines, critics say that a conversation is best carried out on 3rd party sites like HN. However, for technical blog posts specifically, a two-way conversation helps illuminate finer points in the original blog post. Googling around for 'jekyll comments' or 'disqus open source alternative' reveals many people who would use such an idea. However, aside from some quick-and-dirty projects, I see no compelling open source alternative to disqus that will include features such as OpenId, spam prevention, comment threads, etc. Does anyone know of such a project?

mechanical_fish 15y ago
Are you thinking of some kind of hybrid system, in which there's a Disqus-like web app to serve recent comments and enable the commenting infrastructure, but the comments eventually (on a timescale of hours) get rendered into static HTML in my git repository for long-term archiving, SEO, searchability, faster page loads, etc? That sounds interesting. My next question is: Does Disqus's API let me do this via... Disqus? Surfing through the API docs suggests that the answer may be "yes".
- thedz 15y ago
  Yup, the API lets you do that. You can pull our your comments and sync to a local datastore.
  - thetylerhayes 15y ago
    Guide: http://docs.disqus.com/help/58 http://docs.disqus.com/help/58 (though it's already automatic in our WordPress and MovableType plugins).
swanson 15y ago
What about a form that lets someone submit a comment and it appeared as a Pull Request in your repository? Once you merge in the change, Github will rebuild your blog and it will appear. That would be kind of cool. Or you could just have a comment link that uses the github website comments - if you are really interested in technical discussion it's probably fair to assume the poster has a github account

freshhawk 15y ago

That's an incredibly low bar to set for something to be "the ultimate". I can smell the fanboyism from here!

mmahemoff 15y ago

A problem with this approach though is you end up having to manage a directory full of files called MyAwesomeBlogPost.html etc. Or perhaps using a date or sequence based prefix to keep them in some order. A little tricky to manage once you have dozens of posts...so you'd want some front-end...but these days, it could be a TiddlyWiki or some other pure JavaScript app based on CORS (like swanson mentions in the present thread http://news.ycombinator.com/item?id=3235457 http://news.ycombinator.com/item?id=3235457)

mwsherman 15y ago

I think version control and content management are complimentary in some ways, but how is serving static files an “ultimate blog engine”? I feel like we’ve had that for a few years. What might actually happen is that Git or Dropbox become the interface through which we “put files on the web”. One’s blog is just a subset of files that one is maintaining anyway. That’s nice, and a consolidation of tools. But not, um, advanced.

btucker 15y ago
http://pages.github.com/#using_jekyll_for_complex_layouts http://pages.github.com/#using_jekyll_for_complex_layouts So while it is just serving static files, it's static files pre-processed by Jekyll.
bricestacey 15y ago
What might actually happen is that Git or Dropbox become the interface through which we “put files on the web”. There are some tools that exist already. Here is one that I recently discovered. http://www.kissr.co/ http://www.kissr.co/. There was another one also posted on HN recently, I forget its name.

alexcabrera 15y ago

We recently launched an app - http://droptype.com http://droptype.com - that tries to do static site generation using Markdown files over Dropbox. It's still very much a proof-of-concept and we're retooling to make it a bit more full-featured; but the eventual idea is to let you let you publish web content by just arranging files on any cloud storage platform. Again, it's still very early and this is more to prove that the idea is doable, but we'd love to hear any input. We're working on some commonly requested features like customized designs, cname redirection, rss feeds. The idea is to have a very hacker friendly publishing tool that doesn't require very much work to set up.