Welcome and thanks!
Status is waiting for Bike 2 to be released. Then will start on Bike iOS part time, while also pushing Bike 2 forward. Current status of Bike 2 is in progress with some preview releases made. Foundation good I think, but lots of details to go.
No. One problem with markdown and outlines is there doesn’t seem to be ONE clear way to make the mapping. There have been some scripts shared, but nothing’s built in.
Few thoughts:
-
I think some people use DevonThink to store multiple outlines. I think a benefit is you can use Bike’s native file format, meaning you don’t loose things like row IDs.
-
A big part of Bike 2 is a much more powerful extension system. This could make commands like “Copy as Markdown” pretty easy to implement, though that doesn’t quite solve the store it in Obsidian desire.
I just use system standard font, and I think that’s the best option for Bike 1… or at least you should choose a font with variants for all the different bold, italic, code formatting.
Another big feature of Bike 2 is stylesheets. That should allow for much more font and layout exploration. With the stylesheets you can include lots of different fonts in a single outline.
Stylesheets are low level and technical, so not everyone’s cup of tea, but they show what is possible. Here’s a Bike 2 stylesheet demo:
Note: Bike 2 user guide referenced in video is going through some updates (as of this afternoon) and changes that I’m making are describing the upcoming Bike 225 preview. I hope to release 225 tomorrow or the next day. It has quite a few changes that break things… thought the core API and design is still the same.