i18n support will be costly, but this could open the application to way, way bigger audience.
[ ] Extract static strings to consts in a language file.
[ ] Detect user's language as the first thing in init, and use it if it has not been overridden already (aka present in local storage with some value).
[ ] Load words with ajax calls to endpoints with some additional flag (e.g. 'en' would load locations_en.txt).
[ ] Rename current files to *_pl.txt.
[ ] Fill the database with translated words.
[ ] Add a language icon next to about. It should open a panel with language selection menu. It will also nicely balance the footer with 2 icons on the left and 2 icons on the right.
[ ] When user clicks a different language, the page might have to reload completely. This might be needed for screen readers that use html's lang attribute for speech language selection. Research this topic to find out if it's true.
[ ] Is the domain good enough to English-speaking improvisers? Maybe a different one will be nice?
[ ] Descriptions, titles and media images should be handled as well. No idea how that could be done...
i18n support will be costly, but this could open the application to way, way bigger audience.
'en'would loadlocations_en.txt).*_pl.txt.