Could of went either way really, YAML is a superset of JSON, so in theory, you can switch between them at any time.

I think we wanted JSON at the time because it just relied on less extra packages when working inside of the JS ecosystem.

So yeah, if anyone wants to make a resume.yaml, we only need to add an extra step to convert it to json for them to use any of the tooling.

Fair. I guess the reason I asked is because YAML is a little easier to play with for humans, especially since some sections need things like new lines among other things. Doing a YAML text block is easier to read and write than JSON's quoted string with new lines replaced with `\n`.