Jekyll • 简单静态博客网站生成器

Jekyll 3.2.1 Released with Fix for Windows

2016-08-02T13:20:11-07:00

Well, 3.2.0 has been a success, but with one fatal flaw: it doesn’t work on Windows! Sorry, Windows users. Hot on the trail of 3.2.0, this release should squash that . Sorry about that!

This release also fixes an issue when using gem-based themes where the theme was rejected if it existed behind a symlink. This is a common setup for the various ruby version managers, and for Ruby installed via Homebrew. Props to @benbalter for fixing that up.

Thanks to the contributors for this release: Adam Petrie, Ben Balter, Daniel Chapman, DirtyF, Gary Ewan Park, Jordon Bedwell, and Parker Moore.

As always, you can see our full changelog on the History page.

Happy Jekylling!

Jekyll turns 3.2

2016-07-26T15:06:49-07:00

Happy Day! Jekyll v3.2.0 is out, and packed full of goodies.

Our flagship feature for this release has been themes. Themes?!, you say? Yes, proper, versionable, releasable, first-class themes. We’re pretty stoked about it and we hope you like building and using them. For now, it only supports layouts, includes, and sass, but we have plans to include static assets like images and CSS/JS in a future release. Read more about it in the docs. Our site template generated by jekyll new now dogfoods this feature, using the minima theme.

Some other notable changes:

Symlinks are allowed as long as they target a file in the site source
Explicit support for Ruby 2.0.x was dropped
Added an :after_init Hook
Added a where_exp filter to provide more powerful filtering
Added a link liquid tag which can be used to generate URL’s for any post or document based on its path relative to the site source
… and lots more!

As always, there is a full list of changes for your perusal.

Every release is made possible by the countless hours of hard work that our fellow community members put into sending patches, filing thoughtful patches, and so on. These release took the work of over 80 people:

Aaron Sky
Adam Hollett
ajhit406
Aki
Alex Hanselka
Alex Hoyau
Alex Ivkin
Alex Kitchens
Alex Plescan
Alex Wood
Anatoliy Yastreb
Andrew Artajos
Andrew Munsell
AndrewCz
Ankush Menat
Anthony Smith
Ben Balter
Brian Jones
Brint O’Hearn
Chayoung You
Chris Wells
chrisfinazzo
Clark Winkelmann
Dan Allen
David Von Lehman
David Zhang
Derek Gottlieb
Enes Gönültaş
EricH
Erick Sasse
Eugênio Cabral
Florian Thomas
Frank Taillandier
Henry Goodman
Henry Wright
Hugo Duksis
Hugo Giraudel
Jack Reed
Jamie Bilinski
Jeff Kolesky
Jens Willmer
Jordon Bedwell
Josh Waller
Joshua Barnett
Keegan Mullaney
Kevin Miller
Krzysztof Jurewicz
Loren Rogers
Marcos Brito
Marcus Stollsteimer
Matt Rogers
Michaël Guitton
Mike Linksvayer
Mike Neumegen
Nathan Hazout
Nick
No
nscyclone
Parker Moore
Pat Hawks
Pierre Fenoll
Praveen Kumar
Rares Vernica
Saleem Rashid
Sam Dutton
Shengbin Meng
Shinn Kondo
Shinnosuke Kondo
skim
Sondre Nilsen
Spencer A. Bywater
Stephen Checkoway
Suriyaa Kudo
surrim
TheLucasMoore
Thomas Wood
Tim Wisniewski
Tom Fejfar
Tony Garnock-Jones
Vincent Wochnik
XhmikosR
Yanis Vieilly
Yordis Prieto
Zack Spencer

We are so grateful to all of you for helping to put together a terrific release. Thank you!

Happy Jekylling!

Jekyll’s Google Summer of Code Project: The CMS You Always Wanted

2016-06-03T13:21:02-07:00

This year, Jekyll applied to be a part of Google Summer of Code. Students were able to propose any project related to Jekyll. With a gracious sponsorship from GitHub and the participation of myself, @benbalter and @jldec, Jekyll was able to accept two students for the 2016 season, @mertkahyaoglu and @rush-skills.

These students are working on a project that fills a huge need for the community: a graphical solution for managing your site’s content. Current plans include a fully-integrated admin which spins up when you run jekyll serve and provides a friendly web interface for creating and editing your content. The server and web interface will speak a common HTTP interface so either piece could be switched out for, e.g. a server which writes directly to a repository on GitHub.

The strength of text files as the storage medium for content has been part of Jekyll’s success. Our homepage lauds the absence of a traditional SQL database when using Jekyll – your content should be what demands your time, not pesky database downtime. Unfortunately, understanding of the structure of a Jekyll site takes some work, enough that for some users, it’s prohibitive to using Jekyll to accomplish their publishing goals.

Mert and Ankur both applied to take on this challenge and agreed to split the project, one taking on the web interface and the other taking on the backend. We’re very excited to see a fully-functional CMS for Jekyll at the end of the summer produced by these excellent community members, and we hope you’ll join us in cheering them on and sharing our gratitude for all their hard work.

