ER: Wins randomizer content management
- Dominant language
- JavaScript
- Stars
- 363
- Forks
- 872
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 18
Description
### Dependency
- #4190 - need the documentation that this issue delivers before we can start on this ER
### Emergent Requirement - Problem
We need a way to
- know when we need specific practice area wins cards for the randomizer
- see at a glance which wins are in the randomizer (per practice area)
- keep track of which wins have been in the randomizer (in the past)
### Issue you discovered this emergent requirement in
- #2304
### Date discovered
2023-03-24
### Did you have to do something temporarily
- [ ] YES
- [x] NO
### Who was involved
@ExperimentsInHonesty
### What happens if this is not addressed
We are likely to end up with too many of one practice area in the randomizer or a super manual process for auditing that. And no plan for how to know what the past states were, etc.
### Resources
[wins spreadsheet]
### Recommended Action Items
- [ ] Make a new issue
- [ ] Discuss with team
- [ ] Let a Team Lead know
### Potential solutions [draft]
### Categories
- Community Management (we call it admin but we should move to calling it Community Management which is industry standard)
- Content
- Data
- Design
- Engineering
- Dev Ops
- PM (Project and Product)
- Research
- SEO/Marketing
- Fundraising
Contributor guide
Assessment
This issue has not been assessed yet.