Have you considered adding support for mermaid.js in the markdown? I tried including some mermaid.js in a `mo.md` invocation, but it didn't render the diagram :-)
We’ve been thinking about it (but had no requests for it yet). I will look into adding it this week. If you would want to make the contribution, feel free to jump/chat in the discord.
I use text files.
One text file per day, named `yyyy-MM-dd.yml`.
YAML!
Shudder!
But it's the best way I found to enter Markdown with some metadata at the top.
Each day file has multiple Yaml documents, with ids like `yyyy-MM-dd/number`.
I use [ ] for todos and turn them into [x] when they are done.
This way, searching/grepping for `[ ]` gives me a list of stuff not done yet.
I sometimes have a list of things to do in my day.
I move the `[ ]`s to the next day at the end of the current day (or start of the next).
I use Visual Studio Code snippets to enter the metadata.
Example:
---
id: 2023-10-13/1
links:
tags:
project:
text: |
This text field is **Markdown**, not **YAML**.
- first note
- [ ] todo 1
- second note
The `links` item points to other notes by id (it's an array).
IMO the end product looking "average" is quite different from the prototype looking "average", and Noya looks great for prototypes/MVPs.
Put differently, Noya feels like an exploration tool. When exploring, tents are fine. They do not provide a lot of comfort, but replacing them with houses while still exploring might not be optimal :-) Personally I don't mind average tents, as long as they don't leak.
EDIT: Hmmm, maybe Noya is actually between a tent (Balsamiq) and a house (Figma) - something like an RV? :-D
