4 ms·
How is this different from Jekyl?
by johnnyo 10y ago
How is this different from Jekyl?
- christophersu 10y agoLooks like this doesn't generate a static site, but instead dynamically reads the content out of the blog "post" files and renders it on request.
- snehesht 10y agoI haven't used jekyll much but I would say this stores posts in separate git repo (github.com/snehesht/blogposts) and user doesn't need to update the server every time he publishes a new post. It uses github webhooks to alert server of any events related to the blogposts repo. The server verifies the events using HMAC authnication ( see github docs for more info) and then updates the local blogposts repo ( git pull)
- flohofwoe 10y agoWith github pages and Jekyll, updating the blog is also just a simple push of the Jekyll sources. The HTML page generation will than happen on github's side. Of course with this, you're locked down to 2 techs, github and Jekyll.
- icebraining 10y agoNot really locked in to Github, it's easy to replace it with any git server using a post-receive hook.
- danso 10y agoBeing locked into Jekyll is not such a huge deal, as the posts are all Markdown with some YAML frontmatter, and other systems use the same post conventions, such as Middleman. Github only provides the convenience of not having to install Jekyll on your own system in order to publish. If you want to throw it up to S3 or any other static file server, you just have to run `jekyll build` yourself.