Any more thoughts on above?
Im willing to contribute to the Neos project and add those options if some of the issues are resolved.
The setup installer in developer preview currently does not work.
Even after reading the manual the cms seems a bit of a "tech-guy-with-deep-understanding of the system?kind of CMS.
For example errors in javascript that break the UI with error and no good backtrace.
So it feels a bit like, you could get into trouble with the CMS and things could be hard to debug/fix with a limited and still-learning knowledge
sorry it took so long but it is quite hard to answer a list of 20 bullets.
Many of your questions are looking like you are trying to extend Neos.Demo. This package is meant to show the features but it is not the code you should build your site upon. I recommend to create a custom site-package, you can copy Neos.Demo if you like, and change the things you have too.
We are aware of this and this is partly the reason why the ui is currently rewritten in react. The page will be displayed in an iframe and thus js errors can no longer break the whole Neos.