Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Introduction
Standardised naming conventions enhance clarity, streamline collaboration, and facilitated system evolution.
In design systems, naming conventions are pivotal for ensuring consistency, clarity, and efficiency. Clear names, such as "error-red" for a colour, immediately indicate its function, streamlining communication among designers, developers, and other team members.
Standardised naming expedites the design and development process by reducing the need for continuous reference or clarification. It guarantees that references to specific elements are universally understood, facilitating smoother integration as the design system expands.
This shared language bolsters collaboration across teams, ensuring everyone understands each component's purpose. Such conventions prevent accidental duplicates, which can clutter the system, and aid in managing component evolution, especially when deprecating old elements or introducing new ones.
Principles
Using atomic design classification
Simple and descriptive
Scalable
...
- hierarchical structure (atoms, molecules, organisms, etc.)
...
...
Simple and descriptive - consistent naming rules (descriptive, clear, no abbreviations)
...
We are following atomic design…
...
Scalable
Atomic Design
Atomic design is a methodology developed by Brad Frost for creating design systems in a systematic and hierarchical manner.
The idea behind atomic design is to break interfaces down into their smallest parts, which can be combined and recombined to produce any number of UI variations. Atomic design breaks down UI components into the following levels: atoms, molecules, organisms, templates and pages.
Atoms
Component | Description | Mobile | Web |
---|---|---|---|
Button | (covers glossary) | ||
Icon | |||
...