Design Systems

252 posts

figmaSep 12, 20212 min readCurated summary

Announcing Schema, Figma’s design systems conference | Figma Blog

Figma announced Schema, a virtual conference dedicated to building, scaling, and contributing to design systems. The event reflects the shift from static, siloed style guides toward collaborative tools, shared visibility, and cross-functional participation. Schema aims to help practitioners exchange practical lessons while recognizing that organizations of every size are still refining their systems. ## The Evolution of Design Systems - Early design-system workflows relied on PDF style guides and developers translating design decisions into code. - These processes were often separated across teams and tools, making collaboration and alignment difficult. - Modern systems emphasize collaboration, visibility, flexible tooling, and shared understanding. - Design systems now involve contributors beyond traditional design roles, including developers and other design-adjacent collaborators. ## Why Figma Created Schema - Design systems include more than libraries, components, and styles. - Successful systems also depend on: - Clear communication - Measurement and demonstrating impact - Community participation - Processes that encourage contribution - Figma wanted to create a space where practitioners could share how they build and manage systems at different organizational scales. ## Event Details and Audience - Schema was scheduled for October 7, 2021, at 8:30 a.m. PT. - The conference was entirely virtual. - It targeted: - Design systems and design operations leaders - Teams formalizing their first design system - Organizations managing systems at scale - Teams extending Figma workflows through APIs, plugins, and custom tooling - Live attendance was limited, with applications accepted through October 4. Talks were also planned for free release in the Figma Community. ## Conference Themes - **Build:** Practical approaches to creating design systems of different sizes. - **Scale:** Strategies for adoption, measuring return on investment, and expanding system capabilities through tools and plugins. - **Contribute:** Methods for developing internal communities and empowering teams to improve the system. Schema was positioned as an opportunity for practitioners to learn from companies both large and small. Its central recommendation is that design systems should be treated as collaborative, evolving products supported by communication, measurement, tooling, and broad participation.

Design Systems Figma Plugins Front End Development+2

figmaAug 24, 20212 min readCurated summary

What’s new in Figma: August 2021 | Figma Blog

Figma’s August 2021 updates focus on faster workflows, more flexible customization, and easier design-system management. The company expanded its plugin ecosystem into FigJam, improved the Figma plugin API, and introduced tools for moving, swapping, and finding components. Smaller usability improvements also addressed common frustrations in both products. ## Plugins and Widgets for FigJam - FigJam gained support for: - **Plugins**, which automate tasks such as organizing sticky notes, customizing styles, and importing data. - **Widgets**, interactive canvas objects for polls, voting, games, notepads, and other collaborative activities. - Plugins are accessible to users on every plan. - Developers can create plugins with basic HTML and JavaScript, while widgets can be built with React. - Widgets were initially offered through a private beta. ## Expanded Figma Plugin API - Plugins can now write to prototypes, enabling developers to: - Automate prototype creation. - Modify interactions in bulk. - Improve prototyping workflows without manual repetition. - **Plugin parameters** let users provide input through quick actions, avoiding the need for custom plugin interfaces. - Plugin parameters were released in open beta, with examples available through Figma’s plugin samples. ## Easier Design-System Maintenance Three component-management improvements make it simpler to scale and reorganize design systems: - **Move components:** Published components and component sets can be moved between files without breaking instance links. - **Swap libraries:** Entire style and component libraries can be replaced at once instead of updated individually. - **Search components:** Pressing **Shift + I** opens a shortcut for quickly locating components. ## Usability Improvements - Transparent objects now automatically knock out shadows behind them, reducing the need for manual adjustments. - Holding **Shift** while using the pencil tool constrains lines to straight paths in both Figma and FigJam. - Additional bug fixes and improvements were documented in Figma’s release notes. Together, these updates make Figma and FigJam more extensible, collaborative, and efficient—particularly for teams managing large design systems or automating repetitive design and prototyping tasks.

Design Systems Figma Figjam React+3

