max-mapper / max-mapper/web-mpd
Add backend for keyboard/beat storage
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 26
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Today I assembled my first keyboard that exceeded the URL-length limit. It was a keyboard where every key was its phonetic sound, from clips off dictionary.com, so you could type and speak.
Anyways, I think long term we should make a backend for storing the keyboard/beat info, so people can "save" and it will store, and the URL will be an ID instead of all the stored data.
@kumavis had the idea of persisting to github gists, which I know @maxogden has a module for, so that's an option..
Oh, if you want to paste my phonetic keyboard into local storage, I posted it as a gist here.
Contributor guide
No contributing guide indexed for this repository
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 reading the issue body and the linked phonetic-keyboard gist, then inspect the repository to locate how keyboard and beat data are currently encoded in URLs. Compare a GitHub Gist-based approach with other persistence options and define the save/load behavior, including ID-based URLs, before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100