Some markdown items get their own special <template> for instance, open positions...
Instead of handling it in the vue template, Nuxt-content allows for global components to be invoked from the markdown.
We should evaluate pro/cons of this.
Few that come to my mind
pro:
simple templates
reusability across categories
cons:
content creators need to be aware of vue components. However, they also need to be aware of many fields in the ymls..
I think this would be good for simple styled items like buttons, but I think expanding it much beyond that might make the line between comment and code a bit iffy.
Some markdown items get their own special
<template>
for instance, open positions... Instead of handling it in the vue template, Nuxt-content allows for global components to be invoked from the markdown. We should evaluate pro/cons of this.Few that come to my mind
pro:
cons:
ymls
..