2 ms·
This is pretty nice! It's not always obvious how much engineering it takes to make an app like this that's powerful enough to be useful for daily work without t
by bityard 4y ago
This is pretty nice! It's not always obvious how much engineering it takes to make an app like this that's powerful enough to be useful for daily work without the UX getting in the way.
I think this is the closest I've seen anyone come to solving the problem of having separate "write" and "read" modes for Markdown editing in a web browser without resorting to a split-screen view. It's not _perfect_ (likely due to codemirror limitations) but what's there is pretty well-executed.
I might have to borrow a couple ideas from this for my own effort at a personal knowledge base: https://github.com/cu/silicon https://github.com/cu/silicon
- jasonjmcghee 4y agoI'm a huge fan of how Obsidian approaches it- previewing each token if you're not actively editing it. This is always how I use it. Avoiding separate read and write problem entirely.
- zef_hemel 4y agoThis is pretty much how it works in SB as well. Very much inspired by Obsidian.
- deleted 4y ago[deleted]
- pointlessone 4y agoMy biggest frustration with Obsidian is that it doesn't follow any spec when it comes to raw HTML. They seem to have fixed inline raw HTML at some point but HTML blocks are still broken. They know it and they explicitly will not fix it.
- unqueued 4y agoI never use split-screen view for Markdown. Split-screen makes sense for something more abstract like latex or html. But I do not see the benefit for Markdown. I would much rather have 50% of my screen.