jekyll-paginate-v2 | Pagination Generator for Jekyll 3 (enhanced replacement for the old built-in jekyll-paginate gem) ⛺ | Plugin library

I have a variables.scss file that holds all of my sass variables in my root. I want to import it in my other scss files so that I can use these variables:

I have installed the jekyll-compose gem to streamline creating pages, posts etc. In the documentation. I have it working (i.e using the CLI commands I am able to generate, drafts, posts and pages).

However when I generate a post for example, I want it to have certain variables in the front matter. There is functionality mentioned in the ReadMe of Jekyll Compose that says you can set front matter defaults for posts and for drafts.

I have followed the instructions by adding the required lines in the config.yaml of my site, however posts and drafts that I generate using jekyll-compose do not generate with the variables I want.

Jekyll-compose states that if you want default front matter variables you need add something like this to your _config.yaml:

So i have this IPv6 thingy issue where i can't access rubygems and connection times out before it gets to use IPv4. One way or another i managed to install rubygems and when i type -v it all checks out. Now i need Jekyll and Jekyll-paginate-v2. I tried gem install jekyll and it didn't work for reasons stated above. Strangely enough i was able to install Jekyll via sudo apt install jekyll. Tried that with jekyll-paginate-v2 but there's no such option. So is there any way to install it without using gem command?

New to Jekyll converting a WordPress blog I'm trying to add pagination to my category layout. In _layouts directory I've created a file named category.html. I can successfully render a particular category with:

category.html:

We know Jekyll can use front matter variables like tags and categories and access them with site.tags and site.categories to iterate over them using liquid. Now my problem is that I can't do this with a custom front matter variable like author (as in site.authors) because Jekyll will not store it in a list format. This makes it very hard to paginate it.

Every solution I have looked at i.e.

• how to handle multiple authors in Jekyll

• adding authors to Jekyll

• jekyll-author

requires me to hardcode a list of authors to _config.yml or some other .yml (i.e. in _data/authors.yml). The problem here is that I don't use a fixed list of authors. The authors list needs to get updated when I throw in another post with a front-matter tag author: exampleAuthor or a list of authors (as in multiple authors per post, as currently only possible with categories and tags as well), while the server is running. It works with tags and categories splendidly, but not with custom tags like authors.

The easiest solution would be having a site.authors list to iterate over and just extending it with a ruby plugin.

I haven't found a plugin that provides me with a solution and thinking this was a common problem that I'm probably not the first to have.

I then looked at writing my own ruby plugin (Which is hard on it's own because of the lack of documentation. Maybe I'm to dumb to google, but the resources I found where very limited and hardly enough to guide you through the process) but there has to be a reason why this is so hard to do that makes all the existing solutions require hard coding the author list in a .yml (or .json, but most people go with .yml for some reason).

Doing this is out of the question for me, since I want to only throw in posts with author names in it later on and manipulating a .yml (I am under the impression that ymlfiles don't get compiled once the server is started, like _config.yml, correct me if I'm wrong) would be counterproductive because it requires you to restart the server to have them compiled.

Even very advanced plugins like jekyll-paginate-v2 (which I use successfully to paginate posts by tags and categories) don't have a solution to this as this issue portrays. He's getting recommended to abuse the category variable to paginate by author, which is kind of a desperate workaround.

I have found suggestions that it can be done with collections, however it does not seem feasible. Primarily due to the nature of their implementation: They require hard-coding the author list (again, I don't want that. I don't have a fixed list of authors. All of the author information has to come from the front-matter in the /_posts directory .md files) As of now I don't see how it can be done with collections. However I'm open to suggestions.

Edit: I found this dated issue on Jekylls github page which highlights that people are trying to do the same but to no avail. Has this become viable in the last 4 years?

I've run into an issue when using Jekyll (which uses the Liquid templating language), the plugin jekyll-paginate-v2 and offset.

The problem: I have a featured section on my blog that always shows the most recent post. The other posts appear below, 10 per page using paginate.

I tried to simply show them using {% for post in paginator.posts offset:1 %}, but this is flawed in two ways:

• it only shows 9 posts per page instead of 10
• it offsets the first post on each page, so that the 1st, 10th, 20th, etc. posts are hidden, which is not what I want

What I'm trying to achieve: a loop that always ignores the post at index 0 and shows everything else as it normally would.

Am I just using offset wrong, or is this a bug in jekyll-paginate-v2?

Right now I've "fixed" it by doing the following, but it's not ideal as the first page only shows 9 posts:

I'm struggling to overcome a strange behavior with Jekyll-Assets when exporting all assets correctly on build command. The configuration is set to use cachebusting with "file system" cache type. When building we get all images and fonts correctly. But on one of the scss files it seems that fonts and images are exported randomly (sometimes yes, other times no). When files are not exported the path written in css is correct, containing the hash for the cachebust. While trying to debug with deleting .assets-cache and _site/ folder I've notice the random gets even much more frequent.

This is the configuration

Dev environment(Docker Container):

I've set up my site to build with Travis CI, and added a few plugins.

This is my Gemfile: