[meta] Move libraries links under appearance

Grimreaper → credited vmaucorps → .

Sounds good to me!
It would be nice to group them under one entry but I don't know which module should carry the root element.

I don't know which module should carry the root element.

We were thinking about making ui_suite a metapackage for easier installation and easier dependency management: ✨ Turn ui_suite into a module Active
if we do that, it could also be a proper Drupal module and host this link.

Or, this link is in each module. And become it is always same plugin ID, there is no duplication.

Child issues for each ecosystem modules created.

So, according to those MR:

• https://git.drupalcode.org/project/ui_patterns/-/merge_requests/42/diffs
• https://git.drupalcode.org/project/ui_styles/-/merge_requests/35/diffs
• https://git.drupalcode.org/project/ui_examples/-/merge_requests/12/diffs

You are proposing this hierarchy:

Appearance
>> UI Suite
>>>> UI Patterns library
>>>> UI Styles library
>>>> UI Examples library

2 feedbacks:

• I am not comfortable introducing "UI Suite" term here. A lot of people are using "UI Patterns" or "UI Styles" without caring about "UI Suite" project
• I guess people don't care about module names, they want to see design system artefacts.

So, an humble proposal (I am not fully convinced about it):

Appearance
>> Design systems
>>>> Components library
>>>> Style guide
>>>> Example pages

Thanks for the feedback.

I like your proposal, but as you are not fully convinced, what do you think about the following proposition:

Appearance
>> Library pages
>>>> Components
>>>> Styles
>>>> Examples

"styles guide" == "styles library", no? let's avoid this term if not clear enough for us.

Other proposal:

Appearance
>> UI libraries
>>>> Components
>>>> Styles
>>>> Examples

Currently the last proposal is the better, we are on the right path.

One last proposition:

Appearance
>> Libraries
>>>> Components
>>>> Styles
>>>> Examples

Also should it be reflected in the route paths (and route names)? I mean no "ui-suite" in the URL.

Discussed with @pdureau, keep "UI libraries".

I kept "Patterns" until UI Patterns will get in the whole codebase change from pattern to component terminology.

Automatically closed - issue fixed for 2 weeks with no activity.