What are /r/WebdevTutorials' favorite Products & Services?

From 3.5 billion Reddit comments

The video is incorrect in its description of hoisting & scoping, and because of that also in its explanation of the difference between var/let/const.

Read this to get a better understanding: https://www.freecodecamp.org/news/var-let-and-const-whats-the-difference/ (I do not know the author of the linked article)

not to be a dick, but the bare minimum requisite to this career is googling things on your own. I have you more than enough keywords to get started. The job is largely learning how to use google effectively.

Honestly, I'd start w/ Wordpress if I were you. That's going to be the closest thing to what you need straight out of the box.

https://wordpress.com/learn/

call me ignorant, how is this easier than using a flat-file based cms like grav? I mean you can use markdown and create pages/blog entries directly from the CLI or via an admin GUI. https://getgrav.org/

My favourite technologies are Laravel (php, back-end) and Vue.JS (front end, JavaScript). You could use these tutorials. The laravel one you should be okay to jump into with very little web dev experience, as long as you stop and Google anything you don't understand. The Vue.Js one I would recommend learning a good amount of JavaScript first before you do it, because it skips over the basics

https://laracasts.com/series/laravel-from-scratch-2017/episodes/1

https://laracasts.com/series/learn-vue-2-step-by-step

Probably not the right subreddit. But I can tell you how to accept a file upload.

First, what stack are you working with? That will make this a lot easier to explain. I usually work with CodeIgniter, which has a system for uploading files. CodeIgniter is a PHP framework, though, and I know PHP is getting less and less popular. I'm sure React has something that will handle this, and you can do it in pure PHP, too.

At the end of the day, the notion is this:

• Using the <input type='file' > tag, the user selects a file for upload.
  
• The file is sent to the server for processing (this can be done asynchronously using front end code (js) or on form submit)
• Backend code receives the file and does something with it (saves it to the server, usually) and probably puts some data in a database to mark the file for association with a user, the time/date it was uploaded, filetype, size, directory location, and whatever else.
• From there, you can redirect the user to whatever the next step is.

Does that make sense?

Netlify has free custom domain support, automatic SSL for said domain, handles minify for CSS and JavaScript, lossless compression for images, etc.

There are also paid features such as analytics, with no cookies required.

Netlify actually has a good comparison listed directly on their website if you're interested in learning more.