Things that can be improved

[bra1n]

Admin:

• [x] admin area: use a different color in the for "live" toggles (maybe green)
• [x] admin area: have paging buttons both on top and on bottom of questions list
• [x] admin area: add confirm dialogue when deleting a card
• [x] admin area: allow copy & paste of question text
• [x] admin area: allow "minor edits" to not outdate translations
• [x] admin area: look into card order
• [x] admin area: use multiverse IDs for card image rendering (instead of name)
• [x] admin area: adjust sidebar tab styling
• [x] admin area: keep user logged in longer / across sessions
• [ ] admin area: handle authentication issues when setting questions live on the question list
• [ ] admin area: improve session / authentication handling when logged in for long periods of time
• [x] admin area: use Gatherer ids for showing card images instead of card names
• [ ] admin area: show the URL after adding a new question

  Questions:

• [x] questions: order cards by layout, name
• [x] questions: clear cache when adding new questions
• [x] questions: show split cards rotated (rotate(90deg) scale(0.75))

  General:

• [x] general: allow the booth to be easily hosted in a subfolder
• [ ] general: add a tagging system to questions
• [ ] cache offline export to reduce system load
• [ ] provide an easy way to get the question database as a CSV / SQL file
• [ ] fix dropdowns on mobile
• [x] fix error when there are 0 questions in the booth
• [x] add a standard question and standard user to the .sql dump
• [ ] use pretty (mana) symbols in question and answer text

[bra1n]

Questions are now always accessible by their ID, but will only show up on the booth automatically if they are "live".

[Takeno]

What do you think about Progressive Web Apps?

I was looking at offline code. Application cache is a bit complex in this scenario because you must handle the double code for online & offline version.

I think Service Workers can provide a better experience for developers & users. A network proxy with internal cache is a trasparent offline handler which can prepare your application for offline without any additional action.

Another nice to have is app manifest to let users install JudgeBooth as a "native" app.

[bra1n]

I think offline mode is a nice feature, but it was way more important when the booth started. Nowadays, basically everyone has internet everywhere, so it's probably not as important as it was back then anymore. If I had to re-implement it from scratch, I would probably also look into Service Workers and stuff like that, but back then Application cache was the way to go. Feel free to implement whatever you like, because I'm no longer maintaining this codebase myself.

[Takeno]

Let me merge the discussion of https://github.com/bra1n/judgebooth/issues/13#issuecomment-406885467

As mentioned in the other issue, I'm no longer maintaining the code base since I've dropped out of the project. @saveriopalmieri wanted to take over the code but as far as I'm aware, there hasn't been anything pushed back to GitHub. I think it would be best if you could reach out to him - I personally have no objections to adding you as a contributer. I'll also ping the current project lead and let him know that you'd like to help out.

I didn't know this project was unmaintained. I discovered this few weeks ago from an italian judge. I think it can be improved or developed from scratch easy, bringing all the data and knowledge already here. I'm trying to create a tech community of judges to help projects like this to keep themselves alive. I would like to help this project if the project leader wants.

I'd just like to know if any contributions on this repository will be available to users or not ;)

[bra1n]

Well, the project itself is pretty alive, it's just the code base that I'm no longer maintaining. Content-wise, there's still a lot going on. Regarding your contributions to this repo: @saveriopalmieri is hosting the current code and only he can tell if he's updating it along with the commits here.