-
-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Settle on technologies and framework to be used for the website #44
Comments
@ps2alerts/website-wizards Please offer your input to what technologies we should use :) |
Regarding front-end frameworks: Svelte Flutter Web React Vue Angular |
Personally I would go with Vue as I have more experience with it to the point where I can write more advanced plugins. I think Vue is an excellent choice as it is easy to setup with all modern features(e.g. server-side-rendering, SPA, lazy-loading, components). That said React is also a very good choice though it will be more work. Svelte I think is too bare-bone. Angular I see as more or less the same as Vue. And I have never really heard about Flutter. Also I want to propose Tailwinds as a CSS framework. Unlike Bootstrap and Bulma, which are component based, Tailwind is a utility based framework that is really flexible. As our layout is not that standard Tailwind allows us to do everything without the need to write any css ever. |
React would be my pick, but only because it's really the only front-end javascript framework I've used before, but not enough that I'd consider myself a wizard. It also has an expansive collection of UI component libraries. Regardless, I'm up for learning something new if everyone finds another framework more preferable. |
Framework now confirmed as VueJS. @microwavekonijn is to set up the initial framework for the website and collaborators will then hopefully flesh it out. |
The current website is in Angular 1, which is very very old. I was also very new to creating SPAs and JavaScript in general back then, however the design of the website still continues to hold to today's standards, mostly.
I suggest we gut the innards of the site and start that part again, however attempting to keep the design and feel of the site relatively intact, maybe with a few UX considerations.
To discuss August 20th, please offer your suggestions here in the meantime.
The text was updated successfully, but these errors were encountered: