Building non provided components #1141
Replies: 1 comment
-
Hey @imjakechapman, appreciate the kind words - glad you're excited about using Evergreen for an upcoming project! To answer your question(s), it might be worth talking a bit about some of the underlying architecture first.
For keyboard accessibility - it very much depends on what you're looking to build. Evergreen has some of the recommendations from WCAG 2.1 implemented for things like Dialog, Popover, Button, etc. But, if you're looking to build something that's not in Evergreen, we unfortunately don't provide composable keyboard primitives to help ease the process (although, would be happy to accept PRs that introduce it into the lib!) Hope that answers your question(s)! |
Beta Was this translation helpful? Give feedback.
-
Just found Evergreen and first I have to say Segment team nailed the visual design of the library.
I'm trying to find examples of how to properly build out components that aren't provided by the library itself. I understand using
<Pane>
and<Card>
is the way to go, but what is the best approach to take for styling those? css-in-js? css-modules? How do we maintain the consistency of things like theme palette when creating our own components? Maybe I missed something that the library provides:root
css vars to use within our css. Also what are your approaches to accessibility for keyboard navigation when building components that aren't provided in the library at Segment?Looking forward to trying this out once I get past this first hurdle.
Beta Was this translation helpful? Give feedback.
All reactions