Deprecating stratic-parse-header in favor of YAML frontmatter made it clear that the current "attach properties directly to the file" approach is a serious composability problem. The consumer should be able to drop in pretty standard Node modules for the parsing step and with the custom properties, they can't.
This might also simplify post.jade, but I'm not sure. I think gulp-attach-to-template will probably stick around, which means that this won't help. But maybe not.
Deprecating
stratic-parse-header
in favor of YAML frontmatter made it clear that the current "attach properties directly to the file" approach is a serious composability problem. The consumer should be able to drop in pretty standard Node modules for the parsing step and with the custom properties, they can't.This might also simplify
post.jade
, but I'm not sure. I thinkgulp-attach-to-template
will probably stick around, which means that this won't help. But maybe not.Moved from straticjs/generator-stratic#4.