@nathanacurtis@_carbondesign I also think an investment in feature flags helped to reduce the pressure to do major releases as often. With flags, teams could adopt features sooner than the next major and also could make dual maintenance easier (although @Tay1orJones would know way more about this👀)
@nathanacurtis@_carbondesign (Not on the team anymore) but so much of this is due to the cost of migrating between major versions. There are just so many teams and products that migration is a multi-year endeavor. It created a need to offer LTS versions along with a train release model for predictable dates
I'm thrilled to share my latest blog post on the GitHub Blog: "Exploring the challenges in creating an accessible sortable list (drag-and-drop)."
https://t.co/p5DJLfd08o
#Accessibility#WebDevelopment
https://t.co/ZZcJ8VviUc
All code has been letters, on a grid, since the days of the teletype machine. How can we advance the state of the art to make code itself more expressive and powerful? How can we layer more meaning onto code?
@danciupuliga@chase_mccoy@colebemis This info is then mapped to models we have defined over in Prisma and the data is ultimately stored in a sqlite file at the moment 😂 This data is then used by a Next.js app to build a static site that is deployed with the latest data. (3/3)
@danciupuliga@chase_mccoy@colebemis The collection process finds the relevant files in each repo (JS, TS, styles, etc) and parses them to get the AST for each file and the overall dependency graph. We can use both the ASTs and graph to find information about components, styles, etc that we're interested in. (2/3)
We're hiring over at Primer! 🥳 Come work with us on our design system, building out components with accessibility and inclusive design at the core of everything we do.
US: https://t.co/fCs2I4NRI9
Canada: https://t.co/OC22CKA1nb
UK: https://t.co/gHLrv6H0fM
@chase_mccoy@colebemis Thanks for the kind words! 🙏 Let me know if you have any questions or want to talk about this more 👀 It was a lot of fun to put together and I always love learning more about this space.
@githubdesign@githubprimer It was so much fun putting this together and I’m so glad that we can share it 😄 Happy to answer any questions and always open to learn more if you’re tackling a similar problem for your design system!
@githubdesign This talk was a part of our “Building GitHub using GitHub” series and it covers part of how we look at component usage for @githubprimer all across GitHub.
The GitHub Design team is hosting our first ever *internal* Design Conference on June 13-15. We're calling it LGTM 👍. This virtual event is focused on celebrating the creativity, innovation, and collaboration shaping the future of GitHub.
@Tay1orJones@nathanacurtis Jan's work here is so cool! I love how this work manifested in the PR, especially around the helpers for developers to use to participate in the layout system as a whole. This plus the density model to participate in the grid is so awesome to see 🔥
Today, we're excited to launch @github code search - a new way to search and navigate code.
We’re introducing a brand new search and code navigation view and they are jam packed with new features. Here are some I’m excited about.... 🧵 1/6
@_alanbsmith Would love to hear your thoughts if you end up putting a post together or share them through a more appropriate avenue! Currently getting used to the CSS-in-JS side of things after being on the Sass side of the house for a while.