I've seen this pop up a few other places in the ecosystem already, defined as:
content: {
"$type": "site.standard.content.markdown",
"text": string,
"version": "1.0"
},
I think it would be good to have an explicit markdown type built in for content.
I have come to the conclusion that a community implementation is indeed the best way to go too, which is how I ended up the author of markpub.at :)
I forgot this was still open, but I'm curious about the weaver model, I hadn't seen it before! I wonder if the markpub.at facets could support that. As such I'll close this for now, but open to commenting on any future implementations here too!
Haha, no worries! Not an obvious connection. Hopefully though this issue does bring more people to try it out and give feedback!
there are already community initiatives for this content type you might want to take a look at: https://markpub.at/
we have been going back and forth on this. its hard to add content types as we don't want to dictate content types. but we have had requests for this so much that we may implement it. but we have to think through the best implementation for this.
i am partial to the weaver implementation of a markdown content type too. the best way to showcase good lexicon design is through iterating and building an actively used lexicon. weaver has been refining their markdown based lexicon for a bit.