There have many discussions about how the flexibility of Gramps allows (and, indeed, requires) users to figure out what works best for them, and how new users often struggle because of that. There have also been many feature requests for UI changes to help both new and experienced users to work more efficiently.
What I would like to discuss here is not yet specific enough to be a feature request, but may eventually become one. (I’m thinking long-term, like 6.0, not 5.3!)
Suppose Gramps had a concept of a “workflow” which consisted of a set of related UI actions that could be ordered and parameterized in various ways (sort of like a flow chart, though it need not be presented that way).
There could be a number of sample workflows included in Gramps, which new users might find helpful, and which experienced users could modify (or create new ones).
The workflows would leverage existing UI elements (add a new person, copy them to the clipboard, etc.) along with some “smarts” (add a new event for the person that I just copied to the clipboard, etc.).
I guess the idea is somewhat analogous to a “macro” in a program like Excel, or a “wizard” in many other applications", but I don’t want to limit anyone’s thinking in those terms.
And I wouldn’t expect this to help with trickier workflows such as merging databases.
To facilitate further discussion, if any is merited, it might be helpful to reflect on some of your own current practices, and whether and how they might fit such a paradigm, or better ways of generalizing it.