Documentation does not explain underlying structural model, makes program more difficult to understand

[DocSunset]

The hierarchy / relationship between states, syncs, events, conditions, triggers, intervals, processes, etc. is not explained anywhere in the documentation. Having just been given an explanation from Pia, I find that knowing the underlying model makes many aspects of the program much easier to understand, whereas before I found it quite opaque how these objects relate to each other, which owns what, or even the purpose of certain UI elements such as the "put in new event" and "desynchronize" buttons in the inspector for a state.

It would be great to have an explanation of these concepts somewhere in the documentation (e.g. as a new "In Depth" page), as it makes certain things much more obvious.

[bltzr]

thanks @DocSunset you're absolutely right this should be explained somewhere in the doc (and where you point at seems a natural place)
I guess that's a mission for @jln- then - feel like, Julien ?

[thibaudk]

I actually wanted to make an introductory one in the quick start.
A section called "Working with time".

here is the pr #7