Somewhat related T232395

@Volker_E I had imagined something like this (perhaps with the list items rearranged):

Thanks @alexhollender for clarification. In case I've been unclear in the task description I see a flat hierarchy currently as best option too – because we're installing a level that we barely explain in the components itself, nor is it usually used in context of applying our components. But the expanded variant seemed to be my understanding of our conversation as alternative option as well.

Simplified navigation hierarchy proposed in https://github.com/wikimedia/WikimediaUI-Style-Guide/pull/315 cc: @Pginer-WMF

+1 to flat hierarchy and directly showcasing what we have. And since LukeW, we all know that obvious always wins. In regards to sorting the list items, how about an A-Z approach like this:

• I suggest to use singular not plural for components, it’s easier to scan/read (if that’s been discussed/decided/discarded before: ignore this comment).
• For the future, have we thought about including a basic search filter for nav items? I find it extremely helpful when looking for a component.

@schoenbaechler Singular vs plural is an interesting question. Guess it came out of a) using plurals for many fo the “Visual Style” subsections and b) because “Buttons” stand for various types of buttons? But I'm open for majority vote here, will put this into a task of its own though. Captured in T239971.
Search goes alongside a non-static website, which was once started in T164449, but ran into technical cost-benefit issues. It's currently not possible and we have to rely on our SEO being so good, that we can lean back and let “Wikimedia UI dropdown” be googled for us.