@dimaip started a poll on twitter the other day and asked what kind of improvement people would like to see. I suggested better dimension support and some other folks jumped in as well. That’s why I’m gathering the feedback regarding that topic.
Show node usage in other dimensions:
For editors, who are working in a multi dimensional workspace (eg. language), it would be very helpful to see if the currently selected document node is defined within other dimensions. In general better feedback for the editor would be very helpful in that regard.
Confirm deletion of a node:
For instance, if you have a German (DE) and an Austrian (AT) language dimension and the DE is configured as a fallback of AT, deleting DE could lead to an inconsistent content representation for the AT variant. Nodes defined in DE would simply not be available anymore.
A possible solution for that (IMO expected behaviour) could be a confirm message before deleting a node, if it is defined as a fallback and exists in that other language version.
A more complex solution would be, that you get a copy prompt popup asking you if you would like to copy the missing nodes to the AT variant if you delete the DE node.
The basic question is what is the expected scenario anyway?
Optional editor notification before creating a new document node
Imagine you are an editor from France responsible for translating/creating content for the French market. The base language is English and lots of document nodes are already created. If you are NOT aware of the process of copying nodes from the English version before starting to translate it, you end up with two separate document nodes which are not linked to each other as they are supposed to be. In my experience that editor starts creating new nodes instead of copying them.
tl;tr the process is often unclear for the editor
@kapale create a related github issue -> https://github.com/neos/neos-ui/issues/1860#issuecomment-387343164
A simple message for new editors would help a lot to guide the editor into the right direction before accidentally starting a mess.
If some of you have more or better input in that regard, I would be more than happy to improve this RFC