— Alla Kholmatova, Future Learn / Source (Blog)
A name can limit or extend the perception of a component. You can name components after their style, their function or their intent. To name a component with its function or intent is a lot harder and requires a modular understanding of the correlations. But these kind of components will be more stable for future use.
— Yesenia Perez-Cruz, Vox Media / Source (YouTube)
Establish a clear shared language, which helps to make better decisions about the purpose of the components. It also helps collaboration go more smoothly and makes the design and development process faster.
Name things collaboratively, based on their high-level function. (…) It’s not so much about giving something a great name (…), but agreeing on the name. That determines how the element will be used and helps to ensure that it’s used consistently by everyone.
— Alla Kholmatova, Future Learn / Source (Blog)
A typical naming discussion on Slack:
— Alla Kholmatova, Future Learn / Source (Blog)
FutureLearn also has a physical space in their office, where they hang printed designs. There the discussions around naming can happen with a glance on the whole picture.
— Alla Kholmatova, Future Learn / Source (Blog)
IBM sent out posters with icons without labels underneath across global offices in the US, Mexico, Singapore, China and Germany. People should write underneath what they think what each icon means.
— Hayley Hughes, IBM / Source (YouTube)
Their engineers have the same naming as the design file specs. No matter the platform. When the language is the same, an engineer could build a design without looking at it, just by referencing the name.
— Hayley Hughes, Airbnb / Source (YouTube)