ember-learn / ember-learn/ember-styleguide-experimental
analyze survey needs
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
analyze needs for survey questions and create one ticket each for required components. ensure that keyboard navigation and accessibility are success criteria.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by analyzing the survey needs described in the issue, with keyboard navigation and accessibility as explicit success criteria. Identify the required experimental components and define a separate ticket for each; done means the survey needs are covered and the resulting tickets include those criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- accessibility, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100