Hi, @hlpell. I haven't tried using AT2 for a family tree, but I might be able to give you a few pointers and things to watch out for in getting started. First just a little vocabulary. The parent/child relationship that you are asking about only applies to EVENTS. People in AT2 are often defined as ENTITIES, but entities don't have as much flexibility for adding custom properties. If you were doing project planning, you would use the entity person as a resource or for writing a novel, you would use an entity resource as a character. Using entities allows you to do things like filter your display based on whether a scene has a certain character in or a task involves a particular staff member. You may find creative uses for entities in a genealogical timeline or you may find entities aren't needed. You could, for example, represent a person just as an event with a line that represents their lifespan. Or you could simplify even further and just have a dot (no duration) for each person and aim for more of just a tree of names than any real representation of l ifetime events. If you opt for recording more information for each person, one approach would be to have a parent event for the person's lifespan, then sub-events (child events) for the date they were married, the birth date of each child, date they moved to another country/city, etc... AT2 lets you collapse the parent events easily so you can hide these details when you don't need them. Also, by using events to represent people, you can use the configuration editor to add custom properties to your people. You could, for example, add a new property "Religion". Maybe your family has a long history of being Freemasons and you want to indicate which ancestors were members. You can then customize the Display options to show these added bits of information in the detail view for your event-driven people. Note that you cannot add these extra properties to entities - which is why it was important that you understand the difference. Note that if you elect to use both entities and events to represent your people, you will have somewhat more data entry, but you would be able to easily view the age of the participant for each event. One small challenge you might experience will be how information flows on the screen. You probably won't get a consistent view of information like you would with common genealogy software. AT2 redraws and repositions elements in the timeline based on the zoom level, the length of names, the length of the coloured time bar, etc. All you can definitely count on is the progression of ancestors from left to right, past to present in time, not how they get displayed vertically. If you make Jim Smith (the son) a dependent event of John Smith (the father) and Mary Jones (the mother) and do this recursively back through the timeline, you will get nice lines connecting parents and children (in the genealogical sense). You may find though that you can't control just how those lines get drawn, as again AT2 draws them in automatically and redraws them as objects flow on the screen. Sometimes fiddling with the zoom range can improve the layout. Good luck with your project. I'm sure the devs or others who may have direct genealogy experience with AT2 will weigh in with their own ideas.
Hello @razyr, Thank you so much for this. I am currently writing my second (non-fiction) and third (sci-fi) books in Scrivener. My wife is doing the genealogy for both our families and I'm attempting to create a nice template in Scrivener for her. I have the evaluation copy of Timeline and really like what it does for my Sci-fi, and so wanted to see if I could make it work for my wife. I'm going to try your suggestions and see how it works for my wife. Thanks again, both for your reply and for such a quick reply.