A new collection with a different archive, not tags, year, status, or categories

[saguileran]

I want to create a new collection and group it by a new feature. For example, I am creating a new collection named animes and I want to have the different formats on each review (anime, film, ova, web-comic, etc). I extended the current implementation of the other collection's group and updated three files: _config.yml, anime-review.liquid, and archives.liquid. The codes are the following:

# My new collection named anime-review.liquid
{% assign formats = page.formats | join: '' %}
....
      {% if formats != '' %}
          ·  
        {% for format in page.formats %}
          <a href="{{ format | slugify | prepend: '/animes/type/' | relative_url }}"> <i class="fa-solid fa-clapperboard fa-sm"></i> {{ format }}</a>
          {% unless forloop.last %}
            &nbsp;
          {% endunless %}
        {% endfor %}
      {% endif %}

The corresponding config is

# _config.yml
jekyll-archives:
  ....
  animes:
    enabled: [year, tags, categories, status, formats]

Although everything is almost the same, except by the names, it is like the for cycle does not work correctly and does not split the string I am giving to each review, for example: formats: manga anime film video-game. It is taken as a single element, a single format, which is not what I want. The result is the following, last part:

It is so weird because I am following the template, and the current code is creating the following index, for the format grouping:

Any idea how I can fix it? Is it related to the gems or the configuration?

[george-gca]

This took me a while to figure out, but here is the thing: Jekyll has special built-in handling for certain fields like categories and tags. It automatically converts them to arrays when parsing the YAML frontmatter, and apparently this is not exclusive to posts, but applies to any collection. However, custom fields like the one you are trying to use don't get this special treatment and remain as strings.

How did I find out? I wrote some outputs to the book-review.liquid layout to inspect the values and types of these fields. Here are the relevant outputs I got (I named my custom field tablets):

{% assign categories = page.categories | join: '' %}
{% assign tablets = page.tablets | join: '' %}

Categories str: {{ page.categories | jsonify }}

Categories: {{ categories | jsonify }}

Tablets str: {{ page.tablets | jsonify }}

Tablets: {{ tablets | jsonify }}

And here is the code that is created:

Categories str: ["classics","crime","historical-fiction","mystery","novels","thriller"]

Categories: "classicscrimehistorical-fictionmysterynovelsthriller"

Tablets str: "manga anime video-game live-action film"

Tablets: "manga anime video-game live-action film"

As you can see, page.categories is an array (as expected), while page.tablets is just a string. Therefore, when you try to loop over page.tablets, it treats the entire string as a single item, which is not what you want.

The solution: convert page.tablets to an array. So, the for loop will look like this:

{% assign page_tablets = page.tablets | split: ' ' %}
{% for tablet in page_tablets %}

I added this information to CUSTOMIZE.md.

[saguileran]

Great! Thanks for the fast response.

Now the elements are being displayed correctly, but not the indexation. It is still not working as expected.

I changed both the liquid file and the _config, as suggested in the CUSTOMIZE.md file. However, the links are not working properly.

[george-gca]

It seems to be a bug in the jekyll-archives-v2. I will try to update and issue a new version.

[george-gca]

I just submitted a new version of jekyll-archives-v2, but I will only update the version on the template tomorrow.