figmaAug 24, 20212 min readCurated summary

FIT’s principles for fostering a collaborative classroom | Figma Blog

Professor Christie Shin of the Fashion Institute of Technology uses Figma to create a virtual classroom centered on systems thinking, frequent feedback, and open collaboration. Her approach treats design as an evolving process rather than a finished object, helping students build habits that mirror professional design teams. She organizes coursework into Figma teams, projects, files, and templates while preserving space for experimentation and individual expression. ## Celebrate Early Work - Students share unfinished ideas regularly instead of waiting for polished presentations. - They visit one another’s files and provide feedback both verbally and directly in Figma. - This reduces the fear of exposing imperfect work and reinforces design as a way of thinking. ## Guide the Process While Leaving Room to Grow - Coursework—from exercises to final presentations—is kept in Figma. - Students receive structured files with named pages and templates for each activity. - The infinite canvas leaves room for sketches, iterations, and exploratory work. - Each file becomes a “creative journey,” documenting research, summaries, wireframes, and development over time. ## Work Individually, Together - Students complete individual projects within study groups. - For a project involving an MTA app design system and video case study, students presented progress incrementally rather than waiting for final critiques. - Continuous peer feedback reflects real-world cross-functional collaboration and helps students become less attached to initial solutions. ## Embrace Influences - Students are encouraged to share work openly instead of hiding ideas to prevent others from copying them. - Shin frames influence as a normal and valuable part of design practice. - Each project requires students to collect and credit visual references from professional designers and classmates. - Discussing these influences during critiques makes the design process more transparent. The article recommends combining clear structure with open collaboration: provide students with organized tools and milestones, but give them room to experiment, share early work, learn from peers, and acknowledge the influences shaping their designs.

Design Systems Figma User Experience Design Wireframing+2

figmaAug 15, 20213 min readCurated summary

Inside Figma: a Q&A with our 2021 interns and new grads | Figma Blog

The article shares career advice from four 2021 Figma interns and new graduates: Emily Jia, Langston Dziko, Daniela Velez, and Jago Pang. Their experiences show that early-career candidates should evaluate company culture, mentorship, ownership, growth opportunities, and alignment with a product’s mission—not just the role itself. Figma attracted them through its collaborative culture, enthusiasm for design, and opportunities to make meaningful contributions. ## Choosing an Early-Career Role - Emily looked for: - Data science roles matching her technical background and goals. - Fast-paced, product-focused work at growing startups. - An empathetic culture centered on communication and connection. - Daniela prioritized authenticity, community, and coworkers who cared deeply about Figma’s mission of making design more accessible. - Langston focused on career growth, asking: - Whether young engineers receive meaningful ownership. - Whether their work contributes to broader company goals. - Whether employees see opportunities to develop and stay long term. ## Using Internships and Conversations to Explore Options - Emily explored different companies through summer and off-cycle internships. - Conversations with alumni and interviewers helped her understand less obvious tradeoffs between roles. - She considered not only people’s day-to-day responsibilities, but also how they had grown in their positions—and whether she wanted a similar trajectory. - Langston used internships to identify the types of work he enjoyed and those he did not. - He also spoke with many engineers, repeatedly hearing that a supportive manager and team can matter as much as the specific project. ## Why They Chose Figma - Emily was influenced by a Figma blog post written by a software engineering new graduate. She valued that Figma gave early-career employees a platform to share their experiences. - She was especially interested in joining a growing data team making its first new-grad hires and deliberately developing its culture. - Langston was impressed by how enthusiastically Figma engineers spoke about the product. Their enthusiasm suggested he would own innovative projects while developing as an engineer. - Daniela first encountered Figma through a collaborative side project. She enjoyed the product’s collaborative design experience and connected with the company’s emphasis on individuality and community. - Jago credited Figma with helping launch his design career and wanted to support its mission of democratizing design, particularly through Figma for Education and the Figma Community team. The interview suggests that students and new graduates should use internships, informational conversations, and employee perspectives to assess both the work and the environment. The strongest early-career choice is likely to be a role offering supportive mentorship, genuine ownership, meaningful growth, and a mission the candidate cares about.