Thanks, as always, for being part of such a wonderful community that made this all possible. I’m honored to work with each of you to create something folks all around the globe find a joy to use. I look forward to our continued work to move Jekyll forward.

As always, Happy Jekylling!

Jekyll 3.1.6 Released

2016-05-19T12:48:14-07:00

Upon releasing 3.1.5 and kicking the tires, we noticed a glaring bug: our beloved jsonify filter doesn’t work! With that, our work was cut out for us and we decided a 3.1.6 was necessary. This release restores sanity to our object-to-JSON generation in Liquid and we hope you enjoy.

For the gory details, see the pull request or the changelog.

Happy Jekylling!

Jekyll 3.1.5 Released

2016-05-18T21:35:27-07:00

There’s always at least one bug, right? :)

Hot on the trails of v3.1.4, we bring you v3.1.5! It fixes one bug around requiring the ExcerptDrop, which only affects Linux. For the gory details, see the pull request for the fix.

Happy Jekylling!

Jekyll 3.1.4 “Stability Sam” Released

2016-05-18T16:50:37-07:00

Hey Jekyllites!

Today, we released v3.1.4 in an effort to bring more stability to the v3.1.x series. This bugfix release consists of:

A fix for layout in Liquid where values would carry over from one document to the next
A fix for layout in Liquid where a parent layout (e.g. default or base) would overwrite the metadata of the child layout (e.g. post or special).
A fix where page.excerpt referencing its excerpt would cause an infinite loop of recursive horror.
We added Configuration.from and the great permalink fix from v3.0.4 to the v3.1.x series
site.collections in Liquid is now sorted alphabetically by label, so docs shows up before posts reliably.

The fixes for layout may not be seamless for everyone, but we believe they will be the “right thing to do” going forward.

We are alwawys striving to make Jekyll more straight-forward to use. Please do open an issue if you believe an aspect of Jekyll’s user experience isn’t up to par.

For a full history of our changes, see the changelog.

As always, Happy Jekylling!

Jekyll 3.0.5 Released

2016-04-26T17:40:44-07:00

This version fixes a bug affecting only v3.0.4 where autoregeneration was always disabled when running Jekyll locally. This feature is a huge reason why Jekyll (or any static site generator, for that matter) is a joy to use. Sorry for the regression!

If you’re using GitHub Pages, you can follow the progress of the upgrade on the github/pages-gem repo.

As always, our history doc has links to the pull requests and issues associated with the release for your perusal.

We’re looking forward to the upcoming release of v3.2 which has some excellent goodies we think you’ll love.

Happy Jekylling!

Jekyll 3.1.3 Released

2016-04-19T10:26:16-07:00

v3.1.3 is a patch release which fixes the follow two issues:

Front matter defaults may not have worked for collection documents and posts due to a problem where they were looked up by their URL rather than their path relative to the site source
Running jekyll serve with SSL enabled was broken due to a bad configuration.

Both of these issues have been resolved. For more information, check out the full history.

Happy Jekylling!

Jekyll 3.0.4 Released

2016-04-19T10:26:12-07:00

v3.0.4 is a patch release which fixes the follow two issues:

Front matter defaults may not have worked for collection documents and posts due to a problem where they were looked up by their URL rather than their path relative to the site source
Configuration for the posts permalink might be borked when a user specified a value for collections.posts.permalink directly. This forced the use of permalink at the top level, which also affected pages. To configure a permalink just for posts, you can do so with:

collections:
  posts:
    output: true
    permalink: /blog/:year/:title/

Both of these issues have been resolved. For more information, check out the full history.

Happy Jekylling!

Making it easier to contribute to Jekyll

2016-03-10T00:00:00-08:00

Jekyll is an open source project, built one contribution at a time by community members just like you. These community contributions can come in many forms beyond just writing code, from reporting an issue or suggesting a new feature to improving documentation or providing feedback on proposed changes.

If you’ve been looking to get involved with the Jekyll community, but didn’t know, we’ve recently made it easier to contribute to Jekyll in two ways:

First, we’ve completely rewritten the project’s contributing guidelines, outlining the various ways you can contribute, and including better instructions for submitting proposed changes via GitHub.com or for submitting your first code improvement. And if you have any feedback, we’d love to hear it! Simply click the “improve this page” button in the top right corner of the contributing documentation.

Second, this week, we created six community interest groups, we’re calling Jekyll affinity teams. If you’re interested in a particular aspect of the project (or just want to learn more), you can join any one of these teams (or two, or three), to participate in discussions about potential bugs and proposed improvements. And the best part is there’s no commitment. If you just want to listen, or if at any point you want to leave (or switch teams), that’s totally fine. We won’t say a thing. To learn more about the various affinity teams, or to join one (please do!), just head on over to teams.jekyllrb.com.

We hope these changes will make it easier for you to make your first (or second, or third) contribution to Jekyll today. Thanks for helping to make Jekyll awesome!