Standardising the front matter about gcweb

[masterbee]

@thomasgohard , JSON please since most of the templates variables are being passed as JSON variables.

[thomasgohard]

@masterbee PR #116 is in, with JSON.

[nschonni]

Core WET is all YAML for front matter

[thomasgohard]

@nschonni Do we need both repos to be standardised on the same? I think it's fine to have one repo using YAML and one using JSON. As long as, within the same repo, all files are using the same language.

[nschonni]

Yup, just pointing it out

[pjackson28]

@nschonni @thomasgohard We should pick one for both to make it much easier to sustain (and so we have built-in examples). I personally don't have a preference between YAML or JSON so whichever is the better one to support is the one we should go with.

[thomasgohard]

@pjackson28 How about standardising on JSON then?

I think more people will already be familiar with it. I know that @fbernard2 and I spent a lot of time trying to figure how to code certain data structures in YAML that I could have coded in JSON easily.

[pjackson28]

@thomasgohard Sounds like a good justification for JSON then. We need solutions fast so if JSON can be done much quicker and more people can support it then it seems like the right way to go. Could you please update core with the JSON solution you come up with so we have consistency across repos? This will be important as the GCWeb theme is going to fall under wet-boew soon.

[masterbee]

@thomasgohard , @nschonni , @pjackson28. I vote for JSON since less indenting ( like Coffeescript ) and more about syntax. Also plugins like tables use it in the data-wet-blew attribute, so I would keep it the same all over.

Just my 2 cents.

[thomasgohard]

OK. I'll update wet-boew to JSON tomorrow.

[thomasgohard]

Standardisation of front matter to JSON for wet-boew is done: wet-boew/wet-boew#3428.