Design Systems Figma Product Design Design Collaboration+2

figmaJul 6, 20213 min readCurated summary

How News UK developed a multi-brand design system | Figma Blog

News UK needed a unified design system for brands spanning print, digital, radio, and television, but its independently operated teams and fragmented tools made scaling difficult. By migrating to Figma, simplifying library management, and investing in education and advocacy, the company created a flexible system that supported brand differences while encouraging collaboration. The transition improved adoption substantially, including a 23-point increase in internal NPS during the first quarter. ## Fragmented Tools and Independent Brands - News UK’s brands, including *The Times* and *The Sun*, historically had separate design organizations, product teams, and workflows. - The team attempted to combine Sketch, Abstract, Zeplin, and InVision, but the result was difficult to maintain. - Design-system updates could take days or weeks, and accommodating brand variations created thousands of styles. - Existing theming features became rigid and overly complex as product requirements expanded. - The launch of *The Times* radio station exposed how much support the design-systems team needed to provide, making the approach unsustainable. - News UK chose Figma to consolidate tools, centralize library management, and increase participation. ## Building Adoption Through Education - The team recognized that successful adoption required cultural change, not just a new tool or library. - Design-system specialists personally configured designers’ Figma workspaces and provided onboarding. - Workshops and documentation covered: - Migrating files from Sketch - Structuring and managing files - Using components - Commenting and inspecting designs - Integrating tools such as Jira - Designers were encouraged to contribute component specifications and reusable patterns. - The team created Figma guidance tools to recommend components for common scenarios, such as onboarding users to a new product. - Designer advocates promoted best practices within product areas and acted as contacts between their teams and the design-systems group. ## Supporting Multiple Brands at Scale - News UK completed its migration to Figma in a few weeks. - Designers shifted from viewing the design system as a burden to seeing it as a productivity aid. - Shared components could be given different brand themes, allowing one system to support distinct visual identities. - A custom Themer plugin helped teams experiment with and build components that worked across multiple brands. - Earlier collaboration and feedback reduced duplicated work and discouraged teams from reinventing existing solutions. - The system was rolled out across all product and design teams. ## Measurable Results - Internal product teams increasingly adopted and contributed to the system. - News UK recorded a 23-point increase in its design-system NPS in the first quarter after introducing Figma. - Teams reported practical benefits while recognizing that the system would continue to evolve. News UK’s experience shows that a scalable multi-brand design system depends on both flexible technology and sustained organizational engagement. Consolidating tools, supporting brand-specific themes, educating users, and appointing internal advocates can turn a centralized system into a shared platform rather than a constraint.

Design Systems Figma Jira Sketch+4

figmaJun 3, 20212 min readCurated summary

Pride 2021: Getting back out there | Figma Blog

Figma’s 2021 Pride post presents Pride as both a celebration of LGBTQ+ identity and a continuation of the community’s history of resistance. Clancy Slack describes how Figma’s Pride Employee Resource Group creates space for authenticity and belonging, especially after the isolation and injustice of 2020. As in-person events began returning, Figma invited the broader design community to express Pride through posters made and shared in Figma Community. ## Figma’s commitment to community and belonging - Figma’s mission of making design accessible extends to building inclusive communities. - Figma Community connects hundreds of thousands of users who collaborate and create together. - Employee Resource Groups help Figmates connect around shared identities and experiences. - The Pride ERG, founded in 2019, provides LGBTQ+ employees with a space to be open, authentic, and supported. - During Maker Week, the group explored Pride iconography and collaboratively designed original artwork. ## Pride’s history and renewed significance - Pride offers LGBTQ+ people a rare opportunity to celebrate openly, feel safe, and connect with their community. - The occasion commemorates the 1969 Stonewall Uprising and the history of resistance to anti-LGBTQ+ discrimination and police raids. - The pandemic and widespread reminders of injustice made community and solidarity especially important in 2020. - With vaccinations increasing and cities preparing for in-person parades, Pride represented a hopeful return to public celebration. ## A call for Pride posters - Figma encouraged designers, artists, and makers to create Pride posters using the platform. - Participants were asked to publish their work to Figma Community with the hashtag **#pride**. - Posters could be printed for local parades or used to celebrate Pride at home. - Figma planned to feature selected designs in a curated Community collection. - The post highlighted employee-created designs, including messages such as “Show your true colors” and “Love is Love.” - A Figma template provided standard sizing and printing guidance. Figma’s central recommendation is to use creative collaboration to strengthen visibility, connection, and LGBTQ+ community celebration—bringing Pride back into public spaces while keeping its history and purpose in view.

