What's this all about?
The goal of the Call Kent Podcast is to get my answers to your questions. You record your brief question (120 seconds or less) right from your browser. Then I listen to it later and give my response, and through the magic of technology (ffmpeg), our question and answer are stitched together and published to the podcast feed.
If recording isn't an option, you can also type your question and we'll generate the audio for you.
I look forward to hearing from you!

A caller wants to expose internal styles from their component library to consumers. Kent suggests using a variable to export the class names and using a library like CVA to create multiple variants of a set of class names. He also recommends against using disabled buttons as a workaround and instead suggests creating individual components for each use case.
Exposing internal styles from design system
A caller wants to expose internal styles from their component library to consumers. Kent suggests using a variable to export the class names and using a library like CVA to create multiple variants of a set of class names. He also recommends against using disabled buttons as a workaround and instead suggests creating individual components for each use case.
Exposing internal styles from design system
A caller wants to expose internal styles from their component library to consumers. Kent suggests using a variable to export the class names and using a library like CVA to create multiple variants of a set of class names. He also recommends against using disabled buttons as a workaround and instead suggests creating individual components for each use case.
Exposing internal styles from design system
A caller wants to expose internal styles from their component library to consumers. Kent suggests using a variable to export the class names and using a library like CVA to create multiple variants of a set of class names. He also recommends against using disabled buttons as a workaround and instead suggests creating individual components for each use case.
Exposing internal styles from design system
A caller wants to expose internal styles from their component library to consumers. Kent suggests using a variable to export the class names and using a library like CVA to create multiple variants of a set of class names. He also recommends against using disabled buttons as a workaround and instead suggests creating individual components for each use case.
Exposing internal styles from design systemHave a look at these articles.