Don't be like me thx

Create backend & frontend views for /information pages, including About us, Contact information sections and a feedback form for the website interface. We can put the form in About us page or separate them. It's fine either way

Following the discussion in issue #10. We will now try to extend our user model to support password authentication.

Feature/Enhancement Description

OAuth is being used for login so that new users don't have to register for a new account providing that they have a WCA account and ID. This puts a limit on who can sign in to our website, and some people might not need a WCA account in order to create meetup events.

Tasklists Suggestion

• Extend our current User (Cuber) model to have a password field.
• Implement registering.
• Implement login with password.
• Allow registered user to connect with their WCA account to sign up for events and competitions.
• Email verification. THIS IS IMPORTANT

Additional Comments

This is only required for master branch. Run python manage.py check --deploy for more details.

In general, there are settings for Debug mode, logging, database access, Https and proxy, cookies settings that need to be taken care of

😢 ya know

Feature/Enhancement Description

This is obv a better packaging management tool

Tasklists Suggestion

• Try setting up pipenv on local
• If it works, remove requirements.txt and rbvn folder for virtualenv since pipenv will use a different folder to manage virtual environment
• Update README with our changes to setting up the repo

Additional Comments

Feature/Enhancement Description

This is a continuation of #10. As we have kind of agreed on the model used, we can now proceed to design and program the user flow for event scheduling.

Tasklists Suggestion

• Design user flow
• Create views for each page

Additional Comments

Client browser won't have to refresh every time a user changes a single search filter. It provides better UX I guess?

Should test some basic Http requests

Feature/Enhancement Description

There was pagination when we were rendering all results into a template. The json endpoint currently doesn't support that.

Tasklists Suggestion

[edit] I just thought about it and we only need to handle on front-end
[edit2] I'm dumb. This needs back-end also

• Write helper functions for pagination because Django's paginator does not serialize well
• Paginate on server side
• Use Ajax to get results at certain page and render data
• Add navigate buttons

Additional Comments

Feature/Enhancement Description

In order to keep our README concise and other docs organized, it's better to put some contents to this repo wiki pages.

Tasklists Suggestion

• Git installation (Linux/Windows/MacOS)
• Cloning and deploying locally with Docker
• Importing WCA database
• Workflow + some useful resources for learning

Additional Comments

We might want custom html pages for 404, 500, 403, 400 errors instead of the default ones provided by Nginx

Feature/Enhancement Description

The current installation script is written in bash, which would be nice if I didn't suck at it 😢
From my observation, it's prone to runtime errors, and more often new developers had better follow the installation steps manually.

Edit: let's give bash one more try 😛

Tasklists Suggestion

• Use python for easier arguments parsing
• Look into executing privileged commands for apt install or w/e in python
• Rewrite install.sh
• Install dependencies
• Populate config file
• Set up MySQL account
• Process WCA database export
• Perform migrations

Additional Comments

Comment on this issue if there's any progress made

Feature/Enhancement Description

One of my initial intentions when this website was started is to provide a common platform for local speedcubers to create, announce and manage meetups or small unofficial competitions, and ultimately WCA competitions. It would be amazing if we can integrate OAuth from WCA for user verification, too.

Tasklists Suggestion

• Design a user model. Only logged in users can create and manage events
• Integrate WCA's OAuth system for logging in/out
• Design an event model. We also need to categorize our events (e.g: cubers meetup, unofficial competition, WCA competition, etc)
• Back-end views
• Provide a front-end for it

Additional Comments

We need some info about rubikvn (the outdated forum, ongoing projects for our new website, and the speedcubing community)

For the feedback form, we need some relevant questions to ask our users about their browsing experience, feature request/suggestion, bug reports.