fyysikkokilta / ilmomasiina Goto Github PK

Currently, one can add a Facebook event. However, this doesn't do anything.

Maybe it could be used to fetch an image for the event?

Currently the "cancel registration" with its warning info takes 1/3 of normal registration form and is in the same font as the other text. The big red "cancel registration" button is also larger than the "submit" making it look like the primary action in the form flow.

Make the cancellation be a pop-up that is opened from a grey-ish text and have that pop-up have the scary warning texts.

There are some typos in the event status views on the front page and on some other places that @heikki-simojoki and @rikhardranta found out. Assigning this to them.

Word wrapping is off in event titles (except for mobile view) so longer titles overflow under the registration box / out of the view.

Add a filter that excludes past events

Submitting a registration with over 255 characters in a short answer field gives the default vague "registration did not succeed" style popup. Browser logs show a backend call yielding a 500 error with appropriate error message.

The backend should respond with a 400 Bad request for this error and the UI should have an option to see this message (popup to have a down arrow which extends error details).
For this specific case the UI should also have a red hint and highlight around the box when i.e. 245 chars are typed and there's only 10 more left.

AC:

• Sort events by newest to oldest instead of the current one
• (Optionally) Add a button to change the sorting as well

Not all users are familiar with for example forcing a new line without a line break in Markdown. Make the hint text be a link to a guide so that everybody can learn how to do stuff there.

Dockerised backend would be a lot easier to maintain, frontend might as well be just static files.

Implemented in Athene upstream so blocked by #12

Some development appears to have happened at https://github.com/athenekilta/ilmomasiina/commits/otax/production, so we should make fetch from upstream and change anything that has changed too much.

Changes include at least converting @ handles to Telegram instead of Twitter

tietokilta/dev seems to be where future development is going to happen so better refactor FK changes to support this.

Potential challenges

• Check that TypeScript works -> convert current FK code to TS
• Use Docker Compose for backend instead of older method

Vaihdetaan oikea url-prefixi tapahtumille:
${domain}/event/ -> ${domain}/events/

Currently, texts, such as sähköposti, tapahtumat, nimi, are only in Finnish.
Either make them bilingual or add support for multiple languages.