Open Jayclifford345 opened 1 week ago
This will also need to support {{< param "<LOOKUP>" >}}
.
The metadata for this lookup isn't guaranteed to be in the file. I think the tool will need an "inherited metadata" option to capture all that external source which can be cascading from parent topics: https://gohugo.io/content-management/front-matter/#cascade-field.
I think the algorithm would be:
<LOOKUP>
in the page's front matter<LOOKUP>
in the inherited metadata option value
{{% param “PRODUCT_NAME” %}}
doesn't expand when rendered through transformer (used pervasively in some docs repos like alloy where I'm testing)