UX Writers Need Design Systems, Too! - Pinda Phisitbutra (Config 2022)

preview_player
Показать описание
UX/UI designers have benefitted from design systems for years, yet no such system exists for UX writers. Join Pinda to hear how the team at SCB TechX decided to stop the madness and built their very first copy system – right in Figma.

00:00 - Introductions
1:28 - Consistency and reusability
2:42 - Content style guides vs. design systems
3:11 - Use Cases + Annie examples
4:26 - Behind the scenes demo
9:00 - Atomic Design
9:54 - Design Challenge: Browse + Search
13:22 - File Management
14:58 - Efficient copy alignment process
15:22 - Key takeaways
17:55 - Closing

#Figma #Config #Config2022 #FigJam #Tutorial #NothingGreatIsMadeAlone
Рекомендации по теме
Комментарии
Автор

Excellent talk. Regardless of the method teams choose to promote reusability and scalability in their designs, I love seeing UX writing promoted and advocated for in this context. Thank you!

phaedra
Автор

Thank you so much Pinda and your amazing team for putting this together. Indeed UX Writers are underserved. I hope things change for the better soon too.

blessingenofe
Автор

Excellent presentation; I love how UX writing is becoming very important; I would say crucial step in the design process.

adnanpuzic
Автор

Super useful. I’m going to create a content library for one of my products and I’ll definitely be referencing this.

DrewJohnson-godm
Автор

Very interesting. I'm curious why you use this method and not a plugin like Ditto or Frontitude? Ditto has a fully functioning search feature, the ability to preview where text appears in the Figma files, add tags to help filter your searches, and create a component library.
I'm definitely going to have another think about your method, but I wonder if Ditto doesn't do most if not all of this (and more, thanks to the search box) already?

UXHeWrote
Автор

Interesting. But isn't it hard to use components for choosing text every single time, and maintaining all strings in Figma as component variables? And the number of .Button-Text variants will be too many - delete confirmation itself will have multiple variants based on context ("Are you sure you want to delete (one/many)

Also, what about Localisation situations? Isn't it easier to use tools like Lokalise to manage strings?

HiranVenugopalan
Автор

very awesome! but how to implement all those copy component to the existing design which already on development? because if the answer is we need to replace the existing copy to the 'component copy', will it override all the component design? imagine you already have thousand designs..

nuraisyaho.
Автор

🤔Will there be copies outside from system? Instead of a "Component" - it's a one-use copy in your product. How to keep copies like it, especially if there are many?

lupylon