Open office hours - Nov 2ndNovember 2, 2018 at 6:27pm
Chat with us about building a React component library, working with Figma, and building design systems at GitHub! 2-3pm PT
November 2, 2018 at 9:20pm
We're sort of soft launching them this week so not making a big public announcement, but feel free to dig around and shoot us any feedback if you have any! :)
We'd love feedback around: whether or not the props API feels intuitive/easy to learn or any accessibility feedback!
Hey Emily and Diana, one q, out of curiosity and firsthand struggles atm. From your docs,
This project uses emotion under the hood to generate static CSS from some component styles, but still relies on Primer CSS for some component styles that haven't yet been ported over.: will Primer live in two eco-systems (CSS/SASS-land and another version in CSS-in-JS via Emotion)), or eventually all live in Emotion? This is something I've been thinking about a lot, specifically how to best and sustainably rollout and maintain a design system without maintaining two or more sources. I'm still reading through things... love the principles
Our long-term goal is ideally to move entirely to emotion, and also to generate a CSS only version of primer from the react component library. We'll likely be maintaining both versions for a while which creates some overhead, but feels manageable for the time being. Starting off with using the classnames package with our existing primer CSS meant that we could begin developing the public API without the blocker of re-coding all the styles for every component.
As an aside, though currently we're using emotion.js, it's possible we'll swap it out for another solution like styled-components which has pretty much the same API. Our focus to start with was to get the public api right and then focus on making the private api better to work with for contributors.