KOkoch·Jun 19, 2023
Sounds like you might be writing markwhen (though it expects a colon after each date or date range)
https://github.com/mark-when/markwhen
In Plain text journaling in Vimmark-when
markwhen
HTML2022–2023
mark-when / markwhen
markwhen
Make a cascading timeline from markdown-like text. Supports simple American/European date styles, ISO8601, images, links, locations, and more.
4Distinct people
11Mentions
0Explicit recommenders
4.9KGitHub stars
What to know before exploring
What it is
Make a cascading timeline from markdown-like text. Supports simple American/European date styles, ISO8601, images, links, locations, and more.
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:54:37 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by month11 dated mentions
Observed mentions: 2022-06-20 16:31:44 UTC to 2023-06-19 17:12:24 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Jun 2022 | 2022-06-01 00:00:00 UTC | 2022-07-01 00:00:00 UTC | 6 | 0 | 6 |
| Jul 2022 | 2022-07-01 00:00:00 UTC | 2022-08-01 00:00:00 UTC | 0 | 0 | 0 |
| Aug 2022 | 2022-08-01 00:00:00 UTC | 2022-09-01 00:00:00 UTC | 0 | 0 | 0 |
| Sep 2022 | 2022-09-01 00:00:00 UTC | 2022-10-01 00:00:00 UTC | 0 | 0 | 0 |
| Oct 2022 | 2022-10-01 00:00:00 UTC | 2022-11-01 00:00:00 UTC | 0 | 0 | 0 |
| Nov 2022 | 2022-11-01 00:00:00 UTC | 2022-12-01 00:00:00 UTC | 0 | 0 | 0 |
| Dec 2022 | 2022-12-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 0 | 0 | 0 |
| Jan 2023 | 2023-01-01 00:00:00 UTC | 2023-02-01 00:00:00 UTC | 1 | 0 | 1 |
| Feb 2023 | 2023-02-01 00:00:00 UTC | 2023-03-01 00:00:00 UTC | 0 | 0 | 0 |
| Mar 2023 | 2023-03-01 00:00:00 UTC | 2023-04-01 00:00:00 UTC | 2 | 2 | 0 |
| Apr 2023 | 2023-04-01 00:00:00 UTC | 2023-05-01 00:00:00 UTC | 1 | 0 | 1 |
| May 2023 | 2023-05-01 00:00:00 UTC | 2023-06-01 00:00:00 UTC | 0 | 0 | 0 |
| Jun 2023 | 2023-06-01 00:00:00 UTC | 2023-07-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
11 sourceshttps://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.
My other problem is not only am I not good at marketing, I don't like doing it. But I also know it's the other half of the equation.
In Ask HN: Side projects making less than $2k MRR, what's your project?Show HN: Markwhen: Markdown for Timelines
59 points · Open discussionShow HN: Markwhen: Markdown for Timelines
2 points · Open discussionI have hit this problem in a project of mine[0]. Users can zoom the timeline in and out, and what this does is adjust the width and the scrollLeft of the zoomed element [1]. And zooming is exponential, so you very quickly get very large values.
Obviously I have feature requests for supporting both larger and smaller time scales so I'll have to figure something else to do. My initial inclination is to virtualize the scrolling, so the element has a minimum and maximum width, and when the user zooms in and out (beyond/close to the min/max) I reset the view and the scroll position. You definitely have to hide the scroll bar in this scenario as it would be jumping all over the place.
[0]: https://github.com/mark-when/markwhen/blob/9823e44d0445d3bf1...
[1]: https://github.com/mark-when/markwhen/blob/main/src/Views/Ti...
In CSS lengths in Gecko are limited to 17,895,697 pixels (2010)For all those who are requesting ISO8601 dates -- according to the GitHub repo [0] these are already supported:
> Dates: A date can be expressed in a few forms. Human readable dates are supported, like 1665, 03/2222, or 09/11/2001, as well as IO8601 dates, like 2031-11-19T01:35:10Z.
[0]: https://github.com/kochrt/markwhen
In Show HN: Markwhen: Markdown for TimelinesHey! Thanks for the workaround. Still, I second this feature request, and opened an issue in your repo.
https://github.com/kochrt/markwhen/issues/35
Awesome project. Thanks for sharing.
In Show HN: Markwhen: Markdown for TimelinesNot right now, but it's something I've been thinking about, in addition to separating the parser out
https://github.com/kochrt/markwhen/issues/32
In Show HN: Markwhen: Markdown for TimelinesYeah, so long form 8601 are supported
`2022-08-02T23:00:00.000Z - 2022-08-03T00:00:00.000Z: Event`
but in general I do need to figure out a way to allow more customizable date parsing.[0]
[0]https://github.com/kochrt/markwhen/issues/27
In Show HN: Markwhen: Markdown for Timelineshttps://github.com/kochrt/markwhen is about a month behind the live website.
The upstream repo that the live site uses is available to sponsors.
In Show HN: Markwhen: Markdown for TimelinesLicense says yes.
https://github.com/kochrt/markwhen/blob/main/LICENSE
> kochrt/markwhen is licensed under the GNU Affero General Public License v3.0
In Show HN: Markwhen: Markdown for Timelines