guardian / guardian/dotcom-rendering
[Q1 Candidate Assessment] Template
- Dominant language
- TypeScript
- Stars
- 274
- Forks
- 34
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 121
Description
## [Insert candidate item description, e.g. iOS gallery captions]
**Owner:** [Name]
**Links to context docs / Github issues (if applicable):** [Insert / remove]
---
### 1. Direct impact on consolidation
**Does this directly bring us closer to decommissioning duplicate platforms?**
- Which legacy template/component does this help remove and how?
- Which migration milestone does it unblock?
**Assessment:** [Insert]
---
### 2. Reduces time, risk or cost of decommissioning
**Does this meaningfully reduce the time, risk or cost of safe decommissioning?**
- What aspect of the migration becomes faster or safer?
- Can we say roughly by how much?
- What evidence supports this?
**Assessment:** [Insert]
---
### 3. Mitigates material user-facing, security or operational risk
> Material = user-facing errors/downtime, security exposure, reputational risk, significant operational challenges etc.
- What specific risk does this work mitigate?
- What's the likelihood and impact if the risk materialised?
- What happens if we don't address this in Q1?
**Assessment: [Insert]**
---
### 4. Estimated effort
Input what's currently known
- Size: [Insert rough take on # of people + sprints]
- Key dependencies: [Insert]
- Unknowns to consider: [Insert]
---
### Recommendation
Based on the above, should this work be categorised as:
- [ ] Directly impacts consolidation
- [ ] Acceleration enabler / risk reducer
- [ ] Defer to stabilise / elevate phase
**Rationale:** [Insert]
Contributor guide
Assessment
This issue has not been assessed yet.