Code Coldspots
Problem to solve
Sometimes a project can become unwieldy in size. One of the ways of being proactive about maintenance is identifying code coldspots- like hotspots, but the opposite #33177 (closed)
I see this as dogfoodable with gitlab-com/www-gitlab-com#6015 (moved) where, because of the way the handbook is stored as code, we can identify what hasn't changed in a while and is likely out of date
Intended users
- Parker (Product Manager) => wants to make sure they're proactively identifying technical debt
- Delaney (Development Team Lead) => same as Parker
- Sasha (Software Developer) => same as Parker
- Presley (Product Designer) => wants to make sure old pages aren't being missed when rolling out changes to the style guide