Use metadata for file data about metalsmith-json-to-files HOT 3 OPEN

The files generated aren't namespaced per se but you do provide it with a pattern to generate the "filename" in the metalsmith files object. I suppose you could add files to the object with a random hash if you didn't want to create files with meaningful names.

1. Yup, provide a JSON or YAML filepath that contains the plugin options. Alternatively it accepts a JS object with the same options.
2. Array of objects defining source files, file pattern, permalink style and any other frontmatter you want carried across.
3. You could pass a JS function within the options to do any data transformations.
4. Covered by point 2 to carry extra frontmatter over.
5. Yes.

(I updated your comment with a numbered list)

from metalsmith-json-to-files.

Hmm, so if I was to use a config.yaml for global site pages for example and do something like this:

index:
  title: 'Home'
  heading: 'Welcome to this site'
about:
  title: 'About us'
  heading: 'More about us'
services:
  web-design:
    title: 'Web Design'
    heading: 'We build websites'
  seo:
    title: 'SEO'
    heading: 'We optimize websites'

Then have posts in another posts.json, like this:

[{
  'date': '2016-07-22',
  'title': 'How to use Metalsmith',
  'layout': 'post.liquid',
  'contents': '# This is Markdown',
},
{
  'date': '2016-07-23',
  'title': 'How to use Liquid',
  'layout': 'post.liquid',
  'contents': '# This is Markdown',
}
]

Would that potentially work?

from metalsmith-json-to-files.

Thoughts on that config?

from metalsmith-json-to-files.