3.0 RELEASE GAMEPLAN

[parkr]

I have written about what I'd like to see for Jekyll 3.0. That post is now a month and a half old. I'd like to get Jekyll 3.0 out the door in Q1 2015 to bring all the amazingness we have been cooking out to you excellent Jekyll users and developers. Check lists usually help me more than anything else, so here's what I'd like to accomplish:

• Incremental regeneration ( Incremental regeneration #3116 )
• Integrate basic hooks (potentially via @imathis's Octopress::Hooks work) ( Add Hooks, based on the Octopress::Hooks project #3392, prototype of jekyll hooks, encapsulated #3553. )
• Switch over to Rouge as default syntax highlighter, dropping hard dependency on Python ( Remove most runtime deps & move to Rouge as default highlighter #3323 )
• Drop hard dependency on ExecJS runtime (e.g. Node) ( Remove most runtime deps & move to Rouge as default highlighter #3323 )
• Make most dependencies optional and handle their absence gracefully ( Remove most runtime deps & move to Rouge as default highlighter #3323 )
• Upgrading to Liquid 3 & adding optional liquid-c support ( Upgrade to Liquid 3.0.0 #3002 )
• Make _posts a default collection (& therefore simplify the internals) ( Make pages and posts instances of Jekyll::Document. #3169, initial implementation of posts as a collection #3690 )
• Remove Convertible.
• Automated Windows tests? ( Add Appveyor testing #3115 )

Anything else you'd like to see?

[imathis]

Everything here looks so great. I'll be especially excited to hooks come to Jekyll. Anything to get rid of all the monkey-patching we do for plugins!

[paulrobertlloyd]

This looks great. In terms of supporting plug-ins, it would be nice-to-have a more fully featured jekyll-paginate be released around the same time (i.e. having the ability to paginate practically any group of posts). Pagination I think is the only area from a templating perspective where Jekyll still suffers slightly.

[pepelsbey]

+1 for pagination issues.

[parkr]

Pagination chat should be had over at: https://github.com/jekyll/jekyll-paginate But thanks for the input.

[IainIsCreative]

Rouge seems like a nice idea, but frankly, I'd like to see if my code blocks can be written out as lists and not using table. Does Rouge support that or are there other methods it provides?

[alfredxing]

👍

We should probably get working on Make _posts a default collection (& therefore simplify the internals) & remove Convertible. Related issue is #3169.

[parkr]

@iainspad If you open an issue on jneen/rouge, I'm sure they can get you sorted. :)

[parkr]

We should probably get working on Make _posts a default collection (& therefore simplify the internals) & remove Convertible. Related issue is #3169.

@alfredxing I was going to wait until @envygeeks landed #3305 his rebase nightmares aren't epic.

[alfredxing]

#3224 (using Liquid::Drop) would also be great if it can be done.

[erlend-sh]

I'm probably just confused by semantics here.

Make _posts a default collection

Does that include Pages as well then?

[parkr]

Does that include Pages as well then?

This is a tougher sell for me – each page is meant to be a separate entity. It therefore doesn't really make sense to join them together into a collection. That being said, we provide site.pages in Liquid, which is a simple array of Page objects. So as it happens we already give the user access to a "list" of pages. Now, whether we want to go one step further and allow all the various add-on features of a collection is not necessarily the case. I'll definitely revisit this once we have a _posts collection to see if we can swing it. :)