The idea is to have a new workbench part, defined by classes annotated with @WorkbenchPreferences, that will be like screens. They will implement a screen responsible for the editing preferences.

Also, already the PreferenceStore injection point can be annotated with @ComponentKey("component-id") (on both client and server code), so they can have a componentized scope hierarchy defined. More details on Uberfire Documentation.