@C-Lodder why don't we go one step further and eliminate com_cache/com_admin altogether and add all its functionality to com_config ?

That's completely beyond my PHP skillset, so I can't answer that

@C-Lodder why don't we go one step further and eliminate com_cache/com_admin altogether and add all their functionality to com_config ?

@dgt41 com_admin is also resposible for the current user edit form as well as updates etc. i don't think we can easily remove the component.

Same for com_cache it serves a complete different functionality scope. (cache vs settings)

@zero-24 depends on the way you look at this. For me com_config should be something like windows control panel or OS X's System Preferences, where the user can accomplish a lot of different tasks.

hmm is'nt windows control panel or OS X's System Preferences just a view over different components?

yup, so maybe we can just follow that root and make e.g. com_admin the control panel for joomla. That will remove a lot of unneeded menus and will improve the UX by a big margin

ok so you just want to move the GUI to one unifined one and not move the seperated code. Than 👍 from me.

Both ways will work, but I guess creating a simple view with icons is far easier than merging few components to one

Currently i have not enough time for another bigger task sorry. I could only add this to a very long todo list, but i guess this would not help much. Sorry. I can help if someone need advice on implementing that.

But the main problem would be that currently the view is stored with the component. So if you try to have one components you need to go a route like com_categories or similiar.

But what about adding a view to com_config / com_admin where you can jump into the different components?