Acceptance criteria:

• verify the points laid out below against the PR proposed
• if needed - complete the PR
• in case of blockers - make sure to have follow-ups with the links arranged

Disclaimer:
The "issues" reported here may have arised due to the "work in progress" of the Magnolia 6 UI framework. 
While the app basically works, the UX on some of the dialogs / actions seems confusing (at least for me), and there also might be an error on the action Publish.

 Action Add folder

The textfield to provide the name of the new folder contains the name of the parent folder. That's confusing, people may think that they are on the way of changing the name of the parent folder.

Action Add file

The textfield to provide the name of the new "file" contains the name of the parent folder. That's confusing. (See above)

Action Edit file

The editor doesn't take RETURN - which in fact disables direct editing within the browser.
Currently you must create the file outside on another editor and then copy/paste to the app. MGNLUI-5285

Action Publish

-
Given: Create the file /admincentral/foo/bar.yaml
When I try to publish bar
Then an error occurs, since the parent foo has not been published. ✔︎
-
Given: Create the file /admincentral/foo/bar.yaml
When I try to publish far
Then, again an error occurs ...
... Parent content /admincentral is not yet published or you do not have write access to it. ...
Here the error is wrong. /admincentral also exists on the public context, and I have tried the it via superuser.
 Maybe that's a bug a needs a distinct ticket.Actually ... IF I publish admincentral first, then I can publish foo too, however, that should not be necessary.

Look&Feel of the Dialogs generally 

Please add a title e.g. could be the name of the action.
i) It gives the dialog a certain context
ii) We will need this title most probably for the ui tests :-|

Will be done as part of  MGNLUI-5305