Confused, guide?

Question

Backend

Hello dear experts!
In short, I studied the layout of html, css, scss, figma, etc. (a little bit of js) for a month, but I seem to have mastered everything and it’s not bad for a beginner, laying out a landing is not a problem
. I can decide how and where to start, everything seems very complicated, I start one thing and without noticing it I turn to another, as a result of knowledge 0. How to be in this case, can anyone help, guide, give advice !?

++ I’ll describe how the problems started, for example, I’m making a simple blog and starting to finish (improve) I wanted a simple admin panel like add / edit a post, upload multimedia, login form and then a dead end began

Answer 1

You need to start with simple things.
It’s difficult to write a blog with an admin panel on your own, but everyone is used to the fact that you can take ready-made tools and file it down, but when it comes to writing something from scratch, everything immediately falls into place. Choose an easier task to start with.
There are two radically different approaches (you must first choose which way to learn)
- when a web application is mainly developed on the server, the html code is generated by the backend and sent to the client in the browser, defining the entire interface (this is an outdated approach but is still actively used)
In this case, the backend literally generates html code (and sometimes css, right on the fly, but this is not often practiced), php began with this, it is an html template language, it just developed so much that it became an independent and very effective programming language.
- when a web application is mainly developed on the client side, everything related to the interface logic and information display is implemented in javascript in the browser, the server is the backend, but it is mainly responsible only for business logic, checking input values, access rights, and other things, communicating with the client side using your api, generating, for example, json lines with variables, from which the client collects the page. In some simple cases, the backend will be a simple layer to the database.
I recommend starting immediately with the second one, it greatly eases the load on the server and the network, frees up UI solutions and in general this is the right direction in principle, but there are still problems with search engines that do not work well with such web applications.
Unfortunately, if you choose some approach, it will be very difficult to change it later, consider redoing everything again
...
It happens that these approaches are combined, more often expanding the first option so that part of the interface (animations, menu operation, etc.) is implemented in javascript but the content itself is somehow generated on the server, solving problems with search engines and SEO.
The first approach is a lot of coding on the server side, little on the client side, the second is a lot of javascript code.
When you choose the second approach, some use logic when choosing a language for the backend, if I write a lot of code in javascript, why not write the backend in it, a single language, reusing the same methods both on the backend and on the client side. Therefore choose nodejs.