Design Systems Figma Collaborative Design Figma Community

figmaMay 31, 20212 min readCurated summary

Embracing the mess at Config 2021 | Figma Blog

Config 2021 emphasized that product development is inherently messy, and setbacks, conflicts, and failures can ultimately improve teams and products. The central recommendation is to treat difficult moments as learning opportunities: step back from failed work, communicate openly, and intentionally preserve what can be learned. ## Learning from Setbacks Shanique Shields of Shopify described discovering that a feature she had worked on for 18 months would be rolled back. Initially, she felt personally responsible, but taking a break helped her recognize the experience’s value. - **Don’t personalize feedback:** Stakeholders may simply have different perspectives or priorities; criticism is not necessarily a judgment of the designer or the work’s quality. - **Document the process:** Preserve design decisions, Figma comments, and personal notes, even when work does not ship. These records help future projects and allow others to learn. - **Be intentional about growth:** Identify the skills, business knowledge, or cross-functional experience gained from each project. - **Start the next project positively:** Use a new workstream as a fresh start and rally the team around a shared goal. ## Addressing Conflict Through Openness Frank Bach of Headspace argued that even strong teams experience communication breakdowns. The best response is to address friction directly rather than allowing problems to grow. - Be transparent about concerns and listen carefully to the other person’s perspective. - Approach difficult conversations candidly and objectively. - Ignoring conflict prevents teams from making progress. - Practice gratitude by recognizing the value of design work, teammates, and collaborative opportunities. The article’s practical message is to embrace the difficult parts of product work. Teams become more resilient when they reflect on failure, communicate courageously, and carry lessons from messy experiences into future projects.

Design Systems Figma Product Development Project Management+2

figmaMay 26, 20212 min readCurated summary

Q&A with Dantley Davis | Figma Blog

Dantley Davis’s Config 2021 Q&A presents design as intentional problem-solving shaped by curiosity, collaboration, and diverse perspectives. He emphasizes using adversity and data to create meaningful impact, while staying humble and avoiding ego-driven design culture. His answers also highlight the importance of cross-disciplinary knowledge, personal creativity, and building inclusive teams. ## Design Philosophy and Creative Practice - Davis describes his creative process as “intentional.” - The best design solves an unrecognized problem so effectively that people cannot imagine life without it. - He defines design as problem-solving through form and function. - His greatest design fear is producing work that receives no reaction. - He dislikes designing primarily for oneself. - He values data as an underused tool for informing design decisions. - His favorite UI font is Montserrat; he prefers Akzidenz-Grotesk for type, hex colors, and specifically `#000000`. ## Collaboration and Team Culture - Good teammates are curious and ego-free. - Teams feel cohesive when members: - Seek feedback because they trust one another. - Inspire each other through their work and perspectives. - Set aside personal ego. - Davis considers building the most diverse team in tech his greatest career accomplishment. - He views mentorship as an important part of his role in the Design Twitter community. ## Leadership and Professional Growth - Davis is skeptical of the emphasis placed on being a “thought leader.” - He encourages young designers to study business, engineering, and finance to become more well-rounded thinkers. - He admires Issa Rae for combining writing, producing, and acting while remaining authentic to her story. - He credits personal time and side projects with helping him do his best creative work. - He regrets that one shipped product remained available too long after it stopped meaningfully benefiting users. ## Design Inspirations and Future Ambitions - Davis would like to design a car interface and would love to shape Porsche’s entire ecosystem, from driving to its app. - He admires designer Clement Mok and would invite him to critique his team’s work. - He praises Roblox for enabling children to play, socialize, and build rather than merely consume content. - He enjoyed Afrotech’s virtual conference, especially its combination of online access and a feeling of presence. - His favorite Figma feature is Observation Mode. Ultimately, Davis advocates for intentional, user-centered design supported by data, interdisciplinary learning, honest feedback, and inclusive collaboration.

