OverviewEdit
Technical and UX debt is a matter of priority to the reading web team. Here, we are displaying a list of themes of technical and UX debt which we have worked on and plan on working on in the following quarters of 2016/2017 (Q2-Q4). This list will be used to communicate technical and UX debt on a sprint-by-sprint basis within the team, as well as to summarize the goals and initiatives we have taken on tackling debt over time. Below each theme, an example of a task which would belong in each theme is displayed for reference.
UX Debt ThemesEdit
UI StandardizationEdit
Perceived PerformanceEdit
Visual Design improvementsEdit
- Alignment issues
- paddings / margins
- font sizes
UsabilityEdit
AccessibilityEdit
Low grade browser supportEdit
Technical Debt ThemesEdit
PerformanceEdit
- tweaking something to make the site faster
AccessibilityEdit
- writing accessible HTML
SecurityEdit
- addressing code with security issues
team workflows / internalEdit
- improving tools used by the team, e.g. replacing jsduck in favor of jsdoc
- updating tests
MaintainabilityEdit
- Making code modular
Clean-upEdit
- removing dead code
Improvements such as using new approachesEdit
- templates rather than inline PHP
- upstreaming and using the upstreamed modules rather than modules developed in an extension
- using resource loader image module rather than inlining images in CSS
Developer performanceEdit
- a list of articles to test against, etc.
Common ThemesEdit
- Accessibility
- Low grade browsers
- Usability