Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Already on GitHub? Sign in to your account
Upgrade to Jekyll 3.x #1193
Conversation
harding
self-assigned this
Jan 7, 2016
|
ACK |
harding
referenced this pull request
Jan 13, 2016
Closed
Create template for developer weekly IRC meetings #1147
|
Note to owners/other maintainers: I'm beginning the upgrade now; please don't make any other merges until I post here that I'm done. If you need me, I'll be checking IRC periodically. |
harding
merged commit 7d98f79
into
bitcoin-dot-org:master
Jan 16, 2016
1 check passed
harding
added a commit
that referenced
this pull request
Jan 16, 2016
|
Upgrade complete. I watched the build and didn't see any problems in the logs, and I've spot checked a few dozen pages in several different languages without seeing any problems. If you do spot a problem, please post here or open a new issue. Thanks. |
harding commentedJan 7, 2016
Update to Jekyll 3.x
This commit updates the site from Jekyll 1.3.0 to 3.0.1 (anagram unintended). This catches us up on a couple years of technical debt from not upgrading and makes it easier to fulfill feature requests like #1147.
A diff of the HTML compared to the current site is provided below. I'm sorry it's so large: as part of the upgrade, the syntax highlighter was changed from Pygments to Rouge and so every code span and block on the site was changed. (And, gosh, we had a lot of 'em.)
There should be no changes to any javascript, CSS, or links. I think there's only one user-visible change to the site: the Bitcoin Core releases are now shown in date order rather than version order (but the highest version number is still the version offered for download on the Download page).
Explanations of all the changes in the commit are available in the commit message. Sorry it's one giant commit---everything seemed to be interdependent. Site developers should be able update to the latest Ruby gems after checking out this branch by running,
bundle installI'm aiming to merge this early morning on Saturday the 16th. (I want to merge on a Saturday so I'm available to fix any upgrade issues.)