Design Systems Figma Web Design User Interface Design+2

figmaMay 24, 20213 min readCurated summary

In the file at Config 2021 | Figma Blog

Config 2021’s breakout sessions emphasized practical systems for building products and teams. Coda’s Helena Jaramillo described how to create a strong product vision without existing user data, while Stripe’s design team shared principles for meeting immediate needs without sacrificing long-term scalability. Both approaches rely on context, shared perspectives, strong foundations, and thoughtful communication. ## Building a Vision from Zero to One - At Coda, Helena Jaramillo worked on a publishing platform designed to help users share best practices and discover documents. - Because the product was new, the team lacked existing user behavior, research participants, and historical data. - Helena built context by studying competitors and adjacent products, annotating screenshots in Figma, and identifying useful or unsuitable patterns. ## Developing a Strong Product Perspective - The team explored what publishing on Coda should feel like: a blog post, a no-code app, or a website. - They used Helena’s publishing experience and internal discussion to form a shared point of view. - Two priorities emerged: - Make publishing interactive documents easy. - Help publishers feel proud of and recognized for their work. - These principles shaped features such as simple publishing flows, photos, subtitles, and bylines. - When user insights are unavailable, a team can rely on collective intuition and expertise—but only by aligning around a clear perspective. ## Communicating the Broader Story - Helena created a “tl;dr page” in Figma to align cross-functional partners. - Rather than documenting every feature, the page used a short flow and several mockups to show the product narrative. - The goal was to make the intended experience understandable without requiring deep project context. ## Designing for Immediate Needs and Long-Term Scale Stripe’s Connie Yang, Tayler Aitken, and their team focus on simplifying complex processes for businesses and end users. Their approach combines urgency with long-term planning. - **Think in long time scales:** Stripe uses a “city planner mentality,” considering how systems connect, handle growth, and respond to future needs—potentially as far ahead as 2030. - **Lay strong foundations:** Teams should invest in fast, accessible products and scalable systems instead of short-term fixes. - Stripe’s design-system color tables, for example, include contrast and accessibility ratings, embedding quality requirements directly into the infrastructure. - **Prioritize rigor and quality:** Because Stripe handles payments and payouts, user trust is essential. The team accepts additional complexity when it produces a more reliable, polished experience. The practical recommendation is to combine strong early judgment with durable systems: build enough context to form a clear vision, communicate that vision simply, and make foundational decisions that continue serving users as the product grows.

Design Systems Figma User Experience Product Design+2

figmaApr 26, 20212 min readCurated summary

Introducing branching: space to iterate and explore freely | Figma Blog

Figma introduced branching in beta to help large design teams experiment without risking changes to shared files. The feature combines the freedom of isolated exploration with Figma’s multiplayer collaboration, while keeping the main file as the approved source of truth. Branches are auto-saved and can later be merged into the main file by editors. ## The challenge of decentralized design systems - Design systems were spread across teams and tools, creating inconsistencies and forcing designers to switch contexts. - Centralized systems improved reuse and efficiency but introduced governance challenges. - In large systems such as Netflix’s Hawkins, many contributors may update files, even when the latest changes are not approved for production. - Teams needed a way to protect shared libraries while still allowing designers to explore new ideas. ## Branching built around simplicity - Figma considered traditional workflows involving commits and nested branches too complex. - The product adopted two principles: simplicity and consistency. - Branches work within Figma’s existing multiplayer model, retaining real-time collaboration. - Work is automatically saved, eliminating the need for explicit commits. - Designers can create a branch from any file, experiment safely, and merge approved updates into the main file. ## Future plans and availability - Figma planned to expand branching with features such as reviews. - The company was also exploring a unified approach to versioning across branching and multiplayer workflows. - The beta initially launched for Organization-plan customers, with access granted gradually. Branching is intended to let organizations centralize their design systems without limiting experimentation. Teams managing shared libraries should use branches for exploratory work and merge only reviewed, approved changes into the main file.

Design Systems Figma Collaboration Version Control+2

figmaApr 20, 20212 min readCurated summary

Coming together at Config 2021 | Figma Blog

Figma’s Config 2021 announcements focus on making design more collaborative and accessible to broader teams. The company introduced tools for brainstorming, safe experimentation, mobile review, live discussion, and large-scale participation. Together, these updates reflect Figma’s shift from a specialized interface-design tool toward a broader collaborative workspace. ## FigJam for Brainstorming - FigJam is a new whiteboard space for brainstorming, diagramming user journeys, and exploring ideas. - It includes features such as emotes and chats to recreate some of the spontaneity of in-person collaboration. - Released in open beta, it was initially free through February 2022, with planned free and paid tiers afterward. ## Branching for Safer Iteration - Branching lets users create independent versions of a file to explore ideas without changing the main design. - Teams can collaborate within branches using Figma’s multiplayer tools. - Completed work can be merged back into the main branch. - The feature is available in beta for Organization-plan customers and is intended to support design-system contributions and large-team workflows. ## Mobile Access and Review - New iOS and Android apps make files and prototypes easier to access from anywhere. - The apps improve the mirrored playback experience, helping designers preview how work appears on actual devices. - The mobile app was launched in beta, with a broader release planned. ## Audio Collaboration - Audio allows teammates to start calls directly inside Figma or FigJam. - It supports live design critiques, group brainstorming, and discussions without leaving the editor. - The feature was planned for Professional and Organization plans. ## Larger Multiplayer Sessions - Figma increased its limit to 500 concurrent users: 100 editors and 400 viewers. - The company planned to raise the limit to 1,000 users across Figma and FigJam, with 200 editors and 800 viewers. - These limits support large presentations, workshops, classrooms, and other emerging collaborative uses. ## Publishing to the Figma Community - Everyone can publish files, templates, techniques, and other resources to the Figma Community. - Users can both discover work from others and share their own contributions. - FigJam templates were highlighted as an early example of this expanded community ecosystem. Figma’s Config 2021 updates recommend a broader model of design collaboration: teams can ideate in FigJam, experiment through branching, review work on mobile, communicate through audio, and share results with the wider community.

Design Systems Figma Figjam Collaborative Design+3

figmaApr 6, 20212 min readCurated summary

How Repsol rethinks the way the world interacts with energy | Figma Blog

