We need to decide on the proper naming of our products so we have consistent naming for internal documentation and we set the right expectations for the end users. This issue also serves as a place to store the documentation & rationales behind our naming conventions.
Background
Related issue #509
History:
2021-2022: It seems that there has never been any formal discussion around one consistent naming. Previous documentations show the terms "Universal Design Systems Template", "HfLA Design Systems Template", "Component Library", "Figma Design System" and "Figma UI Library".
2023: The following comments include discussions around the naming.
Overview
We need to decide on the proper naming of our products so we have consistent naming for internal documentation and we set the right expectations for the end users. This issue also serves as a place to store the documentation & rationales behind our naming conventions.
Background
History:
2021-2022: It seems that there has never been any formal discussion around one consistent naming. Previous documentations show the terms "Universal Design Systems Template", "HfLA Design Systems Template", "Component Library", "Figma Design System" and "Figma UI Library".
2023: The following comments include discussions around the naming.
Action Items
[x] Set a date for the Namestorming session
[ ] Each team members create a list of possible names + a short blurb about why that is a good name
[ ] Discussing the options at the namestorming sessions
[ ] Create a shortlist of the names
[ ] Plan a quick research study to collect user feedback with open-ended questions about their expectations after hearing each name
[ ] Send a survey to UX-UI CoP
[ ] Share the results with the team
[ ] Choose the official name
[ ] Change the name in GitHub Milestones and working files
Resources/Instructions
Design Systems Template Figma file Our DS team workspace Figma file HfLA Figma Kit