How to organize full-stack (web) development for a beginner?

Question

PHP

Hey!
I'll try to be brief. I decided to rewrite my old php-mysql project with manual layout and manual assembly from scratch in order to study modern development technologies using a live example. I have never touched gulp, sass, pug, bemto, etc. before, I wrote everything by hand. In general, the frontend began to make up. I took the TARS faucet , got into it basicly and the frontend went very quickly and conveniently.
Now I want to work with PHP (I would like to consolidate my knowledge of php, please do not offer to delve into ROR now :) ). I wrote a couple of custom tasks in TARS that are responsible for compiling and minifying from .pug, and as a result I got php pages instead of html (is this even legal?). Browsersync and everything else set up, so you can work.
And already after, inside the layout of the components in the PUG code, I started using php inserts, everything works.
Question. Where will all this lead as the project grows? Is it possible in principle to do so? Can I work like this with php in pug, and with the project in general? How to organize "component" php development inside gulp, store code in .pug or use it in some other way? With gratitude, I will take into development the proposed stack of solutions used by professionals.
Thanks in advance for your attention and advice.

Answer 1

You do not quite understand the stack of technologies that you are going to study. Your front-end vs. back-end boundaries are extremely blurred.
Your first mistake is that you, as you put it, are going to do component development with php and gulp. This is fundamentally not true, because gulp was conceived solely for building the front-end part of the project.
I'll try to give you an approximate list for the future:
1. Backend development in PHP - Laravel.
2. Front-end build - Webpack + Laravel Mix
3. Front-end development - ES6 +
Vue.js pornography.

Answer 2

One of the main mistakes is to use here or another technology in order to use technology. Technology should simplify something or speed it up, etc. There should be a transparent and tangible effect. You, as I understand it, are just using technology for the sake of technology. This is not true. It's possible for learning, but then the question is

Where will all this lead as the project grows?

not logical. No need to do nonsense for the sake of learning on a live project. Master the technology, then decide whether it is worth using it in a particular project.
You will be able to answer all your questions when you master these technologies. But you shouldn't do it on a working project.