New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document renderData feature.
#33
Comments
|
also 11ty/eleventy#315 and maybe 11ty/eleventy#329 ? |
|
I’ve been reluctant to document this as I think a better idea for this will crop up and I’m waiting for inspiration 😇 |
|
@zachleat Is there any update on this? I'm working on a simple notes site and I'm trying to set up a standard I tried a few different variables of |
This is just my 2¢, but would anything really bad happen if you just turned on interpolation by default in the front matter. Is anyone really including curlys in those values that they don't want to be interpolated? Maybe I'm missing something here, but it seems to me like the easiest thing would be to turn interpolation on by default and allow people to escape |
I second this. Although maybe a non-breaking change (if any hypothetical person was already using curly braces as content in front matter) would be an option in the Eleventy config file, which is disabled by default? |
|
This would be really useful so I will third it! |
There's no way to get a dynamic, data driven title from pagination right now? That's... a surprisingly large missing feature |
|
@braco I managed it like this, but I wish there was a better way: |
|
Closing this in lieu of new Computed Data feature. Follow along at 11ty/eleventy#481 |
@LandonSchropp @braco @zachleat Where to put this code to make it actually override the front matter definition? ---
permalink: "auditees/{{ auditee.title | slug }}/"
title: {{ auditee.title }}
---
{% set title = auditee.title %}still the rendered page title is |
Related: 11ty/eleventy#216 11ty/eleventy#236
More info at 11ty/eleventy-base-blog#15
The text was updated successfully, but these errors were encountered: