It did make it into the admin sidebar for a beat, but it unfortunately had to be reverted as it caused a couple of issues. But I think it should be back again soon.
Great! Glad you have come to like the new admin sidebar.
Same!
This might be about to change, now that we are considering moving more to the sidebar like the subsections for settings, users and badges. But we are now also looking at adding a search filter at the top of the admin sidebar to make it easier to drill down to find what you need.
And weâre looking at a bigger restructuring of the admin section which should hopefully make it more intuitive to find what you need to configure your site and manage your community. Weâll be starting another topic to discuss that at some point soon.
This is a known issue - we will be getting that back soon.
Ah. @martin this appears to be a bug. The link seems to go straight to /latest instead of to /. I think it should work the same as clicking the site logo/title.
Ah yes my bad, I hardcoded this to latest, will fix it to respect prefs:
I have been away a couple of days this week and buried by many other things that have popped up in my absence. Hopefully I can get to these little fixes next week
This is starting to really shape up! Thank you for the improvements.
Iâm seeing the real benefit of this on the mobile form factor especially.
I guess the only slightly unintuitive thing is the way the drop-down menu changes scope, which is unusual UX behaviour? ⌠but I still like it, itâs far better than having everything on the menu at once and itâs quick to get used to this.
If youâve been using the new admin sidebar and keeping up with software updates, you will have seen some cool new additions since we first started work on it in December 2023. It is our intention to make this the new default soon on new sites and eventually for everyone, so your testing, bug reports and ideas are most welcome!
collapse status is remembered when you return to the admin section
search filter to quickly find sidebar items by name
sidebar sections reflect emerging new admin section structure
We are currently also working on improving and standardizing navigation elements on admin pages beyond the admin sidebar itself. This is a work in progress so expect to see quite a bit of inconsistency right now. The goal is to give each page a title, crumbtrail to help with orientation/navigation, and a sub-navigation menu to access related pages.
In addition, each plugin will get a new page that contains a menu to access settings and other sub-pages related to the plugin. We are starting with AI which currently looks like the below but will get more sub-pages. Once we have figured it out with AI we will apply that styling to all plugins.
More admin pages will get similar treatment. For instance, if you access âWhatâs Newâ and âReportsâ directly from the sidebar now you can see them on their own page, not as tabs on the admin landing page.
The new navigation structure is not set in stone - we are exploring ways to simplify it further by moving some items that are not accessed so often deeper into the structure, and then providing various useful ways to get to them, e.g. via keyword search, section landing pages with information on what you might want to do in the section, and links directly from the admin landing page.
When I use the sidebar on my tablet, I sometimes tap the item next to the one I wanted to tap. So then I use the one I wanted to use, but somehow the filter is not applied. For example, I first clicked âsearchâ and then âexperimentalâ, and this is the result:
And I still donât like that some sidebar sections, which apply a filter instead of using a category, show different settings depending on my locale. The experimental button in the sidebar returns all experimental site settings when your locale is English, but in German, you only get the ones which contain âexperimentalâ in the settingâs name and those which are not translated. The latter are the reason why using the German term also wouldnât show all. [1] I expected to see all experimental settings when I use that section of the sidebar. What bothers me most is that it is not obvious that clicking the same button on the sidebar will show different settings depending on the language you choose as a user.
Iâm also confused when I click âfontâ and settings like âdelete user self max post countâ appear.
Something like âexperimentâ would work to find those with a German translation and those without. However, I think there are languages where this workaround wouldnât work. âŠď¸
This is actually a bug, thanks for pointing this out, we will get it fixed.
This is a good point â we should move these into their own dedicated category.
Yes this is because we have fuzzy searching for site settings; I agree itâs quite confusing though when you click on a sidebar link and see things that arenât an exact match. This needs some more refinement.
For filtering, you have to know the name of what you are looking for. For the things I donât use regularly, I often donât know the name.
Are those translatable? I have the impression they are not. When I change my locale to English and filter for âuserâ, I get four results. One of them does not contain the word user. When I change my locale back to German, I can find three results filtering for âBenutzerâ. To find the one with the keyword, Iâd still have to use âuserâ.
For this example, we havenât actually added keywords to any links except âInstalled Pluginsâ, which gets all of your installed plugin names (which are not translated) as keywords. Do you have any plugins with âuserâ in the name?
All of the sidebar links which we filter on now are translateable. We do need to keep this in mind when adding additional keywords for the sidebar search â we did this when we added keywords for site setting search (which are also not widely used as yet). cc @kris.kotlarek so you are aware
But some of the plugin names are translated in the interface e.g. solved, templates, assign⌠When the plugin in my list is shown as âVorlagenâ Iâd not filter for âtemplatesâ to find it.
Ah yes I see â I know itâs not that helpful, but this is because we have a weird mix of translated and untranslated plugins. Some plugins have their own category for their settings, which can be translated, and we use this for the name in the list:
And some (like User Notes) do not have this, and we just have to fall back to the raw plugin name:
Perhaps we just need a really explicit translation key, something like admin.plugin_name, that can be filled in for all plugins and then translated. I think that will provide more solid ground for the future and allow us to remove these strange hacks and fallbacks eventually.