Monaco Toolbox Discoverability
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 641
- Avg merge
- 12h 4m
- Merged PRs (30d)
- 57
Description
Through our user testing, we have found that many students aren't aware of the Toolbox as an aid in writing JavaScript or Python code.
6/7 participants were not aware of, and did not use the Toolbox to aid them in writing code
"Initially, I thought the Toolbox was something else - not actual code stuff, so I didn't use it. Maybe put some text on the top that says 'Code/Commands' or something so people know where to look"
"I thought it would be blocks, that's why I didn't use it"
"I did notice it, but when you told me to write code, I didn't think I should use it because it looks like it would be blocks and not code"
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
No file or test is named. Start by locating the Toolbox UI in the editor and review how JavaScript and Python users encounter it; use the supplied screenshot and user-testing feedback as the requirements. Done means the Toolbox is clearly recognizable as a source of code commands rather than blocks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, python, typescript
- Domain
- design, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100