Sneak Peek: What we're working on in Q1 2025

Official Announcements
#63

@AeonRob - I’ve just wrapped up the video and was hoping to discuss text export with you. My recommendation would be to put them into markdown files (.md). Given how much time has passed, I was curious to see how these Q1 goals turned out - do we get them into the latest build?

Do you have a similar video for Q3??

I believe I bought this app several years ago, way before v3 3 and it’s wonderful to see the small team is still at it.

I have lots of thoughts, especially when it comes to how data is currently stored within the app, users’ ability to get that data, or export it. Have there been any discussions about loading this data into a GCP or AWS project & rapidly expanding functionality by integrating AI/ML models or even Knowledgebase Chat Apps? Even just a simple MCP server for Aeon Timeline could get very, very exciting for users, but also what then becomes possible for the application itself.

Considering spending some more time with AT3, and would love to know if you had 15-20 minutes to jump on a call & discuss the progress made thus far, that feature roadmap & if Aeon Timeline has any interest in an MLops Engineer integrating the latest and greatest in LLMs. Simply giving voice commands or talking with your timeline to make edits, for instance…

1 Like
#64

Hi everyone,

Sorry we’ve been a bit quiet lately, but we’re excited to now have an alpha build in the quality control stage as we prep for a beta release in the coming weeks.

We intended to reach this stage a bit sooner, but some things have taken longer than we’d hoped, and we’ve had a couple of issues outside of work to juggle along the way.

@ahansonauthor 3.5 will have a text export to both Word and Markdown :raised_hands: We’ll be really interested in gathering everyone’s feedback on the way this works and how the files are formatted once we’re in beta.

@jcachat Thanks for your thoughts on AI integration. We are very interested in the future potential of that, but it’s not on the immediate roadmap.

1 Like
#65

If you go through and read all the discussions in this forum about export to Markdown, you will find many thoughts on format etc. but you should actually let people decide for themself, what’s going to YAML keys, what the want as headers, and if they want the export to go to a flat file system or a folder hierarchy, and let the users define what that hierachy should be based on… e.g. Event’s, People, items/entities, or more like chapters…
Because, remember that there are many people using Aeon for a lot more than just a writers tool…

My setup in Markdown have a folder hierachy based om objects like people, ships, addresses and houses, companies, ports and journeys, BUT I also have a complete folder hierachy built around how sources connect to repositories etc.

So an export tailored for writers will not do me any good at all.

Just as an example…

1 Like
#66

Jaran, I like the idea of having YAML metadata definable, particularly if it can be mapped optionally to the various item types, relationships, etc. of AT.

I’m not entirely sure about how a folder hierarchy would work, given that MD is just a text file–maybe a hierarchical numbering system appended to the exported .md files would work. No doubt others more capable in this area will see how that might work.

We writers would also love to leverage such export flexibility. :slight_smile: