Github recently upgraded Jekyll version to 3.0, but along with that, many features were removed. Github is now fighting with users to adhere to their new standards, even at the cost of breaking existing websites.
Ask HN: Why GitHub is downgrading its GitHub Pages?
1–4 of 4 posts
Re: Ask HN: Why GitHub is downgrading its GitHub Pages?
#2Er, can you give examples of broken functionality?
Re: Ask HN: Why GitHub is downgrading its GitHub Pages?
#3Er, can you give examples of broken functionality?
https://www.rohit.io/
The CSS of the complete website is broken with hardly any change.
Re: Ask HN: Why GitHub is downgrading its GitHub Pages?
#4You need to change your markdown to "kramdown" instead: https://github.com/rohit01/rohit01.github.io/blob/master/_co...
Did you update to the Jekyll 3 gem? I do not see a Gemfile.lock to verify. But you should move to the v3 of the gem to make sure. "bundle update jekyll"