My view is that a technical oriented list such as this is a great start but that what we want in the long run is something which not only lists the extensions available but also how they fit in the ecosystem (e.g. where they are deployed). See a more complete description of this idea here.

We would like to discuss what would be the best place for such list. Official documentation of CSS seems like a good candidate to me personally.

Personally I think it would be better to have this data stored in a separate location. For example, a simple github repository with just a README. This would make it easier to change the list. The CSS documentation could then link to that list, with some added explanation perhaps.

@bourgeoa do you remember where did we land on this topic?
@nikolaswise has created https://www.npmjs.com/package/css-postgres-kv
I will eventually also publish components I'm cooking in https://github.com/hackers4peace/sai-js/tree/main/packages/components

There is also stuff like https://github.com/CommunitySolidServer/shape-validator-component and I bet many more from the solid lab that might not be easy to find unless one knows about them.

Another one https://github.com/RobertGuillaume/passkey-for-community-solid-server via solid/solid-oidc#226 (comment)

awesome-css-components and anything else that uses css presumes that Community Solid Server is the most common expansion of that acronym (or other kind of abbreviation).

That's a poor presumption.

I don't think there's a need to conserve characters in the length of the name of such a list, so why not awesome-extensions-for-CommunitySolidServer?