Create Developer Persona for Knative
- Dominant language
- No language data
- Stars
- 13
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
## What is changing? (Please include as many details as possible.)
We want to create a developer persona, complete with persona name, attributes, wants, needs and pains.
## Context
The DUX WG has expressed interest in separating the documentation by persona, this would be a first step in achieving that outcome.
## How will this impact Knative users?
Users will more easily be able to find topics relevant to their persona as a developer, and not be bogged down with the complexity of other persona's needs (such as administrators)
## Prototype
N / A
## Potential Feature List
N / A
Contributor guide
Research direction
Start with the issue requirements and the stated DUX WG goal of separating documentation by persona; no files, tests, or entry points are identified. Define a developer persona with a name, attributes, wants, needs, and pains. The work is done when that persona is documented clearly enough to guide persona-specific documentation.
Written by the indexing model from the issue text.
Assessment
- Domain
- design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100