Jekyll 4.0 Ideas

👋 Hello everyone! Summer is coming, and so is the implementation period for Jekyll 4.0. That's right, it's time to get some breaking changes in. To accommodate for this, we're opening this issue to collect interesting ideas that people would like to see implemented in 4.0. Keep in mind that even if an idea receives a lot of support, there's no guarantee that it'll get implemented — that depends on if someone is free to actually implement it. We're all volunteers here, keep that in mind.

Feel free to revive old feature requests, too, just not something that we've explicitly rejected.

For an organized view of how we're consolidating ideas and features, check out our Project board: https://github.com/jekyll/jekyll/projects/2

[laukstein]

I vote for #6293 Markdown links bidi support, in <>, []() by default.

[geraldb]

Adding fetch / get for datafiles to core (or as an "official" addon/plugin) would be great, see the unloved / public domain source @ https://github.com/18F/jekyll-get The code itself is about 40 lines, see https://github.com/18F/jekyll-get/blob/master/_plugins/jekyll_get.rb.

[geraldb]

Using the quik library for scaffolding. If you scaffold a new jekyll theme or plugin now all the code is "hard-coded" / "hard-wired". The scaffolding code itself is also "hard-wired" / "hard-coded", that is, not (re)usable for other projects. Using a (simple) "generic" scaffolding library such as quik you can turn any git(hub) repo (or directory/folder or zip archive) into a parametrized and scripted template scaffold. See the Jekyll Quick Starter Template / Scaffold - Build Your Own (Gem-Packaged) Theme as an example.

PS: Background / References - Talk Notes - Quik - The Missing Project Scaffolder (Library) for Ruby - Quick Start Your Ruby Gems, Jekyll Websites, Jekyll Themes 'n' More

[laukstein]

Custom HTTP headers compatibility for Github Pages (Webrick isn't planned to support github/pages-gem#415)

[pathawks]

@laukstein Let’s keep this restricted to Jekyll features. We don’t have any control over GitHub Pages.

[letrastudio]

I'd love to see automatic generation of tag and category archive pages in core (plugins like jekyll-archives do this, but none are whitelisted in GitHub Pages). I wrote up #6952 with my detailed rationale and a proposal of how it could work.

Here's the TL;DR:

Having vanilla Jekyll auto-generate archive pages for every tag and category is probably a good idea now, and I think I've come up with a good, clean way to do it while staying true to Jekyll's philosophy.

Code-wise, this snippet gets most of it across:

collections:
  tags:
    output: true
    permalink: /tags/:name/
  categories:
    output: true
    permalink: /categories/:name/

[mbrav]

I know that this is markdown and not necessarily jekyll related, but my life would have been a thousand times easier if jekyll supported inline footnotes like so [^Footnote, p. 123] as apposed to the more tedious:

This is first reference[^one], this is the second[^two]

[^one]: Footnote, p.1
[^two]: Footnote, p.2

[DirtyF]

@mbrav This depends on the Markdown engine. Please ask on Kramdown or CommonMark.

[asipple1]

First would like to say thank you to the Jekyll team for all the great work you all do. Jekyll is one my favorite frameworks to work with and I really do appreciate what you guys do!
Ok on to the request it would be great if there was a built-in way to paginate a list Jekyll collection items on a page. I know there is jekyll-paginate-v2 gem but it would be nice if there was a built in pagniation that worked for both post and collection items.

[nativerez]

Hello all, my first post so go easy. I want to just say that I love Jekyll, I'm now using it on a lot of my web builds. One thing that has bothered me though, is that I've not been able to take advantage of the latest Jekyll features because a lot of the 3rd party CMS solutions I rely on for my clients use (cloudcannon, siteleaf and forestry) simply don't run the latest versions of Jekyll themselves. This forces me to have my folder structures in a really messy state and not take advantage of the latest features when developing locally. So if anyone at Jekyll could bend a few arms to get them to update that would be fab.

[DirtyF]

@nativerez It alwyas take some time to update to the latest version for services like GitHub Pages, Forestry, CloudCannon or Siteleaf because they need to run tests and adapt their tools. There's nothing Jekyll's core team can do about it.

[rjachuthan]

I would like to see Nested Collections. I know there are alternatives to do this. But still if the Jekyll team can make it easier, that would be awesome.!