Contributing to TDS - designer guide
Guidelines & Standards
Design contributions should be contributed in the form of a Sketch file (*.sketch).
The component being contributed should be in a stand-alone artboard and not part of a mock-up (this will reduce the risk of any confusion of what is being supplied for contribution)
All known variations of the component should also be supplied in the Sketch file
Files being contributed should be clearly named according to the TELUS Digital file naming convention.
Viewports and Grid:
Each design contribution should be supplied in the following viewports:
XL (desktop): 1200+ px with container width 1168 px
M (tablet): 768 px with container width 736 px
XS (mobile): 320 px with container width 288 px
For each viewport supplied, the TDS grid should be applied to ensure consistent sizing and measurements across the system.
Layers should be named clearly and not using the default naming (e.g. Layer 1, Layer 1 Copy).
Applying the above standards to the contributed sketch files will ensure a clean contribution that can be easily added to the DSM library and used by all teams. Contributed components will be used by teams within TELUS and also external vendors.
For any of the components being contributed, the file should have the TDS type stack applied to any and ALL of the text blocks in the contribution (e.g. Display, H1, H2, H3, etc).
Note: We understand that there are some cases that require the type stack to change slightly (ie. colour of H1). In these cases, please make the appropriate change to the file, and note it during the contribution and we can add the new type stack style to the TDS component library. This will help us manage and update the typestack in the DSM library for others consume.
Use of Symbols:
Any of the existing components in TDS being used in the NEW component being contributed should be maintained as a symbol from the DSM component library.
Any new components being contributed, should NOT be made into a symbol. We will do this on our end and add it to the master Sketch file. This will ensure that the NEW symbol is named and put in the appropriate section.
To reduce duplication or confusion between versions, TDS will manage any new symbols/components being contributed. We will add them to the DSM library once the code contribution has been made. This will ensure that code and design is aligned before we release for broader consumption.