A Neos backend usability question, maybe a “best practice” of what you have been doing in your real live projects:
Consider the fairly common use-case that we have a marginal column with “content boxes”. Those are placed on the Homepage, but inherited in the tree to all sub-pages, so that the same box appear on all pages.
At some point in the tree you want different boxes, “breaking” the inheritance, and starting a new one.
I TYPO3 I would solve that in TypoScript using “slide:-1”. For the editor, in the Web>Page module they can only see the boxes in the grid on the pages they are placed.
Solving the CR part and the rendering in TS2 in Neos is not the problem.
But: What is the best practice to “visualize” this inheritance and editing experience in Neos for the editor?
In the FE the box is shown on every page. Letting her edit it on every page can be dangerous, because she might not be aware on which pages this box is also being used. And how to let the editor “break out” of the inheritance?