Should templating syntax in contents be rendered?

[ismay]

Don't want to duplicate metalsmith-in-places functionality. But maybe this defines the goals for both plugins pretty well:

metalsmith-in-place: A generic template plugin that simply renders the contents in each source file, passing [the rendered contents] to the templating engine WITH the yaml matter in the top of the file.

metalsmith-layouts: A 'layout' plugin that has support for the [layout] template yaml which will pass the rendered content from the template onto the main layout. Again, this would conflict if you was using something like swig or nunjucks so that would have to be noted when using the plugin. It's really just a plugin for templating engines that don't support template inheritance.

from: segment-boneyard/metalsmith-templates#35

Metalsmith-layouts could be easily used for blogs rendering .md files into a main template, etc. Whereas metalsmith-in-place would support more diy, complex templating use-cases.

So basically the support for a layout yaml property is what separates them. Which doesn't mean templating syntax in source files shouldn't be processed by metalsmith-layouts, I'd say. Or are there reasons not to do this? You could also just drop a metalsmith-in-place instance in front of it of course..

[ismay]

Probably easier to just use metalsmith-in-place