techlist.io
KREN

Techlist.io - Korean Tech Blog Curator

figma3 min readCurated summary

Inside Maker Week: more than a hackathon | Figma Blog

Maker Week is Figma’s twice-yearly, company-wide alternative to a traditional hackathon. It gives employees across disciplines, teams, and time zones dedicated time to pursue creative projects without requiring technical expertise. The program has produced hundreds of ideas since 2018, many of which became product features, community tools, or cultural initiatives. ## A Maker Culture Open to Everyone - Figma defines “maker” broadly—not just as an artist, engineer, or craftsperson, but as anyone expressing creativity in an authentic way. - The company reinforces this culture during weekly All Hands meetings, where new employees explain how they are makers. - This inclusive definition allows people who see themselves as curators, organizers, educators, or collaborators to participate. ## Maker Week as a Cross-Functional Festival - Maker Week happens twice a year and pauses normal day-to-day work for a week of experimentation and connection. - Unlike many hackathons, which can favor engineering, product, and design teams, Maker Week invites employees from every function. - Projects have included: - Recruiter-created employee baseball cards for candidates. - An intern-built “Name That Figmate” game. - A chemistry lesson taught through baking by data scientists. - The format encourages cross-pollination, shared ownership, and a better understanding of how different teams contribute to Figma. ## From Experiments to Shipped Work - Figma has held five Maker Weeks since 2018, generating hundreds of projects. - Some projects have become externally released products or features, including: - Auto Layout. - Interactive components. - Figma plugins. - The company suggests that FigJam itself may represent the culmination of multiple Maker Week experiments. - Other projects, such as *Figma in Quarantine: The Musical*, have offered glimpses into Figma’s internal culture. ## Featured Maker Week Projects ### Empathy-Building Cards - Research, sales enablement, and brand design employees created cards combining user personas with different characteristics and situations. - The cards help Figmates better understand users’ perspectives and contextualize the challenges they face. - The project was shared with the broader Figma community. ### Figma in 3D - An engineer and product support employee collaborated to create an extension that projects layers off the canvas. - Users can orbit around the design with a mouse, making Figma feel more like a 3D mapping application. - The project explored new possibilities for spatial software. ### User Collaboration Data Visualization - A data scientist and enterprise sales employee built a Mode-based map showing collaboration between users in different countries within the same domain. - The visualization helps organizations understand how teams collaborate across regions and time zones. Maker Week demonstrates that innovation does not have to come only from formal product teams. Figma’s approach recommends creating structured time for broad participation, experimentation, and cross-functional collaboration—while allowing the most promising ideas to evolve into real products or cultural initiatives.

Read original(opens in new tab)
FigmaFigjamFigma PluginsData Visualization+1
figma2 min readCurated summary

Shifting team culture at Config 2021 | Figma Blog

The Config 2021 sessions argued that inclusive, collaborative design depends on building cultures of transparency, trust, and shared participation. Speakers emphasized two complementary practices: acknowledging people’s real emotions and circumstances, and creating accessible spaces where newcomers and diverse perspectives can contribute. The overall conclusion was that teams cannot create inclusive experiences alone; they need intentional routines, open resources, and community support. ## Embracing Vulnerability - Figma researcher Nannearl Brown described how openness about personal struggles can create a more supportive team culture. - Team members were encouraged to share: - How they were feeling - What support they needed - What they were focusing on during the day - Daily Slack stand-ups included non-work activities—such as exercise, hobbies, or family time—to encourage work-life balance and help teammates understand one another. - Support requires more than listening; teammates should make room for each other’s emotions, experiences, and difficult moments. - The central message was that people do not need to appear fine all the time. ## Creating Inclusive Spaces - Bitcoin designers Johns Beharry and Christoph Ono noticed that Bitcoin design resources often excluded people without technical expertise or geographic access. - They responded by building shared spaces where experienced designers could support newcomers, including: - A Slack community - GitHub resources - The Bitcoin Design resource hub - Weekly community calls - The open-source Bitcoin Design Guide - The resources were designed to work across cultures, regions, languages, and levels of technical knowledge. - Their goal was to create a friendly environment that encouraged broader participation and more diverse perspectives. - They argued that inclusive and accessible design requires collaboration with people who bring different experiences. ## Building Collaborative Culture - Design is inherently collaborative and benefits from varied experiences and perspectives. - Inclusive culture helps more team members and collaborators participate in the design process. - Trust and transparency are developed through both interpersonal habits—such as honest check-ins—and structural tools that make knowledge widely accessible. Teams seeking a more inclusive culture should normalize vulnerability, establish supportive communication routines, and create shared resources that invite participation from people with different backgrounds and levels of expertise.

Read original(opens in new tab)
FigmaOpen SourceGithubSlack+2
figma3 min readCurated summary

Q&A with Robyn Kanner | Figma Blog

Robyn Kanner’s Config 2021 interview presents design as an active, collaborative practice rather than a fixed professional identity. Alongside her work as Creative Director for the Biden-Harris campaign, her answers emphasize persistence, teamwork, cultural awareness, and making things without being constrained by titles or tools. Her central advice is to stay present, keep creating, and define success through meaningful impact. ## Designing the Biden-Harris Campaign - Kanner led the Biden-Harris design team during the 2020 U.S. presidential election. - The team created a wide range of campaign materials, from JoeBiden.com to the campaign plane, working together in one Figma file. - She identifies helping elect Joe Biden as the greatest accomplishment of her career. - Her Config 2021 keynote provides a deeper account of the campaign and its creative process. ## A Relentless and Unrestricted Creative Practice - Kanner describes her creative process as “relentless.” - She does her best work early in the morning and late at night. - She rejects the idea of perfect design, saying there is “nothing perfect.” - Her advice to young designers is not to limit themselves to a job title—or even think of themselves primarily as designers—but simply to make things and let the rest develop naturally. - Her definition of design is immediate and action-oriented: “‘NOW.’” ## Collaboration and Team Culture - Good collaborators create space for the people around them. - Teams become genuine teams by “going through shit together.” - Kanner’s answers suggest that shared pressure, trust, and mutual support matter more than formal processes. - When asked whom she would want in a design critique, she chooses Michael Jordan, reflecting an interest in high-performance perspectives beyond design. ## Influences, Tastes, and Perspective - Her favorite UI typefaces are Decimal and Mercury, and she values type, color, and multiple color systems equally. - She admires her parents for shaping who she is. - She considers sociology underrated and code overrated within the design world. - Outside design, she highlights Jeff Buckley, BROCKHAMPTON’s “BUZZCUT,” and the video game Madden as sources of enjoyment and decompression. - She dismisses comparisons with other designers, emphasizing that everyone has their own path. ## Tools, Constraints, and Figma - Kanner dislikes being limited by tools, particularly Safari’s handling of animations. - She praises Figma as having “revolutionized creating.” - Her favorite Figma feature is Shift+H, though she jokingly says she likes all of them. - Her ambition to “put gradients on Mars” captures her playful, expansive approach to design. The interview ultimately recommends a broad and practical view of creativity: make meaningful work, support the people around you, resist restrictive labels, and focus on the present rather than chasing perfection or comparison.

Read original(opens in new tab)
FigmaUser InterfaceDesign CollaborationTypography+4
datadog2 min readCurated summary

How Datadog's IT team automated monitoring third-party accounts | Datadog

The provided text does not contain the tech blog post itself. It consists primarily of Datadog’s navigation menu and a promotional banner announcing its “Leader” ranking in the 2026 Gartner Magic Quadrant for Observability Platforms, so the article’s argument and conclusion cannot be reliably summarized. ## Promotional Announcement - Datadog links to a Gartner report about observability platforms. - The banner presents Datadog as a Leader in the report. ## Datadog Product Categories - **Infrastructure:** infrastructure, container, network, serverless, GPU, storage, and cloud-cost monitoring. - **Applications:** APM, service monitoring, profiling, dynamic instrumentation, and agent observability. - **Data and Logs:** database monitoring, data quality, job monitoring, log management, sensitive-data scanning, and observability pipelines. - **Security:** code, cloud, vulnerability, compliance, SIEM, workload, and application protection. - **Digital Experience:** browser and mobile RUM, session replay, synthetic monitoring, product analytics, and error tracking. - **Software Delivery:** CI visibility, test optimization, code coverage, feature flags, and developer portals. - **Service Management:** event management, incident response, SLOs, workflow automation, and case management. - **AI:** AI agents, GPU monitoring, integrations, investigation tools, and MCP support. The actual blog content—apparently related to how Datadog’s IT team automated monitoring of third-party accounts—is missing. A summary would require the article body or a complete excerpt.

Read original(opens in new tab)
KubernetesDatadogObservabilityApplication Performance Monitoring+4
datadog2 min readCurated summary

How Datadog's IT team automated monitoring third-party accounts

Datadog built “Clarity,” an automated system for auditing SaaS accounts against Workday’s employee records. It regularly identifies accounts that do not belong to active employees, then logs, tickets, stores, and communicates findings through Datadog, Freshservice, Slack, and DynamoDB. The system replaces infrequent, manual reviews with continuous visibility and faster remediation of security and cost risks. ## The Need for Automated SaaS Audits - Modern companies rely on dozens or hundreds of external applications. - Manual account reviews are difficult to scale and may fail to detect unauthorized or abandoned accounts promptly. - An unexpected account in an identity provider or SaaS application could give a bad actor access to sensitive systems. - Datadog needed recurring audits as its SaaS portfolio continued to expand. ## Clarity’s Requirements - Use a single source of truth for employee status: - Datadog uses Workday. - Other organizations could use Okta, OneLogin, ADP, or Active Directory. - Run frequently enough to provide timely visibility. - Support manual execution when needed. - Integrate with existing communication, ticketing, and observability tools, such as Slack, Freshservice, and Datadog. - Minimize disruption to IT workflows and encourage adoption across a globally distributed organization. ## Audit Pipeline - A CloudWatch Event Rule triggers the audit Monday through Friday at 10 a.m. EST. - Clarity concurrently retrieves: - Active employees from Workday. - Active users from primary SaaS applications such as Slack, GitHub, and Zoom. - It compares SaaS user email addresses with active employee records. - Accounts without a matching active employee are flagged. - Results are: - Sent to Datadog as logs and metrics. - Added to DynamoDB for historical tracking. - Converted into Freshservice tickets. - Reported through Slack notifications with an audit summary. ## Datadog Metrics and Investigation - Clarity sends a metric for every flagged account using the Datadog Metrics API and Python SDK. - It uses a gauge metric to track flagged accounts over time. - Metrics include tags such as: - Environment, such as production. - Responsible team. - SaaS service. - Flagged user’s email address. - These tags provide the context needed to investigate the account and support alerting and visualization within Datadog. ## Practical Outcome Clarity provides a repeatable, automated control for SaaS account governance. Organizations implementing a similar system should connect an authoritative employee directory to their SaaS inventory, run audits regularly, and integrate findings with their existing monitoring, ticketing, and notification workflows.

Read original(opens in new tab)
Database DesignDatadogSlackAws Lambda+4
figma2 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.

Read original(opens in new tab)
FigmaDesign SystemsCollaborationVersion Control+2
figma2 min readCurated summary

Introducing FigJam | Figma Blog

FigJam is Figma’s online whiteboard for collaborative brainstorming and early-stage design. Figma argues that remote work and the shift toward cross-functional collaboration have created a need for more informal, shared online spaces—not just tools for producing finished designs. FigJam addresses this with a lightweight, approachable environment that connects directly to Figma. ## Why Figma Built FigJam - Remote work has reduced in-person collaboration and increased reliance on online tools. - People were already using Figma for activities beyond interface design, including games, icebreakers, meal planning, and brainstorming. - These uses showed that teams wanted a place to share ideas and connect without necessarily designing products. - Figma concluded that these interactions needed a dedicated space where non-designers felt welcome while designers still felt at home. - The product also supports Figma’s broader goal of making design accessible to everyone by involving more people earlier in the design process. ## FigJam’s Role in Early-Stage Design - FigJam is described as a lightweight, easier-to-learn version of Figma for ideation and brainstorming. - Teams can use it to: - Define user problems - Gather inspiration - Explore product ideas - Map user flows - Build and document processes - Multiplayer tools include sticky notes, emojis, drawing tools, stamps, and cursor-based chats. - Shapes, lines, and connectors make diagramming and systems thinking easier. ## Collaboration and Connection - Built-in audio lets teams discuss ideas without switching to a phone or video call. - FigJam integrates seamlessly with Figma, allowing work to move from initial concepts through final prototypes in one ecosystem. - Expressive features such as emojis, stamps, and cursor chats are intended to make collaboration feel warmer, more spontaneous, and more enjoyable. - The product is designed to combine practical functionality with the informal energy of “hanging out” together online. ## Early Users and Pricing - Teams at Stripe, Netflix, Salesforce, Twitch, and Discord tested FigJam during its development. - Discord’s design leadership praised it as a focused, uncomplicated version of Figma suitable for brainstorms, retrospectives, and similar activities. - FigJam was free for everyone through the end of 2021. - Planned 2022 pricing included free and paid plans costing $3 and $5 per editor per month. FigJam’s central promise is to give distributed teams an inviting, collaborative space where product ideas can emerge before formal design work begins.

Read original(opens in new tab)
FigmaFigjamCollaborationDesign Thinking+3
figma2 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.

Read original(opens in new tab)
FigmaDesign SystemsFigjamCollaborative Design+3
figma2 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.

Read original(opens in new tab)
FigmaDesign SystemsUser ExperienceProduct Development+3
figma2 min readCurated summary

About Figma’s new Starter plan | Figma Blog

Figma’s updated free Starter plan, launched April 21, 2021, prioritizes unrestricted multiplayer collaboration over unlimited shared files. Drafts remain an unlimited personal workspace, while team spaces gain unlimited editors but are limited to three files with three pages each. Figma concluded that removing the arbitrary two-editor cap would better let teams experience real-time collaboration. ## Changes to the Starter Plan - Drafts become a personal workspace: - Unlimited files, pages, and viewers remain available. - Co-editing requires moving a file into a team space. - Team spaces now support: - Unlimited editors. - A maximum of three files. - Up to three pages per file. - Existing files, pages, and projects created before the rollout were not moved or altered. - FigJam was also introduced to all plans with unlimited usage during its beta period. ## Why Figma Removed the Editor Limit - Collaboration is central to Figma’s browser-based product and often the main reason teams choose it. - The previous two-editor limit prevented users from experiencing the full benefits of multiplayer design. - Figma considered simply increasing the editor limit but decided any fixed number would be arbitrary. - The new approach supports teams ranging from two collaborators to dozens of teammates. ## Results from User Testing - 87% of users were excited about unlimited editors in team spaces. - Teams collaborated 29% more after the two-editor restriction was removed. - Users typically worked actively on only two or three files at a time, making the new team-space limits seem reasonable. - Unlimited files remained available in Drafts for personal work. ## Rollout and Additional Options - Figma announced the changes ahead of the April 21, 2021 rollout. - Users received notifications through email and the Figma app. - Students and educators could apply for the Figma for Education plan, which provided Professional-plan features for free. The updated Starter plan was designed to make Figma’s multiplayer experience accessible to teams of any size while reserving broader file capacity for paid plans.

Read original(opens in new tab)
FigmaFigjamCollaborative DesignReal Time Collaboration+1
figma2 min readCurated summary

Behind the feature: building multi-account | Figma Blog

Figma’s account switcher addresses a simple but widespread need: users often move between work, freelance, personal, and hobby projects. The feature lets people switch between separate workspaces while maintaining one public identity in Figma Community. Figma concluded that supporting multi-account use required rethinking the relationship between private creation, workspace boundaries, and public sharing. ## A Growing Need for Multiple Workspaces - Figma had expanded beyond product design into brainstorming, presentations, maps, vector art, wedding planning, and fan art. - Users increasingly relied on Figma both inside and outside their companies. - Many people had distinct roles—employee, freelancer, and hobbyist—but no straightforward way to move between them. - User feedback consistently identified multiple-account support as a major request. ## The Account Switcher - The new account switcher allows users to toggle easily between different Figma accounts and workspaces. - It replaces cumbersome workarounds for separating professional and personal projects. - Users can keep work projects and personal files distinct while remaining within a unified Figma experience. ## Separating Creation from Sharing - Designing and collaborating may require switching freely between accounts. - Sharing work introduces different concerns, including ownership, attribution, comments, and public identity. - Users can maintain a single public Figma Community profile and handle while changing jobs, companies, or creative contexts. - This preserves a consistent public brand without mixing personal work with company projects. Figma’s multi-account design treats account switching as more than a convenience feature: it establishes a foundation for separating workspaces while unifying a user’s public presence.

Read original(opens in new tab)
FigmaCollaborationWorkspacesMulti Account+2
figma2 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.

Read original(opens in new tab)
FigmaDesign SystemsCSSHTML+3
figma2 min readCurated summary

Completing a transit map | Figma Blog

Figma invites the community to help complete a digital transit map of the San Francisco Bay Area created in memory of transit advocate Courtney Garg Brousseau. After Courtney’s death, Figma employees recreated his unfinished project from limited reference images, with his family’s permission. The resulting Figma Community file is intentionally open for others to expand, correct, and remix. ## Courtney’s Transit Map Project - Courtney was a passionate public-transit advocate who was building a Bay Area transit map in Figma. - His design was inspired by iconic New York City subway maps. - After learning of his death, Figma worked with his family to preserve and continue the project. - Because the original Figma file was unavailable, Figma rebuilt the map from a small number of images. ## An Incomplete Community File - Figma published the recreated map as a Figma Community file with Courtney’s family’s permission. - The map still contains missing details because the reconstruction was based on limited source material. - The project reflects Figma Community’s collaborative model: people can share existing work and build upon it. - The map is intended for people interested in public transit, cartography, and design. ## How to Contribute Readers can help by: - Opening the transit map in Figma Community. - Clicking **Duplicate** to copy it into their drafts. - Adding to or refining the map. - Publishing their contribution back to the Figma Community. The article also directs readers to information about Courtney’s life, legacy, and nonprofit work. Ultimately, Figma presents the transit map as a collaborative memorial. Designers and transit enthusiasts are encouraged to complete and improve Courtney’s work while keeping his interest in accessible public transportation alive.

Read original(opens in new tab)
FigmaDigital DesignFigma CommunityTransit Mapping+1
figma2 min readCurated summary

By the numbers: one year of remote work | Figma Blog

Figma’s shift to remote work prompted an experiment to understand how teams collaborate when offline workflows move online. By introducing a template picker with remote-work-focused files, Figma increased collaboration and helped users discover more features and community resources. The findings suggest that curated templates can make remote collaboration easier and encourage broader cross-functional participation. ## Moving Offline Workflows Online - Figma increasingly used its platform for brainstorming, research, team building, and other activities previously handled in person. - The growth team hypothesized that templates designed for remote work could reduce collaboration challenges and increase activity beyond traditional design work. - Figma built a template picker offering blank presets and curated templates, then tested it with a portion of its existing user base. ## Results of the Template Experiment - Users who received the template picker had a **5% higher collaboration rate**, measured by edits or comments in shared files. - The picker improved feature discovery: - **10% more users** discovered frame presets. - **90% more users** used files from the Figma Community when creating files. - The benefits applied to both designers and cross-functional collaborators. - Popular templates covered design-specific activities, such as remote design sprints, as well as broader uses like whiteboarding and team-building. ## Collaboration Across Teams and Locations - After a year of remote work, Figma observed more collaboration across regions and time zones. - Designers worked more closely with cross-functional colleagues. - Teams began involving collaborators earlier in the design process. - User feedback on social media and requests for additional templates indicated that people valued and actively wanted these resources. Figma’s experience shows that thoughtfully curated templates can turn a collaboration tool into a broader virtual workspace, helping distributed teams work together more effectively.

Read original(opens in new tab)
FigmaRemote CollaborationData ScienceFigma Community+2
figma3 min readCurated summary

Behind the feature: comments, contextually | Figma Blog

Figma’s Community comments feature was designed to turn a mostly one-way publishing platform into a space for direct creator–audience communication. The team combined general feed comments with spatial, in-editor-style comments, while carefully adapting interactions to preserve the file-viewing experience. Technical constraints mattered, but the hardest work involved resolving subtle interaction and edge-case decisions. ## Why Community Comments Were Needed - Community users could browse, duplicate, and install resources, but had no straightforward way to contact creators. - Figma wanted the Community to support deeper engagement through questions, feedback, and discussion. - The feature introduced two comment types: - **General comments**, displayed in a feed beneath the file. - **Contextual comments**, attached to specific locations within the design. ## Adapting the Existing Commenting System - The team initially expected to reuse Figma’s existing in-editor comments with minor changes. - They replaced the previous iframe-based file preview to enable communication of viewport information. - They also had to consider performance when files contained many comments. - The larger challenge was interaction design: - Community files traditionally supported one-way creator-to-audience communication. - Comments created a two-way channel between audiences and creators. - Contextual comments required spatial navigation rather than a simple linear feed. - Users needed to inspect comment locations while still being able to pan across the canvas. - The team aimed to encourage commenting without diminishing the existing view-only experience. ## Exploring the User Experience - Engineering, design, and product worked in a close feedback loop. - Designers used animated prototypes and GIFs rather than only static wireframes because commenting depended heavily on interaction behavior. - Explorations considered: - Sidebar comment feeds. - Different ways to embed comments around the viewer. - Mini-viewers and canvas interactions for locating comments. - Prototypes helped the team evaluate ideas against technical feasibility, UI edge cases, and the launch schedule. ## Launch Priorities and Design Decisions The team prioritized three goals: - Make entering the commenting experience quick and intuitive. - Give contextual comments enough surrounding space to understand their position in the file. - Deliver a technically feasible, appropriately simple solution within the project timeline. As a result, contextual comments were limited to fullscreen view, where users had enough space to understand the design context. Clicking the minimized canvas expanded it into fullscreen mode, while clicking and panning were disabled in the smaller preview to avoid compromising the primary browsing experience. The feature ultimately required more than porting existing code: it demanded a new interaction model for combining comments, spatial context, and file browsing. Figma’s approach shows the importance of iterative cross-functional prototyping when adapting a familiar feature to a fundamentally different product environment.

Read original(opens in new tab)
FigmaUser InterfaceInteraction DesignIframe+2