Currently, we force the user to create a collection or go through a grouping of something (a type of page, collection ...) to be able to create/select something
I think it's a step that could be solved with this proposal:
1- Right now the user loses the reference where he is, forcing him to create a collection first
(In the case of the fragments, we would solve the conflict of seeing the title of fragments and the tab of collections that is quite strange for the user, who expects that he will create fragments and what he creates are collections).
With this solution, users will see actions that the can do without navigating through collections
2- Information Architecture: Quick Navigation through a local navigation (different collections) showing the contextual content of each navigation and all of this under the title of the section that users are editing
3- Besides, that it is a standard template viewer like template monster, wix, weebly ... .with the filters of the collections on the left and the content on the right, come on, which is easily recognizable by the user, is not something new, users are quite used to this type of navigations to create/select templates.
- Master / Detail *
An M / D pattern like this proposal would help us simplify the requirement that a template must always belong to a collection. That menu component on the left (master) is a component that we already use now (or we want to start using it in the administration part). With the option to add elements to that "menu"
- Hierarchies *
It would reinforce the M / D pattern with a good hierarchy in the detail header. That would help users understand the pattern quickly.
- Contextual Actions *
It would move the contextual actions from the M / D menu to the detail component. The same as we are already doing in system settings and other places of administration. This would simplify the interaction and we would give a clear message to the user that if you want to do something in that collection all the actions are in the highest hierarchical element of the detail (export, import, etc ...)
- State 0 and empty *
It would have to work state 0 in which there is no created collection and suggest to the user that as there are no collections created there is nothing to show and that he must create one. Or start with a collection already created by default (although the user could also delete it and get back to state 0. On the other hand, the empty states that we normally use would have to use them every time a collection is empty or has just been created.