There are 3 Epics created:
Think about features that would be solved by CSS. Such as , colour, focus, font-size, borders
Think about standardizing the way people do things in an application or on a page. For example, how should a user enter an address or date format
Think about standardizing components such as <button/>, <input/>, <datatables />, <datepicker/> or <navigational elements>. Be sure to note: what the design, UX and A11y considerations should be
What you will have to do: Create/Assign Issues
If you feel that there is documentation/standards/guidelines missing.
You will be responsible for Creating an “Issue” OR Use an existing Issue to “relates to” the appropriate Epic (Style, Pattern, Component).
For example, this existing issue — https://itdjira.csd.toronto.ca/browse/DTSTA-8 has been updated to include a “relates to” link to the Style & Presentation (Style) epic
Please ensure that all issues have :
- Screenshot
- Links to pages/applications in development or production if available
What we will do: Create Features & Document
- We will create Features to address the issues create.
- Each feature will relate to the standards documentation. The feature will be used to track the development and comments related to the standard
- For example, the Style epic — https://itdjira.csd.toronto.ca/browse/CTUS-2 has two Features Assigned.
- DTS - Development team and DCS - Design team will review and document features.
- As each feature is completed then they will be assigned “DONE”
- “DONE” means that we have created documentation to address that Feature.
- For example, the Colour Contrast feature https://itdjira.csd.toronto.ca/browse/CTUS-5 has two tasks to complete a Design Specification and Accessibility Specifications to document the colour contrast