Summary

Folder icon bug

Expected behavior

Display the arrows icons properly when setting
material_theme_arrow_folders is true

Actual behavior

Steps to reproduce

Just change the setting material_theme_arrow_folders,
Please check the full config bellow
...
"

The "Who to follow" page seems a little unruly. I think it might be better to change it to a Twitter list maintained by the A11y Project Twitter account or separate Twitter lists for people, companies, and Meetups.

This would have the added benefit of allowing users to follow/unfollow the whole list at

All plugins are currently documented well via the CLI help, maybe start by copying that output, later on refine the readme files

Why is Padding behavior creating a fix width + fix height on the group?

This is kind of stupid. Wanting a padded symbol doesn't mean we want it fixed size.
Or am I missing something? I'm having a headache using this feature.

Following up on the analysis done in #798, we should update related full page demos to eliminate use of card backgrounds. Demos affected include:

Data List
Table
Forms
Master-detail

From @veronicageek:

Looking at the M365 Community Docs, I was wondering if maybe, we could put the articles in alphabetical order or something inside of their group (Basics, IA, etc…)?
I think it would be easier… Knowing that when you’re on that page and you search, it’s actually not scoped to the Community Docs 😕

Is your request related to a problem? Please describe.
The "why" behind some of these guidelines is not clear — which can lead to some of the critical ones not being followed.

Describe the solution you'd like
Audit the Figma page and add clarity to the requirements.

Currently you have to go into the filter panel to tell which filters are active (use "Show filters" button). It would be helpful to have the active filters visible outside of the panel (just as text) so the user is aware how the content is being filtered. This becomes even more useful when filter persistence between pages and session is added since the user may not remember which filters are enabl

What's your idea?

When using multi: true, (de-)serializers only operated on the inner value, not the entire array, which in general is fine. We also support emptyOn on such parameters, and we also recommend in the docs that emptyOn can be further customized by instead using (de-)serializers since the former is just a convenience wrapper around the second.

**Describe the solution yo