by bradgessler on 5/7/2014, 2:38:13 AM
by PStamatiou on 5/7/2014, 3:58:28 AM
This is amazing news. I currently have to run 2 Jekyll installs to do what I want with custom post types (before this I had a fork to add a different type and that was getting hard to keep updated): I have one main Jekyll install for my blog, and inside of that inside /photos I have another Jekyll for my photo blog so I can do things like this:
http://paulstamatiou.com/photos/japan/two-weeks-in-japan/
<3 open source! All hosted on S3/CF with https://github.com/laurilehmijoki/s3_website
by danso on 5/7/2014, 2:20:27 AM
Congrats! Native support of Sass and CoffeeScript seem trivial, because of the various hacks and plugins out there...but damn it was hard, even knowing the hacks, to get a Jekyll project up and running if I hadn't been recently re-acquainted to its quirks. It'll also be nice to have Github Pages (I'm assuming) support the baking out of sass files...it feels so wrong to go back to plain CSS.
The #1 feature, collections, is also huge...Lately I've been using Middleman, because there are a lot of small data-apps that don't require Sinatra/Rails but that Jekyll, being blog focused, is not well-equipped to handle...Middleman fits that niche perfectly...almost too well, as I often get to the point where I think, "Why didn't I just make this a Sinatra app?" But I'm glad to see some more flexibility with Jekyll...even in the previous version, you could get pretty far with the hardcoded blogging conventions.
Mainly, I'm excited to Github Pages become even more easy-to-deploy and configure, particularly for documentation. Congrats and thanks again!
by samstokes on 5/7/2014, 2:09:03 AM
Looks awesome. I wonder if Octopress is planning to support this new version? Some of the new features (e.g. support for sass) seem to overlap with Octopress.
by fdsary on 5/7/2014, 2:49:03 AM
So I'm trying to check this out, but my ruby gems mirror seems to not want to. I get this error:
`ERROR: Could not find a valid gem 'jekyll' (>= 0), here is why: Unable to download data from https://rubygems.org/ - bad response Gateway Time-out 504 (https://tokyo-m.rubygems.org/quick/Marshal.4.8/jekyll-2.0.1....
Is there any way to specify other mirrors, and is there other mirrors than the Tokyo one that would work better?
by Kronopath on 5/7/2014, 3:51:31 AM
Good to see them supporting Kramdown as the default Markdown converter. When building up my personal website using Jekyll, I very quickly switched to Kramdown from the default Redcarpet—it had a lot better handling of typographic characters like smart quotes and dashes, and played much nicer with Mathjax.
Collections also look like they will really help with creating websites that deviate from the exact "blog" format that Jekyll is optimized for.
Good work from the team.
by tdicola on 5/7/2014, 1:59:07 AM
Nice! Anyone know if github pages support Jekyll 2.0 yet?
by taigeair on 5/7/2014, 3:40:56 PM
I use Jekyll and am having an issue with it when I use feedburner. It recommends using {{site.url}} in the markdown and templates.
http://jekyllrb.com/docs/posts/
So, for example, I have {{ site.url}}/radio-surfing
On my site it shows http://www.taigeair.com/radio-surfing/ but on feedburner it becomes http://feeds.feedburner.com/radio-surfing/ in the feed.
Example http://feeds.feedburner.com/taigeair
Does anyone else have this issue? Any suggestions?
by canadev on 5/7/2014, 10:12:12 AM
Is there any sort of interactive static site generator, for people who are not very computer literate to use?
(I write code, so it's not for me, but I am wondering if I could say, setup a template for a friend, and have them fill in the content of the pages.)
by mrmondo on 5/7/2014, 3:50:33 AM
Shout out to parkr, albertogg & troyswanson for the fastest public bug-fix turn around:
by tragic on 5/7/2014, 8:54:56 AM
Looking at the changes, it's like every small niggly pain-point I've had with my particular Jekyll use cases (faffing around to get sass watch going in a separate shell, using 'posts' for things that are not in any sense posts) have been addressed. A version bump just for me!
I am a happy bunny.
Congratulations and thanks to the Jekyll folks.
by liquidvisual on 5/7/2014, 3:04:31 PM
I'm using the starter template ($ jekyll new project) and pretty URLs are enabled by default. The "about" page works but the "welcome to Jekyll" link goes to a .html appended url.
Anyone else finding this?
by ericHosick on 5/7/2014, 3:21:44 AM
I really like Jekyll and use it for both my website and blog. It really is a great product that is easy to use. Thanks!
by 100k on 5/7/2014, 2:18:52 AM
This looks like a solid release. Collections will make Jekyll a much better choice for a wide range of sites.
by benatkin on 5/7/2014, 3:39:04 AM
It's great to see open source projects that are used by many people evolve.
by gpxl on 5/7/2014, 2:37:35 AM
Very cool! Thanks to the whole team for their hard work.
by drchiu on 5/7/2014, 5:51:41 AM
This is fantastic. Thank you Jekyll team!
by nilved on 5/7/2014, 3:00:46 AM
Quite disappointed the developers have decided to stick with Liquid templates. With such a handicapped and useless template language, jekyll is a non-starter for any website more complex than something you could trivially write yourself.
Congrats on the 2.0 release!
I highly recommend taking a look at http://middlemanapp.com if you're considering Jekyll. I gave a talk at RailsConf (http://bradgessler.com/talks/middleman-frontend/) about static website generators and found that Middleman handles everything Jekyll does in a much more modular, more "railsy" way by using tilt, sprockets, and all that good stuff.