I was an early adopter of Bike because of the fluidity and even joy I experience while working in it. I eventually stopped using it because there was no real way to get stuff “out” into other programs. The addition of this feature nudged me to take a chance and renew my license. I’m so glad I did.
Markdown is a feature of Bike 2.0 which is still in preview, but you can download from posts in the releases category.
In 2.0 Markdown (a specific subset) can be used for file format. Or you can use the standard HTML based format and then get markdown out using Bike > Edit > Copy > Bike Markdown.
Hmm, disappointing, since Bike Markdown is not actually Markdown. However, I think I can see how to write a script that will do the conversion, so it’s better than nothing.
I think anywhere that I have deviated from “standard” markdown I have only done so because Bike’s data model can’t be represented in standard markdown. I also think these cases can be avoided if you don’t use the unrepresentable formatting in your document… for example row level attributes, etc.
Perhaps more a family of dialects (each variously optimised) than a specific idiom ?
Commonmark, for example, reaches less of HTML’s inline formatting than Bike (no highlight, strikethrough, superscript or subscript),
and like other Markdown dialects, muddies the categories of decoration and structure, leaving the latter inadequately defined for the purposes of outlining.