You are correct, Bertrand: I should not have spoken as I did.
And I am frustrated.
I have spent a great deal of free time trying to get a developer's understanding of this platform.
It offers me the promise of being able to add functionality to serve my needs and those of clients and markets, and maintain a core CMS capability to enable quick turn-around on content changes.
But it really has been hard to get a good grasp of everything that's involved to manage sites and develop functionality.
I've read the one book, watched the Pluralsight video's, read all the documentation, and read the discussion forums in historical order.
really only the forums address the issues that are important to me.
But the answers you and your team provides are so brief, and only address the 'very next possible step', that most of the time they just provide a new concept to be researched.
So I've had to find time to disect the platform the same way I would a big chunk of legacy code: first having to deduce everything it does before I can start to deduce how to work with it.
And one thing that is extremely hard is the very arbitrary use of nomenclature like 'shape', 'part', 'content', 'driver' etc.
They really do not operate or produce code or data elements that act like or are used like their names.
This platform deserves a book that explains the platform components and how they interact.
But still, thanks for providing it.