- Issue created by @balintbrews
Introduce folders in Experience Builder's library to organize components. Make sure all component sources benefit. Allow users to create, edit, re-arrange, delete folders, and place components into them on the UI. When creating code components, prompt the user to optionally select an existing folder, or create a new one for the newly added code component.
Implement folders as a new config entity type to track the name, weight, uiLibrary, and components of a folder. Use uuid as the id entity key instead of a machine name, so renamed folders don't end up with outdated machine names.
SDCs and blocks already have ways to express organization: The former has the group property in the metadata, the latter has category in the plugin annotation. Read these values automatically, create the corresponding folders when new values are discovered, and place the components into them. Provide an easy way for any component source to define an initial folder.
Even the auto-created folders can be freely changed by users: They can be "disconnected" from the component-provided folder values. When a new component enters the system with a group/category that was already used for auto-creating a folder, and that folder was later renamed, the new component should cause a new folder to be created with the original name.
When a folder is deleted, disable all components that belong to the folder. Allow this only if none of the components that belong to the folder are currently in use.
Active
1.0
Page builder
