Show HN: Markwhen: Markdown for Timelines
11–20 of 102 posts
Re: Show HN: Markwhen: Markdown for Timelines
#12Any chance you can copy some of this for aesthetics? https://www.chronoflotimeline.com/timeline/shared/3118/Home-...
Re: Show HN: Markwhen: Markdown for Timelines
#13Re: Show HN: Markwhen: Markdown for Timelines
#14https://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 eventsRe: Show HN: Markwhen: Markdown for Timelines
#15Re: Show HN: Markwhen: Markdown for Timelines
#16Re: Show HN: Markwhen: Markdown for Timelines
#17Trying to build a timeline like this:
title: History of the World
0: Foo Calendar's civilization founding.
124: Invention of the Foo Calendar
220: Founding of Bar
1310: Invention of GlooblyGock
5621: Demon invasion.
Edit: After trying it don't think it works for this usecase.
Re: Show HN: Markwhen: Markdown for Timelines
#18This looks very good. Is there syntax for dependent tasks in the timeline? In other words tasks that only start once prerequisites are done. If the date of the original tasks changes, the dependent tasks move accordingly automatically, without needing to edit a full list of dates for each dependent item.
It's a timeline that tracks events and periods. It doesn't seem to have the concept of a task in any way.
Re: Show HN: Markwhen: Markdown for Timelines
#19Re: Show HN: Markwhen: Markdown for Timelines
#20Been 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