Implement "groupings"

[thiagodemellobueno]

Just as with "mappings" we currently implement .... we could use grouping strings to group multiple fields into keys, this maybe just a modified 'mapping' functionality.

eg.

groupings: [
  content: 'Content_',
  our_promise: 'Promise_'
  meta: 'Metadata_',
]

should we use "starts with" (hithercontent groups tabs in a given template under Tab-Name_, this could help us deal with some complex structures.

alternately, we can also use:

groupings: [
  name: [
    'first_name',
    'last_name'
  ]
  image: [
    '*results-img__alt',
    '*results-img__image',
    '*results-img__caption'
  ]
]

might have to switch from simple indexing to minimatch for pattern matching... coming towards either a naming convention, or some flag mechanism to indicate when / which objects to apply these groupings to is part of design i have not yet considered.

groupings: {
  image: {
    pattern: [
      'portfolio/**'
    ],
    fields: [
      '*-Image__alt',
      '*-Image__image',
      '*-Image__caption/
    ]
}

overall it would be cool if we could create these conveniences and make the parsing of data into something of a 'middleware' so we could hook up to different content stores, and just write mini plugins for each one (reducing the cost / technical debt for swtiching to different content apis (gather content, contentful, eventually a sweet drupal experience outputting a restful api?)

@RobLoach thoughts?

[thiagodemellobueno]

mappings: {
    global: { // applies to all variables in the loop
        title: 'Content_Title', // Map single value
        name: ['Content_First-Name', 'Content_Last-Name'] // Concat values (join with space?)
    },
    article: { // Applies to content with the `article` template
        hero: { // Map nested
            image: [
                { alt: 'Hero-Image__alt' },
                { src: 'Hero__Image' },
                { caption: 'Hero__Image_Caption' },
                { attribution: 'Hero__Image_Attribution' }
            ]
            title: 'Content_Page_Title'
        ]
    }

}

[RobLoach]

Hmmmm, it could, but unsure we'd need it. Is mappings front-matter from a file? Or from Gather Content?

Perhaps this is just an extra function that's called from the plugin? Collections would've do it right?

[RobLoach]

https://www.npmjs.com/package/json-mapping
https://www.npmjs.com/package/node-json-transform

1. Add json-mapping to project
2. Introduce a gathercontent-mapping.metadata or something???
3. Have gather content addon read the mappings