Embed Notice

@db @eleventy by default they throw on conflict, same as if you have two templates with colliding permalinks. But this approach gives a controlled place to do testing logic (ie, “does something already exist in the pile of pages to be rendered? Is there a file on disk that “claims” a given content id in its frontmatter?”) before programatically injecting a virtual file for the content. With the pagination method, I could never find a reliable way to do that.