Creator here - glad to see people like markwhen!

Been working on markwhen for a few years now, originally inspired by cheeaun's life timeline that another commenter posted about.

At this point markwhen is available as a VS Code extension, Obsidian plugin, CLI tool, and web editor in Meridiem.

Some recent markwhen developments:

- Dial, a fork of bolt.new (Stackblitz's very cool tool that leverages AI to help quickly scaffold web projects): an in-browser editor that lets you edit existing markwhen visualizations like the timeline or calendar or make your own. I just released that yesterday so it's still rough but I have big plans for it (it's one of the visualizations in meridiem)

- Event properties: each entry can have it's own "frontmatter" in the form of `key: value` pairs. I wanted this as I'm aiming for more iCal interoperability in the future, so each event could theoretically have things like "attendees" or google calendar ids or other metadata. This was released in the last month or two.

- remark.ing: this one isn't ready yet by any means but it's like a twitter/bluesky/mastodon-esque aggregated blog site. So you write markwhen and each entry is a post. In this way "scheduling" a post is just writing a future date next to it, and you have all your blog in one file. This one is a major WIP

This is neat! It reminded me of this project by cheeaun that enables one to create a visual timeline based on a simple texted based format. The purpose was to plot one's life events in a visual way.

https://github.com/cheeaun/life

Sample file (from the repository):

    @USERNAME's life
    ===============

    - 24/02/1955 Born
    - ~1968 Summer job
    - 03/1976 Built a computer
    - 01/04/1976 Started a company
    - 04/1976-2011 Whole bunch of interesting events

This is pretty cool! I'm the developer of a semi-automatic electronic logbook system for sailboats: https://bergie.iki.fi/blog/electronic-logbook/

Right now I'm using YAML for the file format, as I wanted something that would be reasonably readable for both humans and machines. Markwhen would also fit the bill nicely, so that's something to consider, at least as an export format. My entries have a lot of properties, though (stuff like wind speed, vessel coordinates, barometer, etc). Traditional ship's logbooks were done in a tabular manner to record all this. So I'm not sure if that would end up looking quite messy. Here is an example of a day of log entries in the current format: https://github.com/meri-imperiumi/log/blob/main/_data/logboo...

I'm using these also for some data analysis, like watermaker membrane health, or sailed miles per crew member.

Note that Mermaid also supports timelines (if it is new enough): https://mermaid.js.org/syntax/timeline.html

Mermaid is supported by gitlab/github and other markdown editors (within code blocks).

Again reimplementing Emacs Org mode. Nice work!

This looks terrific, but honestly Markdown is a document markup language. Org mode, while superficially similar in scope, is actually a data storage and exchange format. The data manipulation and querying built around Org mode are unlikely to be replicated in Markdown.