A changing calendar changes the purchase case
Aeon Timeline can define custom months, weekdays and eras. The less obvious detail is when that structure can be edited: the current guide says a custom calendar is editable only while the timeline has no dated events or items. Once dates exist, changing the calendar is a different undertaking from renaming a view.
For an author whose year still changes from eight months to ten between drafts, that is a meaningful limitation. Moving a large chronology into a new tool before the basic calendar settles may create migration work instead of removing it.
A reusable settled calendar is a stronger fit
When the calendar is already defined, a template can retain that setup for future files. The current guide describes creating a new file from the settings, changing the calendar there and importing existing data when a redesign is necessary. That is a route to plan, not an invitation to assume dates can be reinterpreted without consequences.
The distinction also prevents an unnecessary purchase. If the project only needs rough “Day 1, Day 2” order, Aeon supports relative dates; a complete invented calendar may not be needed. Consider the actual kind of timing information before building more structure.
Choose a chronology tool when the chronology is the work
Shortlist Aeon when defined date relationships and repeated views of a setting are valuable enough to maintain. Keep a plain explanation of any calendar redesign alongside a new file, especially when collaborators rely on earlier dates. For a world still exploring the length and organisation of its year, a simpler planning document can remain useful until those rules become decisions. The software is most convincing when it organises an agreed system rather than being asked to invent that system.
Sources & further reading
Editorial review date:
