Is it possible to generate multiple pages with the same multiple data files?

[hoanguyenn2015]

Hello,

I have many data files (file1.yml, file2.yml, ...) that need to generate page1, page2, and so on.
I cannot find docs about this.

https://www.11ty.dev/docs/pages-from-data/ does mention about one data file to many pages, not my use case.

My YML files have a similar structure, but not all the same; some have 5 keys, some have 40, etc.

key1: data1
key2: data2
key3: data3
...
key900: data900

[dwkns]

I believe that Eleventy only supports .json and .js data files by default.

With that in mind, the way I would go about this would be to create a global data file, something likeyamlData.js.
In this I'd create an array, then I'd loop over all your yaml files, read them (using fs) and parse them to a JS object using js-yaml in a format something like like :

{ 
 name: <filenameWithoutExtension>
 data: <parsed YAML>
}

Then add each object to your array. If you export this array from yamlData.js it will be available to your templates as yamlData Then you just need a template something similar to :

---
pagination:
  data: yamlData
  size: 1
  alias: item
permalink: "{{ item.name }}.html"
---

{% for key , value in item.yamlData %}
  <li>{{ key }} - {{ value }}</li>
{% endfor %}

And it will create a page for each item in the array and you can use your YAML keys & values as required.

Does that make sense?

[hoanguyenn2015]

Thanks for your support. Does it mean I lose the caching mechanism if I use the helper file? Since it will process all files again for each build.

[dwkns]

I'm struggling to see a way to avoid building all the pages on each build as Eleventy doesn't know if/when the data in the YAML files changes.

If the data is not going to change (or it changes rarely), you could set up a 'one off' script that just builds those pages and coppies them into your project (seperate to the main build process). Then you could do an addPassThoughCopy of those files into your output folder. Unless you have a LOT of pages and the processing of your YAML is complex I suspect it wouldn't be worth it.