đź“ť Articles
Securing Buy-In for Your Design System: A Lifecycle Approach
Nezar explains that implementing a design system involves securing stakeholder buy-in, engaging teams during development, and promoting and iterating on the system post-launch to maximise its benefits. This approach ensures successful adoption, fosters collaboration, and enhances efficiency and innovation in product development.
Accessibility in Design Systems: A Comprehensive Approach Through Documentation and Assets
Cintia highlights the importance of embedding accessibility in design systems, using comprehensive documentation and assets to support inclusive design at Pinterest. By integrating accessibility guidance into their Gestalt design system, they ensure designers and cross-functional teams can create accessible, user-friendly products, while also fostering a culture of continuous learning and improvement in accessibility practices.
Typography Variables in Figma Are Here | by Joey Banks | Apr, 2024 | Medium
Joey explains that Figma's latest updates, including typography variables and the ability to use variables within gradients, significantly enhance design consistency and efficiency. Additionally, they highlight the introduction of Code Connect, which promises to bridge the gap between design and code by allowing developers to view and use actual design system code directly in Figma, fostering better collaboration and smoother design handoffs.
Optimising the design system with Figma's variables
Nana discusses how to optimise design systems using Figma’s variables by establishing both primitive and semantic variables to ensure consistency, scalability, and maintainability. She highlights practical steps for creating and naming variables, and emphasises the collaborative nature of design systems, integrating feedback and insights from engineers and project managers.
đź‘€ Interesting Reads
A “single source of truth”—and other Design System lies
Kevin argues that the concept of a “single source of truth” in design systems is misleading, suggesting instead that truth is a shared responsibility involving both designers and developers. He highlights the challenges of collaboration, asserting that while truth should ideally stem from design, the practical implementation often involves multiple sources and perspectives, making the notion of a singular truth impractical.
Design systems and the never-ending job of buy in
PJ discusses the ongoing challenge of securing buy-in for design systems, emphasizing that skepticism and the need for constant selling are integral to their success. They advise that achieving buy-in is a gradual process that requires aligning with company priorities, demonstrating tangible benefits, and maintaining strong communication and visibility.
How to generate colour palettes for design systems
Matthew discusses the complexities of generating colour palettes for design systems in modern software, highlighting the need for accessibility, adaptability, and consistency. They introduce a tool they have developed that uses the OKHsl colour space to create flexible, scalable, and accessible colour systems, addressing the limitations of existing tools.
🧰 Tools / Resources
The Right Code for Your Design System
Emil highlights the importance of bridging the gap between design and code for effective collaboration and announces Code Connect, a tool designed to improve design system adoption. Code Connect allows developers to access approved code directly within their workflows, ensuring consistency and efficiency, ultimately fostering better alignment between design and development teams.