Repsol is using design to make energy more understandable and encourage consumers to participate in the transition toward sustainable energy. After creating its first internal design team, the company partnered with Mendesaltaren to build the Oxygen design system in Figma. The system unified design across products, improved collaboration, and reduced product implementation work by 30%. ## Making Energy More Tangible - Repsol’s design team aims to “humanize” energy and help people become active participants in how it is produced and consumed. - An electric car-sharing app shows users how much energy they consume while driving and rates their efficiency. - Another app feature lets users see where their electricity comes from, including nearby solar panels and wind turbines, alongside current weather conditions. - These experiences turn energy from an abstract bill into something visual and interactive. ## Building One Design Language - Repsol serves diverse audiences, including drivers, industrial customers, employees, and teams managing refineries and supply chains. - Before the design system, different products taught users different interaction patterns and languages. - The Oxygen design system provides shared patterns, components, interaction guidelines, and developer guidance. - Built in Figma, it creates consistency across products while allowing teams to adapt designs to different purposes and audiences. ## Figma as the Collaboration Hub - Figma became the central workspace for design, communication, feedback, and executive presentations. - Repsol can work simultaneously on more than 15 projects across internal and external teams while maintaining consistency. - Designers replaced tools such as Sketch, InVision, and PowerPoint. - Product owners, technology leads, and executives can review and iterate on designs in parallel. ## Measuring Design’s Impact - Mendesaltaren developed two plugins to help Repsol measure design performance: - **Figmetrics** tracks how components are used across Figma files. - **MSVM** keeps design, product, business, and technology teams aligned around a shared source of truth. - The new system and processes reduced implementation work by 30%. - Repsol can now track savings in time, money, and effort, making design’s business value more visible. Repsol’s experience shows how a centralized design system can improve efficiency while making complex subjects more accessible. By connecting consistent design practices with measurable results, the company is using design as a tool for both digital transformation and its transition toward net-zero energy.

Design Systems Figma User Experience Product Development+3

figmaMar 29, 20212 min readCurated summary

Behind the scenes of creating the official Figma kit for Tailwind UI | Figma Blog

Tailwind Labs created an official Figma kit to meet strong customer demand for Tailwind UI designs. Building it required translating more than 400 responsive code components into over 1,400 Figma components and 10,000 elements, with the final code serving as the pixel-perfect reference. The project showed that a production design kit needs rigorous structure, naming, responsive modeling, and reusable variants—not just visual accuracy. ## Building a Design File as a Product - Unlike exploratory product files, a commercial design kit is itself the final deliverable. - Every decision affects usability, including: - Layer names - Component structure - Page organization - Variant behavior - The team used the finished HTML and Tailwind CSS components as the standard the Figma files needed to match. ## Consistent Layer Naming - Consistent names allow Figma overrides to persist when users swap component instances or variants. - For example, a button’s text layer was always named “Text,” allowing customized text to carry over when changing button sizes. - This becomes especially valuable in complex components containing icons, headings, paragraphs, and links. ## Mirroring HTML Structure in Figma - Auto Layout, layout grids, and constraints let Figma layers approximate HTML structure and browser layout behavior. - Matching design and code architecture helps designers and developers share an understanding of what layouts can support. - It also exposes recurring implementation patterns, such as responsive padding and centered max-width containers, which developers can turn into reusable layout utilities. ## Using Variants to Simplify Components - Instead of maintaining dozens of separate components, the team combined options into configurable variants. - A single Badge component could cover type, size, theme, and optional secondary elements. - Variant properties were named consistently with code component properties, using terms such as: - Type - Size - Theme - Position - Breakpoint - State - Variants made components more discoverable and reduced duplication. - The completed kit contained 1,430 components averaging seven variants each; without variants, it would have exceeded 10,000 components. ## Scale and Quality Control - Over several months, the team built and rebuilt more than 1,400 components and 10,000 distinct elements. - The project emphasized detailed auditing and pixel-level consistency, although the provided article excerpt ends before describing that process. The main recommendation is to treat a shared Figma kit like a carefully engineered product: align it closely with the codebase, establish naming and structural conventions early, and use variants to keep a large responsive system manageable.

Design Systems Figma CSS HTML+3

figmaDec 15, 20202 min readCurated summary

Redesigning Dropbox’s ways of working | Figma Blog

