-
Notifications
You must be signed in to change notification settings - Fork 11
Frontend refactoring #65
Comments
👋 I could take a look during my holidays (from 1st to 13th of July), don't hesitate to list specific problems. Though, I would have not idea what I would do since I never used Vue but who cares? |
edit: fixed |
I am still wanting to help: preferably on the very front-end aspect. Would you appreciate some Bootstrap Vue integration? Or with another toolkit, I don't care... I have some experience using Reactstrap so it should be quite straightforward with the Vue equivalent. Otherwise, point anything that seems important to you related to the front and that you don't want to take care of. I'll take a serious look at the project tomorrow to understand better what it could need. |
I always used Bootstrap, so I guess Bootstrap-vue would fit here so I don't have to learn something else. I don't know what the others alternatives are too. Bootstrap-vue will be useful when we will have the new design assets, for now it's more or less "X is some page, implement an API for X, then write the Vue part for that X" For now the front does login, logout, register and that's it. |
I think in order of implementation priority I would like to do:
after the first item is completed, it's possible to start working on a better player for the tracks (needs compatibility with the JSON waveform we already have), and when user profile is done (it will permits listing tracks) it's possible to add a smaller player to this part. |
Doing a massive front refactoring, including #63 would most likely require switching to a SPA like Vue.js.
However I have never touched ever Vue.js or anything like that, so...
The text was updated successfully, but these errors were encountered: