3 ms·
Funny enough a WYSIWYG editor is the reason Radix components were originally created. I worked on some of the original Radix components while working at Modulz[
by elliotbnvl 3y ago
Funny enough a WYSIWYG editor is the reason Radix components were originally created. I worked on some of the original Radix components while working at Modulz[1].
[1]: https://modulz.app/ https://modulz.app/
- dgellow 3y agoWhat is Radix?
- BoorishBears 3y agohttps://www.radix-ui.com/ https://www.radix-ui.com/ The main offering is their primitives (https://www.radix-ui.com/primitives https://www.radix-ui.com/primitives): essentially skeletons of common components that plain HTML makes difficult to style. They take care of cross-browser compatibility and accessibility and you apply your CSS to their wrapper element. (generally the term for this is headless UI components) Most recently they released a styled version of those primitives
- tobr 3y agoFor React. Not mentioned even on the documentation page unless you dig for quite a bit.
- BoorishBears 3y agoMentioned first thing on the link for primitives.
- deleted 3y ago[deleted]
- apatheticonion 3y agoI feel like there aren't a lot of use cases for custom elements (W3C web components), but a generalised component library like this is probably one of those use cases. Particularly given the ability to style shadow pseudo-elements like drop downs in a non-hacky, browser supported way. Surprised React was chosen here.
- deleted 3y ago[deleted]