feat(docs/web-components): custom styling and custom slots

[malikarami]

Is your feature request related to a problem? Please describe.
My problem is that I often forget how I can define custom styles for the web components.
For example for adding ellipsis to the button text (which I know is a crazy example), I should be able to access and define some custom styles for the label of the button.
Or on another example I may need to change the placeholder font-weight or direction on the text-field, in order for which I have to be able to define custom styles (inline or css) for the placeholder of the text-filed.
Hence, I need to go and check the codebase to remember how to do the custom styling thing :)) Which is really troublesome.
Worthy to mention that the same problem applies for defining slots and passing children to the components.

Describe the solution you'd like
It would really be nice if you provided a section in the docs that explained about custom stylings and the whole slot thing. The docs really lacks that in my opinion.

Describe alternatives you've considered
nothing for now.

[malikarami]

I mean, at least providing the component parts can be helpful...

[amir78729]

Thanks a lot for the thoughtful feedback!

You're absolutely right—custom styling and slot usage can sometimes feel repetitive to look up, especially when working across multiple components.

A couple of points that might help in the meantime:

• Each component already includes a Slots section in its documentation. For example, the Button component lists its available slots:

  • default
  • leading-icon
  • trailing-icon

Tip

You can also use the exported ButtonSlots object so you don’t have to memorize slot names manually.

• As for custom styling, we generally expect developers to inspect the rendered component and use the part attributes exposed in the DOM. This allows direct styling via ::part(...), especially for things like placeholder direction or label ellipsis. While we don't currently have plans to document part names centrally, you're more than welcome to contribute to the docs if you'd like to help us build that out!

That said, your suggestion is totally valid—we see the value in adding a centralized "Styling & Slots" guide to cover best practices, especially for advanced use cases like yours. We’ll keep this in mind as we improve the documentation experience. ✨