Frontend Refactoring

[pixeldesu]

Retrosprings frontend was a 2014 hobbyist code project, and that's how the code really looks like at the moment as well.

To Do:

(S)CSS:

• [x] Switch from Bootstrap 3 to Bootstrap 4
• [x] Rewrite core elements in a BEM-style syntax
• [x] Use mobile-first approach instead of desktop-first

JS/Coffee:

• [x] Try to remove as much jQuery plugins as possible
• [x] Consider moving to a Webpacker pack and using ES6 instead of CoffeeScript

HAML/Layouts:

• [x] Utilize more layouts instead of copying the same partials into base-files
  • A great example for this are all settings and profile pages
• [x] Create more granular templates and a more defined structure than throwing everything into app/views/shared/
  • app/views/answerbox for all Answerbox partials
  • app/views/modals for all Modal elements
  • app/views/navigation for all navigations

Ruby:

• [x] Refactor a lot of conditionals for classes or URLs into helpers, to reduce in-template logic

[pixeldesu]

Giving a quick update on this, due to the fact that I won't have that much time in the next few months (basically the next 3 years) due to work/apprenticeship I will rework the frontend in another way.

Fixing Retrospring/bugs#95 (or being at the progress of it right now) I realized the frontend at it's current state is a mess, and it would be better having that rewritten as users are already suited to it.

Also, Bootstrap 4 is coming close and I'd need to do some migration work on it, pretty much changing all of the frontend aspects anyway, as they've dropped the .panel element.

So Retrospring will stay Bootstrap, but I will give the entire thing a cleaner approach to make the frontend code not that much of a pain as it currently is.

[pixeldesu]

We effectively removed as much jQuery as possible, the remaining libraries need to remain until we update to Bootstrap 5.

Some other small things can be ported quite easily or will be removed as a result of other issues, but this is done.

And regarding "Refactor a lot of conditionals for classes or URLs into helpers, to reduce in-template logic", this also seems to be solved with the Bootstrap 4 rewrite of the UI.