4 ms·
Here is what I do: - Make sure you know what you want to make For smaller pages (one page sites, not SPA): - Use one of bootstrap/semanticui, include their d
by artpar 9y ago
Here is what I do:
- Make sure you know what you want to make
For smaller pages (one page sites, not SPA):
- Use one of bootstrap/semanticui, include their dist files directly (dont get into
the npm/gulp/bower yet)
- Use their kitchen sink to pick up components (both bootstap/semanticui have loads of examples)
- Include JS dependencies the old way (copy the min.js manually in your project), keep try to keep this number low
- Try to avoid using frontend frameworks for these (say vue/angular/react)
For slightly larger sites (SPAs/Multiple page sites)
- Choose one particular frontend framework and stick to it (the productivity gain does not come from using a tool, it comes from using a tool repeatedly)
- Get the closest looking template from somewhere in above chosen tech (i usually pick one from https://themeforest.net/ https://themeforest.net/ but there are many free resources, like AdminLTE etc)
- Make sure it already has the build/minify pipeline setup (most of them have it)
- Adapt it to your needs
- marktangotango 9y agoI agree with this, although I'd add that building an SPA with bootstrap (or whatever widgets) with no framework can also be a valuable learning experience. You'll most likely end up with a ball of mud, but it's a great way to experience the problems that a framework like angular or ember are solving for you.
- jszersze 9y agoI also agree with that. Frameworks provide you with structure, once you spend some time getting used to it you will not have to think about building basic things anymore.