Jekyll Lambda – Minimal Theme for Jekyll

Also in the same vein --

http://purecss.io/

Main difference I find is a little more styling/ramp up and quotient-based gridding (you can attach semantically named classes for 1/3rd of the space or 2/5ths)

I've used skeleton A LOT for a quick and dirty responsive css framework. But unfortunately, the latest version doesn't support nested columns. A big disadvantage, IMO.

I think they are great, but because statically generated sites can limit growth, just because if you want to add backend features (forms, commenting, etc.), you may have to switch platforms or use third party services.

I host my own blog on Jekyll and that works awesomely well and I have no plans for needing a backend server. If I was a startup and wanted to add small marketing features (email collection, surveys, etc.) then I would consider moving off of it.

Middleman is amazing, I build all of my sites with it...it's a nice mix of Jekyll's ease with the flexibility of being able to write as much templating/backend logic as you need (basically, the ability to use Erb). For any site in which you don't need a database, in which your content can be serialized as several hundred JSON/yaml objects, I think Middleman is fantastic.

Hakyll is fantastic -- works great as a blog, but is also very extensible. I used Nanoc before that and it was also excellent.

I don't think you want Pelican or Jekyll in this case. Their emphasis is definitely on blogging and you'll have to fight them some if you move away from that niche.

What exactly opinions do you want? I tried all of that stuff except of Middleman and ended up writing my own. Jekyll is way too opinionated, no way to make the website exactly what you want it to be. Hakyll is very configurable, but the very fact that it's written in Haskell and needs to be recompiled after every structural change turned out to be way more annoying than I thought. Pelican would be nice, but the last I checked it was quite unstable and buggy, unlike Jekyll and Hakyll. In the end I thought that writing 200 lines of Python code to do exactly what I want is easier, than to explore what's out there and how to make it to do what I want.

I personally like Harp for it's simplicity (which mostly comes from NPM and node magic):

http://harpjs.com/

http://harpjs.com/docs/quick-start

make and bash go a long way!

For Go fans, I had a lot of fun playing with Hugo: https://github.com/spf13/hugo

I tried Pelican just to see how they work and what's so special about static site generators. The downside for me was having to go through the process of re-generating the site and committing just so you can fix something as simple as a grammar error or a comma. It gets old fast IMO. The other annoyance was with images included in the post. You have to copy then write the image path because you don't have something like a pop-up box which just selects the image.

So I switched to ghost and I'm fairly happy for now. The downside of this is that I have to pay ~$4 a month for a shared hosting, which is fine by me.

I'm using Jekyll for my portfolio, and it is working out quite well. Unfortunately, I can't get paging to work on multiple collections at once. So it would be great for a site that's ONLY a blog or ONLY a portfolio, but I recently added a blog and it seems to be holding me back.

Portfolio: http://www.thejeremywhite.com/

Source: https://github.com/iheart2code/iheart2code.github.io

I use jekyll but since I've been learning Go I have wanted to use Hugo which seems to have a lot of nice features. Middleman seems to have the most features though.

Still, it's nice that jekyll doesn't require much work to deploy to github.

I've used Jekyll (quite a bit), Metalsmith, and Hugo and tested some others. They all fit a particular use-case, like Hugo is incredibly fast, Metalsmith is incredibly flexible (it's something like a Gulp for static sites), and Jekyll is well-rounded, has a large community, and has the most progress with content editors for non-technical users.

I run a site with resources for static site generators, The New Dynamic, and you can find a lot of articles on those and others there: http://www.thenewdynamic.org/

Jekyll has a huge community, is actively maintained (it being the backbone of GitHub’s blog system) with plenty of plugins, and has pretty decent documentation (that can always be expanded with a pull request).

I find those factors tend to trump smaller shortcomings. There’s always going to be some stuff, but being able to ask a question and get an answer is very important. Take that from someone who did his first static blog in Blogofile …

Windows support has been non-existent, which is obviously huge to some, but Jekyll 3 aims to remedy that. I haven’t played around with Jekyll 3 on Windows, though, so you only have their word for it. Ruby on Windows is already … interesting.

I love the minimalism. Jekyll?

My Jekyll install (https://collantes.us/) is also minimal. I truly love Jekyll, and the flexibility that presents: add post (.md file), commit, done.

It's not too hard, and is documented here: http://jekyllrb.com/docs/pagination/.

Disadvantages of using Disqus as your commenting system:

1. Your comments are in disqus, and not local to your server 2. Users with JS disabled are not going to see the comments 3. Friends and other would-be commenters may be banned by Disqus without having been banned by you.

As to point 1, I believe there's an API that you can retrieve your messages from if you ever want to migrate away from Disqus, but the other two (I think) hold true no matter what.