As seems evidence by this issue.
There are plenty of aliases, old APIs, old example code and general confusion floating out there. Some of this is self induced.
I am wondering if anyone is working on a high level glossary of terms to help map all this out?
If there is a work in progress for something like this I would be glad to help. The documentation should very much be like a dictionary with short and sweet definitions, footnote and cross reference links.
To me the utility would come in something that is easy to scan, and perhaps link into the API docs directly where appropriate.