Redesign v2 with bootstrap

[zapobyte]

Hello,

As mention in #360(which can be closed as changes are included in this PR) I've mostly finish implementing and redesign using bootstrap of the whole website. Here is an album with some screenshots from the new layout if you want to take a look first: https://imgur.com/a/AVZppKS

Everything is still the same as I did not change anything in regards to what have been done or added to much. Below is a bit more detailed change log of what have been so far and what's still needed.

Hope you will like the work and waiting for your feedback and would appreciate some help testing as to be sure everything works as expected. Aiming to finish the rest of the items by the next week.

Change Log

Front-end log

• implemented new design using bootstrap for all web pages(nothing is changed, everything was just transferred in the new layout)
• removed jquery usage in website. jquery still present as dependencies due to bootstrap v4.5(latest) still using it. it will be removed all together once bootstrap lunches v5.
• added Discord contact details in the FAQ and Contacts page
• screenshot page todo?(is this still needed, found some traces of such sort) or just use the screenshot add form from button?)...

Remaining TODO item list:

• [x] Lua advance button logic from map details
• [x] Add screenshot button logic from map details if uplaoder
• [x] Advance rules on map button logic from map details
• [x] Map rating system
• [x] Registration page accounts
• [x] tweek,align margin,paddings etc... Django(backend) log:
• updated requirements.txt for all dependencies as much as possible without broken current setup.[needs upgrade to django still so a rewrite will be in progress).
• fixed comments page break due to no comments entry in DB. File changes: changed in openra/views.py if comments exists( len of comments > 0) upon db pulling to return comment data, else nothing find message is shown.
• migrations files refactor. Files changes: migrations file like: openra/migrations/0001_initial.py removing unnecessary full object call for on_delete of delete type from models
  • ('user', models.ForeignKey(on_delete=django.db.models.deletion.CASCADE, to=settings.AUTH_USER_MODEL)), +('user', models.ForeignKey(on_delete=models.CASCADE, to=settings.AUTH_USER_MODEL)),

[zapobyte]

I think this is ready for review. It should have all the components from the original site,just made some adjustments to display map and it's like this now(all the down areas are collapsible components) : :crossed_fingers:

[Leo512bit]

I like this! When is this going to happen?

[dsimmons87]

@zapobyte it would be really nice to get these updates that you've made into the Resource Centre code. It looks so much better and looks like it was a huge amount of work. Unfortunately the RC doesn't really get that much attention, so I guess nobody picked it up.

I've been working on getting it all updated code-wise, so will be fairly active on here. The aim is to get a good test suite in and update everything to the latest stable versions, so that it will be possible to work on it properly again.

Anyway, with your PR, I can see there are some changes to the models, convert tags, migrations and requirements files. Are these needed? Just as they are conflicting with other work and I don't think they should be needed. (Besides migrations shouldn't be edited once the database is live).