On the Salzburg sprint we discussed different editing modes and their naming to come to a clear definition of the term “structured-editing” that was over the years used for various different concepts. This document tries to define the terms we will use in future to talk about the various editing options neos offers now and in future.
- Inline Editing refers to changing the properties by directly interacting with the rendered result or a simulation of the rendered result. Inline editing is implemented by RTE editors like CKEditor.
- Structured Editing uses specialized widgets to modify the properties of a node. Those may be input fields or widgets like datepickers or media selectors. The inspector implements structured Editing of the meta-information of the Neos-nodes.
- Inline structured Editing refers to editing node-properties at the location they are rendered in the frontend but using specialized widgets which may or may not be the same as are used in other structured editing modes. An example for such a mode is provided by the Flowpack.StructuredEditing package by using inspector-editors inside the content frame.
- Raw Editing Mode refers to an improved raw content mode that would be using the structured editing widgets instead of Fusion rendering to modify the properties of a document node and possibly its children. By using the whole screen instead of the sidebar much more controls can be shown at a time and nested nodes can be edited as well. This mode should boost the usecase of Neos as a headless CMS, which would allow to use Neos as a content API source, without defining any Fusion code.