I can't help but think at some point GitHub will not be so friendly to free blog hosting through their system. They are a version control SAAS. If you generate to much traffic, what will happen? The market might be ripe for a git based cms/blog why not build that company and service?
Really interesting point. I'm not exactly sure what I think would happen, but my intuition is that GitHub wouldn't turn off access to GitHub pages just for users on our platform - even if traffic was excessive. I think this generates a lot of interest in GitHub in general which is beneficial for them.
But you are right, I believe a git based cms/blog that runs in some standalone fashion could be a v2 or v3 of this product. Or perhaps a one-off paid option if you don't want to use GitHub, you can pay to use our private git repo or even a git repo you host on your own.
Solution: Host the blog on your own domain name. That's literally all you need to ensure that down the line you can move the content to your own jekyll infrastructure (or somebody else's).
It's true. At some point github will turn all this blog traffic into profit. But just like they did with gist.github.com they can make a ghpages.github.com or something and create plans. At this point I think is just another feature that keep them a big step ahead of bitbucket, gitlab, and others.
The market might be ripe for a git based cms/blog why not build that company and service?
But what's a `git based cms/blog' ? A static website generator that commit on heroku ? Or a cli/gui post manager that uses git command-line argument as an API ?
I agree completely. I'm working on a static website CMS that I hope to release soon. I think there's a lot of room for the static website market to grow, particularly alongside proper management and deployment tools.
Comments
I can't help but think at some point GitHub will not be so friendly to free blog hosting through their system. They are a version control SAAS. If you generate to much traffic, what will happen? The market might be ripe for a git based cms/blog why not build that company and service?
Really interesting point. I'm not exactly sure what I think would happen, but my intuition is that GitHub wouldn't turn off access to GitHub pages just for users on our platform - even if traffic was excessive. I think this generates a lot of interest in GitHub in general which is beneficial for them.
But you are right, I believe a git based cms/blog that runs in some standalone fashion could be a v2 or v3 of this product. Or perhaps a one-off paid option if you don't want to use GitHub, you can pay to use our private git repo or even a git repo you host on your own.
Solution: Host the blog on your own domain name. That's literally all you need to ensure that down the line you can move the content to your own jekyll infrastructure (or somebody else's).
I doubt Github would frown upon this. Github Pages has already been handling a quarter million req/sec. [0]
[0]: https://github.com/blog/1992-eight-lessons-learned-hacking-o...
It's true. At some point github will turn all this blog traffic into profit. But just like they did with gist.github.com they can make a ghpages.github.com or something and create plans. At this point I think is just another feature that keep them a big step ahead of bitbucket, gitlab, and others.
But what's a `git based cms/blog' ? A static website generator that commit on heroku ? Or a cli/gui post manager that uses git command-line argument as an API ?
I agree completely. I'm working on a static website CMS that I hope to release soon. I think there's a lot of room for the static website market to grow, particularly alongside proper management and deployment tools.