mermaid VS markwhen

Mermaid - https://mermaid.js.org/

This is an Issue I opened up for a potential feature. A couple weeks ago, I added nomnoml support to ChatCraft. ChatCraft renders previews for Mermaid and Nomnoml.

Mermaid JS is a powerful JavaScript library that allows developers to create complex diagrams and visualizations using simple text and code syntax. It’s a lot like markdown, but for charts instead of plain text.

Currently, ChatCraft supports Mermaid rendering. This feature request involves adding support for nomnoml rendering. Nomnoml is similar to Mermaid, in that they're both used in generating uml diagrams.

Marimo looks and feels great!

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 :-)

https://mermaid.js.org/

This feels like the LaTeX version of Mermaid.js [0]. I can do anything with it, but I gotta learn a lot of new syntax. So, really cool! Gonna have to dig into this.

[0] https://mermaid.js.org/

The creator of this (Chee Aun) is quite prolific and creative with their work (https://cheeaun.com/projects/).

They created https://cheeaun.life, a timeline of their life, more than 10 years ago (which looks to be kept up to date), which was my inspiration for markwhen (https://markwhen.com).

Markwhen

Looks like markwhen[0]. When making it, which initially started out as a strictly timeline-making tool, I realized it is essentially a log or journal language - write a date, any date, and add some stuff to it. Good for notes, blogging, a calendar, etc etc.

[0] https://markwhen.com

https://markwhen.com

I’ve had a lot of these thoughts when working on markwhen. It’s basically turning into a calendar and planning IDE, pretty excited about where it’s heading.

https://markwhen.com - very cool. however, If I could share with you, I would see the value in following case: if I could connect my calendar(s) to it and see what is going on and overlay it with the data here in comment. Use case is both - for retrospective and for planning (for example if you're preparing the meeting and don't want to share content just yet, or jotting something for time in-between meeting what to do, etc)

I realized just over the weekend that the side project I'm working on is in fact a kind of journaling language. It has passed through a number of iterations, started out as a timeline maker (and still does that best), but at the end of the day is a spec for writing what happened when. Or indeed what you hope will happen in the future - I find it's a good planning tool too.

I find myself actually journaling now that I don't have to think about where I'm going to do it, or in the case of most note-taking apps, which note I should put my current thought in. Journal it first, and if it deserves to be somewhere else, move it later.

The project is https://markwhen.com

https://markwhen.com

Timelines in markdown (gantt, calendar, map, other views)

It's open source (https://github.com/mark-when/markwhen) and there are some paid options for storing markwhen documents in the cloud.

Straddling paid SAAS and open source is a bit tricky and I still haven't figured it out completely yet. I have some sponsors as well as some paid saas clients but it's not quite paying the bills yet... I like working on it though, hopefully I can find the right balance or a different revenue model that works better.

Are you familiar with markdown? If so, try markwhen.