Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

I tried visiting debating.web.app but got the following error:

Uncaught ReferenceError: compose is not defined
    at Object.164 (index.js:277)
    at l (bootstrap:79)
    at Module.<anonymous> (2.d14b96c1.chunk.js:2)
    at l (bootstrap:79)
    at Object.166 (app.5e52e444.chunk.js:1)
    at l (bootstrap:79)
    at t (bootstrap:45)
    at Array.r [as push] (bootstrap:32)
    at app.5e52e444.chunk.js:1

caused by this line:

const composeEnhancer = window.__REDUX_DEVTOOLS_EXTENSION_COMPOSE__ || compose;

Is your feature request related to a problem? Please describe.
We need a new frontend! It's going to be built using Yew, as Rust + WebAssembly web framework.

Describe the solution you'd like
Should handle all the necessary stuff – e.g. logging in, logging out, updating data, etc.

Describe alternatives you've considered

Additional context
I'm building a GraphQL runtime to go along with this.

Describe the solution you'd like
Clippy is the official Rust linter.
It can be invoked with cargo clippy. It will need to be configured to cause the CI process to report an error if there's a warning.

Clippy should be run in between these two steps:

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Is your feature request related to a problem? Please describe.
I often find the calendar can be confusing because the days don't appear as I'd expect them to.

Describe the solution you'd like
I want the first column of the calendar to be Monday and the calendar to align itself to suit this arrangement.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Currently the calendar looks a bit like this:

Ideally, the first day would be Monday (not Wednesday) and the second Tuesday and so on. To do this there would need to be either:

• an offset (with blank days)
• events from the previous month would need to be introduced

Describe the bug
It takes a couple of minutes (on a slow internet connection) to load the app.
To Reproduce
Steps to reproduce the behavior:

1. open https://debating.web.app in your browser

Expected behavior
The app to load quickly

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: MacOS
• Browser: Chrome, Firefox and Safari

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Is your feature request related to a problem? Please describe.
I really rushed things when I wrote the server. It would be nice to resolve all the numerous problems in it.

Describe the solution you'd like
The server should compile without the Rust compiler raising any warnings.

Additional context
None.

Is your feature request related to a problem? Please describe.
It is not

Describe the solution you'd like
I'd like to be able to take a register in the app.

Describe alternatives you've considered
None

Additional context
Club administrators should be able to take a register for all events in the calendar.

Is your feature request related to a problem? Please describe.
I might not want to give my password to the app.

Describe the solution you'd like
I'd like to be able to click a 'sign in with Google' button to allow me to log in using my Google account.

Describe alternatives you've considered
Email and password

Additional context

Is your feature request related to a problem? Please describe.
I want to be able to judge debates and provide feedback to people in my club with greater ease.

Describe the solution you'd like
I'd like to be able to input notes for each speaker and give a ranking to them.

Describe alternatives you've considered
Pen and paper.

Additional context
Some work has started upon this.

Is your feature request related to a problem? Please describe.
Rocket is a nicer web framework to use than Actix Web.

Describe the solution you'd like
Instead of using Actix Web, the server should use Rocket.

Describe alternatives you've considered
Warp

Additional context
[ ] The impl::FromRequest for Claims might need to be reworked to use Rocket's equivalent trait.
[ ] Juniper has first-class integration for Rocket with the juniper_rocket crate. This should be used instead of juniper_actix and the server/Cargo.toml should be updated to use a specific release of juniper_rocket and juniper (instead of linking to a specific git commit).

Is your feature request related to a problem? Please describe.
I'm concerned that the project might have a lot of bugs in it.

Describe the solution you'd like
I'd like a series of unit and functional tests to ensure the app works properly.

Describe alternatives you've considered

• Releasing bugs onto unsuspecting users and asking them to report them.
• Reinforcement-learning based automated testing.

Additional context
There is currently a file with one test which is guaranteed to pass.

Is your feature request related to a problem? Please describe.
My feature is not related to a problem.

Describe the solution you'd like
I'd like to see a list of users who have confirmed their attendance to an event in my club's calendar (only if I am an administrator).

Describe alternatives you've considered
None

Additional context
The option to view this data should be in the detailed event view (at the url location /event/:id) and show a list of users who have confirmed attendance as well as all the users who have not confirmed attendance.