Support global templateEngine settings with images in content folders

[Brixy]

I am just porting another site to Lume from Eleventy. And it works just great!

The old sites uses Eleventy’s Nunjucks shortcodes within markdown files. Lume supports this with templateEngine: njk,md in front matter.

Yet, I noticed an issue: Apparently you cannot use this setting globally for all blog posts in combination with images in folders, probably because images are pages in Lume:

# posts/_data.js
export const templateEngine = 'njk,md';

posts/
└── 2022-05-28_a-post/
    ├── index.md
    ├── file.pdf
    └── image.jpg

As soon as you remove the image file from the folder everything works as expected.

(Honestly speaking I have not tried Lume’s modules plugin with this combination.)

Thank you.

[oscarotero]

Mmm, I understand.

In Lume all files are "pages" but there are two types of pages: regular pages and assets pages (it's explained here). Assets pages don't apply the layout variable (to avoid an image/css/js be wrapped in a layout), but it do apply the render. Maybe assets pages shouldn't be rendered, and only apply (pre)processors.

As a workaround, you can use a preprocessor to apply the templateEngine variable only to md files:

site.preprocess([".md"], (page) => page.data.templateEngine = "njk,md");

[Brixy]

This works perfectly! Thank you.

A global setting of templateEngine does not seem to have any disadvantages.