These 5 principles can be used to evaluate a component’s fit for TELUS Design System community components.
- Must follow digital design principles
- Must have an identified use case in at least 2 unique applications
- Must not include business logic or proprietary information
- Must be sufficiently different than other pre-existing components
- Should be sufficiently granular to promote reuse
“As part of the design platform, Community components should simplify a team’s path to production, enabling team members to do what they want to do, easily.” ~ Harry McIntosh, Director
- Communicate early and often . Let the Community know what you are planning.
- Community components have the most impact when shared across multiple situations, in many applications.
- New designs and UX patterns must involve Design Direction to preserve a high-quality, consistent end customer experience.
- Avoid including anything that may limit the breadth of reuse for a component - think functionally.
- Design system components are focused on reusable user experience patterns. Keep business logic, API calls, content, or other application-specific behaviour in the application.
- Any hard-coded strings, such as English phrases, must have the ability to be overridden in order to support multilingual applications
- Community components reduce duplication by promoting flexibility and reuse of existing code.
- Before creating a new component, consider whether an existing pattern and component is sufficient. If not, consider extending or adding features to an existing component before creating a new one.
- Design system components should encapsulate a single pattern or user experience "element." Seek to find the most granular, standalone, reusable pattern.