Hi Rob, I love the concept. I've played around with it for about 20 minutes now. I use obsidian for almost all my notes and documentation because I like keepin

Hi Rob, I love the concept. I've played around with it for about 20 minutes now. I use obsidian for almost all my notes and documentation because I like keeping everything as close to plaintext as possible. I also currently use Omniplan for timelines and Gantt charts, so that is what I would be comparing Markwhen to, in terms of functionality. Omniplan is a very mature app and I recommend giving it a try if you haven't yet. There's a lot of ideas in there that you could import to Markwhen. Thoughts: - The travel itinerary planning aspect is interesting. I've never found an itinerary planner I liked, and many of them cost a substantial amount. I'd like to see more about this from markwhen. - The syntax is somewhat confusing on first reading. I am used to using `###` to mark out headings and paragraphs and this conflicts with standard markdown in that sense. though I havent used Markwhen enough yet to climb over the learning curve. Two biggest feature requests from me: - release an Obsidian plugin for Markwhen so I can have Markwhen timelines inside my exisiting Obsidian notes. I'd be happy to pay a one off licence for this even though it would be locally run. - Find a way to do automatic dependency levelling so that when one task is dependent on another, and I increase the time taken for the first task, then the dependent one is automatically moved forward appropriately.