Streamline Content Node Creation When Only One Document Type Is Allowed #18097
Replies: 4 comments 12 replies
-
I like the idea behind this, but I think this should be configurable on the content type so that you can set the permissions to 'single mode' or something and only select one content type you can create. But what would happen if you have content templates, should they be ignored? I think I would want this to be enabled on your example of a news overview with news pages. But when it's not so obvious I really would like to show the available option - even if it is just one - so that it's clear to the editor what he's about to add. Hence the possibility to configure it :) |
Beta Was this translation helpful? Give feedback.
-
Just as an FYI - when you enable collections (previously know as list view) on the document type, you do get that one-click behavior - could be a good workaround for now! |
Beta Was this translation helpful? Give feedback.
-
Apart from the workaround posted above, I think other people at HQ might be of the opinion that a "single-click-start-new-node" might be considered inconsistent and confusing behavior. I can imagine that this would be a great menu item to add, maybe that's possible to do right now, I don't know. |
Beta Was this translation helpful? Give feedback.
-
As I recall from discussion with some of the Umbraco HQ developers. I don't think my wish is so easy to implement. Maybe if was possible to extend the side panel "Create" with the document types. Or right after list of items is ready. Redirect to create node. |
Beta Was this translation helpful? Give feedback.
-
Description:
Currently, when creating a new Content Node in Umbraco, editors must select a document type from a list in the right-hand panel after clicking the "+" icon in the content tree. This process becomes inefficient when only one document type is permitted under a specific parent node.
Problem:
When only one document type is allowed as a child of a specific Content Node, the current workflow requires unnecessary mouse movement and clicks. Editors must:
Alternatively, editors can use the "Actions" menu, which involves even more clicks:
Proposed Solution:
If only one document type is allowed as a child of a specific Content Node, the creation process should be streamlined to a single click. When an editor clicks the "+" icon (or "Create" in the actions menu), a new content node of the allowed document type should be created immediately, bypassing the document type selection step. This would significantly improve the editing experience in scenarios where document type restrictions are in place.
Benefits:
Example:
Imagine a "News Archive" node that only allows "News Item" document types as children. Currently, an editor has to click "+", move the mouse across the screen, and click "News Item." With this feature request implemented, a single click on "+" would instantly create a new "News Item" node, ready for editing.
Considerations:
Beta Was this translation helpful? Give feedback.
All reactions