Closed
Description
When using liquid I had a news.11tydata.json
containing:
{
"layout": "layouts/post",
"tags": ["news"],
"permalink": "{{ page.date | date: '%Y/%m' }}/{{ title | slug }}/index.html"
}
When using WebC I should instead be using WebC for that? Feels like a challenge? I would preferably use eg. liquid for my permalinks and only WebC for my actual HTML
You may use data variables here (and template syntax, too). These will be parsed with the current template’s rendering engine.
This plugin could provide a custom behavior by setting permalink
in compilerOptions
to a function or false
:
eleventy-plugin-webc/src/eleventyWebcTemplate.js
Lines 84 to 90 in f7bc146
I think it should done of:
- Have an example of a dynamic permalink in WebC
- Provide an alternative renderer for permalinks
- Disable permalink link rendering if its not feasible with WebC
Activity