Workflows with Markdown

One of the things we are aiming to do with Aeon Timeline 3 is unify some of those tools a little bit with the introduction of the Narrative and Outline views for mapping those chapters and scenes, and Mindmap View for that initial idea sketching.

We are aiming for the experience of “Create the data once, and it is available everywhere”, rather than chopping and changing between different apps and trying to pull it all together.

So again, this is perhaps a different topic, but I would be interested to understand any gaps in those features within Aeon Timeline 3 that are better covered by Mindomo or Plottr, so that we can help unify that whole experience.

I guess understanding what format that Markdown file should take would be a challenge.

I could picture it being relatively easy, for instance, to take a Timeline Narrative and turn it into markdown – each step down the tree using progressively smaller headers, with perhaps the item summaries being included as text in between that you could then extend into your writing.

Pulling back out of that structure may be a little more difficult though.

The benefit of markdown is that it is text based and yet still potentially hierarchical.

Matt