Dropbox’s shift to a virtual-first model required more than moving meetings online; it meant redesigning how teams collaborate and maintain creative energy. Having already adopted Figma, the design team expanded its use from design production to brainstorming, reviews, handoffs, and cross-functional communication. Figma ultimately became a shared visual workspace for teams across Dropbox, helping recreate some of the spontaneity and connection of the physical office. ## The Challenge of Virtual-First Work - Dropbox’s culture and workspaces had been designed around in-person collaboration across twelve global offices. - Design teams relied on physical workshops, post-its, whiteboards, and informal interactions to generate ideas. - Remote work made creative flow and team connection less automatic, requiring more intentional collaboration practices. ## Redesigning Collaboration with Figma - Dropbox’s design organization had migrated from Sketch to Figma in 2018 and already used it for: - Brainstorming - Wireframing - Prototyping - Commenting - During the pandemic, designers increased their reliance on Figma to reduce communication gaps. - Observation mode replaced some in-person design reviews, allowing participants to follow a presenter’s work directly. - Designers shared files for rapid iteration instead of pairing at a desk or brainstorming in a physical room. - Design sprints brought engineers and product managers directly into Figma, making participation easier for non-designers. - Teams also created asynchronous workflows, such as using checkmarks in an icon template to signal that assets were ready for inclusion in the master library. - These file-based processes reduced unnecessary communication and improved the efficiency of recurring library releases. ## Expanding Figma Across Dropbox - The design team became an example of how remote collaboration could work for the broader organization. - Cheechee Lin led workshops teaching cross-functional teams how to navigate Figma and use features such as commenting, exporting, viewing, and following. - More than 200 people from marketing, research, data science, and other teams attended the workshops. - Figma provided a shared visual space that compensated for the lack of physical whiteboards. - Teams beyond design began using Figma for test plans, research presentations, survey data, qualitative insights, and collaborative presentations. Dropbox’s experience suggests that successful virtual-first work depends on deliberately rebuilding collaborative habits, not simply adopting video calls. Making a shared, accessible workspace central to communication can help distributed teams preserve creativity, speed, and cross-functional involvement.

Design Systems Figma Prototyping Remote Collaboration+2

figmaNov 18, 20202 min readCurated summary

Behind the feature: the making of the new Auto Layout | Figma Blog

Figma’s new Auto Layout evolved from a long-standing idea into a more flexible system for creating responsive designs. The team sought to combine flexbox-inspired power with an approachable interface, defining Auto Layout as “a thoughtful subset of flexbox.” The result was a feature designed to reduce manual resizing while preserving usability for designers who may not know CSS deeply. ## The Need for Automatic Resizing - Before Auto Layout, designers had to manually resize buttons, reposition neighboring elements, and adjust containers whenever content changed. - This repetitive work made responsive design systems difficult to build and maintain. - Figma had considered automatic layout since its early designs, but the concept remained unimplemented until Maker Week in 2018. - During Maker Week, product director Sho reimagined the feature in prototypes, eventually leading to a dedicated team focused on making Auto Layout real. ## Designing a Thoughtful Subset of Flexbox - The team drew inspiration from CSS flexbox because it could help align design workflows with implementation in code. - They intentionally avoided reproducing all of flexbox’s complexity. - Their guiding principle was to create “a thoughtful subset of flexbox” that remained easy to learn and use. - Core capabilities included: - Enabling vertical or horizontal layout on a frame. - Setting spacing between items. - Automatically sizing frames to hug their contents along the main axis. - Allowing fixed or content-based sizing on the counter axis. - Giving individual components independent alignment within their container. ## Prototyping and Team Alignment - The designer, Marcin, built an early prototype entirely in HTML. - The prototype helped the team experience the feature early and resolve interaction details before implementation. - It informed decisions about frame-handle decoration, dragging behavior, and visual outlines. - This shared prototype helped product, design, and engineering align around both the feature’s behavior and its usability. Figma’s approach shows that a successful layout tool does not need to duplicate the full complexity of web technologies. By selecting the most useful flexbox concepts and presenting them through an intuitive editor, Auto Layout made responsive design more practical while keeping the experience accessible.

Design Systems Figma CSS HTML+3