3 ms·
I don’t want to copy and paste instructions and throw something together without a clue what’s going on Don’t read medium. Web world has less order than MSVS w
by wruza 4y ago
I don’t want to copy and paste instructions and throw something together without a clue what’s going on
Don’t read medium. Web world has less order than MSVS world, so you have to settle on a tech stack first and read these manuals. Also don’t think “hey it’s just web, I’ll figure it out”, it’s a path to headaches.
Here is my advice, based on I avoid frameworks but still get it done.
“Just html, css, js” will get old quickly, like in half an hour or so. You want to try it much later, after feeling okay in webdev.
For frontend start with Parcel or Vite, both are zero-config bundlers (as in compile, link, autoreload). You’ll need a separate Node.js-based project for a frontend. Use Bootstrap for CSS, since you can’t css yourself from ground up and don’t really want. Use Sass for CSS (you have it out of box with Parcel/Vite).
After a week or two with pure DOM, take a look at jQuery ecosystem, Mithril.js and Vue.
Frontend runs in a browser and is limited in what it can do.
For a simple backend (it talks to files/db, basically a regular program with an http server instead of gui) there are js and non-js options. Node.js Express. Python Flask. The key idea for searches in other languages is “I want to serve few files and api routes”. Make backend a separate project, web world is not zero-config ready for all-in-one projects.
Read most relevant parts of each manual and don’t visit medium unless you’re “in context” and know what you want exactly, but forgot where it was in a manual.
References: MDN, CSS-Tricks.
Stack: Node.js, Parcel/Vite, Bootstrap.css, Sass, Express/Flask.
This will be a good starter with a straightforward setup.