I love the concept though. It kind of reminds me of Excel. It's really hard to tell if "the users" will like it or not, you have to test it on them. But I think "the users" will want some sort of GUI/WYSIWYG.
i'm creating a mavo project right now and i wanna use a simple textarea as a mavo field. (tinymce makes me feel a little icky inside.) but i didn't see anything in the documentation about how i would do that. can i? if so, how?
edit: oh hey. i just acted like it would work, tried it out, and bingo! hey, that makes me happy...
except markdown also makes me feel a bit icky -- too many inconsistencies in the various flavors.
markdown's redeeming value is that it's "popular".
which is also why it's so frightening now, since it desperately needs to be replaced. (it cannot be improved, because xkcd 927.)
speaking of "popular", that's how you describe the showdown converter that your plug-in uses.
one reason it's popular is because it was fast -- the fastest converter, at one time, it claimed.
note the past-tense "was"...
because that time has now passed.
other converters, also coded in javascript (the other big reason showdown got popular) are now much faster and far more powerful.
without getting into all the surrounding drama, i'd recommend that you use markdown-it instead: it's blazingly fast, and has much functionality.
> https://github.com/markdown-it/markdown-it
(functionality is now a better differentiator of the worth of a markdown converter than speed.)
mavo's choice of converter is more consequential than it might appear at the first glance because follow-on effects of differential functionalities will surely impact the success of a mavo project, as will the inconsistencies that will bite users.
all this aside, mavo is a fascinating little tool. :+)