Jekyll 3.0.x

[benbalter]

This is a progress tracking branch for getting things where the GitHub Pages Gem could be bumped to use Jekyll 3.0.x and related dependencies.

Initial todo to establish a baseline of what's changed:

• Get the Gemfile to bundle
• Confirm plugins work on 3.x
  • jemoji
  • jekyll-mentions
  • jekyll-redirect-from
  • jekyll-sitemap
  • jekyll-feed
• Enumerate breaking changes

Known breaking changes

• Dropped support for Ruby < 2.0
• Rouge is now the default highlighter
• Coffeescript and paginate must be explicitly included
• Dropped Maruku support

Please contribute only constructive comments below. If you would like to follow the effort's progress, you may click subscribe in the right-hand sidebar.

[parkr]

🙏

[parkr]

@benbalter jekyll-redirect-from has been updated: https://github.com/jekyll/jekyll-redirect-from/releases/tag/v0.9.0

[parkr]

@benbalter Also, see jekyll/jekyll#3945 for a list of gems that have been CI'd against Jekyll 3.

[benbalter]

Thanks @parkr looks like just mentions and jemoji then, which have fixes in the works.

[parkr]

@benbalter Did you add jekyll-paginate?

[benbalter]

Did you add jekyll-paginate?

Added.

[parkr]

Both jekyll-paginate and jekyll-coffeescript can be moved down to "Plugins" as they're no longer runtime dependencies of Jekyll. :)

[parkr]

Marvelous!

[alexconst]

Considering the work being done here, would it be worth submitting a fix to jekyll's issue with (the lack of) bold text on firefox?
(And there is also the issue with the header sizes, like h2 font being bigger than h1)
Which would eventually bump jekyll to 2.4.1 and would eventually be adopted by github.
I have no clue on the progress timeline for these things.

FWIW, test case for both bugs (visible in firefox):

---
layout: post
title:  "Test case"
date:   2016-01-10 21:44:44
categories: jekyll update
---

# header 1

test

## header 2

test

### header 3

testing **bold text here**

[j-mes]

@alexconst Wouldn't this be more of a CSS issue than Jekyll itself?

[alexconst]

@j-mes Well, it's the CSS produced by Jekyll using its site_template. But I get your point.
And since the solution is already documented I guess it's not really worthwhile.

[benbalter]

Just a quick update for those following along, this effort is still very much on track, and should be available at a GitHub Pages site near you in the coming month.

In the interim, if you'd like to test your site against the GitHub Pages Jekyll 3 stack, see @parkr's excellent post over in https://talk.jekyllrb.com/t/jekyll-3-x-with-github-pages/1832.

[larryfox]

@benbalter Is it safe to assume Github pages will be targeting 3.1.x now, since that's been released in the interim?

[parkr]

@larryfox: no, v3.0.1 is currently targeted. 3.1 will come later.

[benbalter]

Is it safe to assume Github pages will be targeting 3.1.x now, since that's been released in the interim?

There are a lot of moving parts in 3.1 (specifically drops), with few user-facing features other than performance. We're focusing on getting folks happy on 3.0.x, and then can come back and take a look at 3.x in another pass. This will also give 3.1 some time to bake in the wild.

[larryfox]

Understandable, thanks for the clarification!

[ghost]

I think there is a problem with Kramdown or Rouge:

Before:

source 'https://rubygems.org'
gem "github-pages"

---

After:

source 'https://rubygems.org'
gem "github-pages", github: "github/pages-gem", branch: "jekyll-3"

---

I use Prismjs for the highlighting, so it is based on classes of <pre>
The highlighting is now broken because the language is not being used in the class

I use

kramdown:
  input: GFM

[vdclouis]

w00p!

[pathawks]

🎉 👍