Current settings are chaotics and hard to navigate for users. Especially the "extensions" section that is the core value proposition of bonfire is relegated to a single view, where both data schema, external libraries and custom extensions are merged together leaving no room for users to understand what they can do.
I would propose the following architecture where we split extensions that can be enabled / disabled from the rest of libraries and data schema ( I put those under "advanced" section).
Also I think listing the enabled extensions in the man setting view is important, so that users can have a way to know what they can enable/disable directly from the settings page and dig more into the extension view to see all the options..
here an improved version:
Further changes i propose are the following:
Merge preferences and appearances
Merge default roles and custom roles
Merge boundaries and additional extensions settings ( not sure if that page is a catch-all extensions settings or only related to the boundary one)
Current settings are chaotics and hard to navigate for users. Especially the "extensions" section that is the core value proposition of bonfire is relegated to a single view, where both data schema, external libraries and custom extensions are merged together leaving no room for users to understand what they can do. I would propose the following architecture where we split extensions that can be enabled / disabled from the rest of libraries and data schema ( I put those under "advanced" section). Also I think listing the enabled extensions in the man setting view is important, so that users can have a way to know what they can enable/disable directly from the settings page and dig more into the extension view to see all the options..
here an improved version:
Further changes i propose are the following: