"The interaction between Figma and Notion sucks. Part of having a more strategic role as a designer is participating in the conversations that shape the direction of the work. You may do a lot of work in Figma, but for most people, Notion is where serious discussions about work planning and scope happen. Why would you want to bring Figma text layers into Notion databases? It's way easier to track the progress on design work in Notion databases rather than in Figma."
"Opening and navigating Figma takes more mental effort - especially for non-designers - than Notion. It's also mentally taxing and distraction-prone to switch between Notion and Figma. Every time you switch apps, you risk being distracted by Slack or email. And sure, you can copy and paste your text layers one by one into a Notion database, but that is incredibly tedious, time-consuming, and not the best use of your brain."
"The workflow I'm sharing lets you copy a virtually unlimited number of text layers and import them into a new Notion database with useful properties like numbers and priority. You can also add statuses and other fields if you want. As an example, I'm going to use a heuristic audit I did recently for Zoios as an example. But you can apply the principles to your own workflow."
Figma and Notion do not integrate smoothly, creating friction for designers who must join planning conversations held in Notion. Notion databases are easier for most people to navigate, better for tracking progress, and reduce the mental cost of switching apps. Manual copy-and-paste of many Figma text layers into Notion is tedious and inefficient. The presented workflow enables copying large numbers of text layers into a Notion database with useful properties such as numbers, priorities, and statuses. The workflow includes practical setup steps like screenshotting screens, serial-numbering them, and creating an annotations component in a presentation kit.
Read at Medium
Unable to calculate read time
Collection
[
|
...
]