Jekyll vs Punch: What are the differences?
Developers describe Jekyll as "Blog-aware, static site generator in Ruby". Think of Jekyll as a file-based CMS, without all the complexity. Jekyll takes your content, renders Markdown and Liquid templates, and spits out a complete, static website ready to be served by Apache, Nginx or another web server. Jekyll is the engine behind GitHub Pages, which you can use to host sites right from your GitHub repositories. On the other hand, Punch is detailed as "A simple, intuitive web publishing framework that will delight both designers and developers". Punch allows you to use boilerplates to quickly setup a site, write minimal templates with Mustache, and create flexible site structures with inheritable layouts and partials.
Jekyll and Punch can be categorized as "Static Site Generators" tools.
Jekyll and Punch are both open source tools. It seems that Jekyll with 38.1K GitHub stars and 8.31K forks on GitHub has more adoption than Punch with 1.2K GitHub stars and 104 GitHub forks.
What is Jekyll?
What is Punch?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Punch?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Punch?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
With limited knowledge of CSS/HTML5, Jekyll makes it easy to create templates for static HTML5 sites. Unless I really need a database for something, this is the tool I prefer for standing up websites.
I settled on Jekyll to be the CMS for my research blog. Out of the box it works, and over time I added to it... why write a dissertation when you can instead hack templates to tweak things.
This static site generator is used with "contentful-import" ruby plugin, which allows to fetch data from Contentfull and generate new web-pages based on it. Easy and fun to use.
We wanted to pay the cost for website generation up front. Doing this allows us to put our website up in AWS S3 where it can be served reliably and for cheap.