How to maintain and expand the site on a production server?

Question

Work organization

I would like to hear from professionals (preferably those who worked in a company / studio / team) about how the development (and then support and expansion) of the site is organized from the very beginning.
For example, I will take Wordpress, since it has the largest number of freelance orders.
I will describe my method (starting with layout):
- I get a psd layout;
- Layout. I make layout using the Tars assembler (something similar to BEM). This collector allows you to store html (pug), js, images, etc. one so-called component in a separate folder (for example, the slider folder with all the code for the slider). When building a project, everything is compressed, optimized, merged, etc. And at this stage everything is cool, each component is in its own folder.
- Stretch on WP. Everything is simple here, I cut the html and pull it.
- I'm downloading the site for further support and deployment in PhpStorm.
And then the mess begins, the collector is gone. For example, styles need to be corrected somewhere (sometimes from the WP admin panel), these styles are no longer compressed, prefixes for browsers are not put down, images are not compressed by anything.
But what if you decide that the "component" slider is no longer needed on the site, look for all of its css, js, etc. in files and delete manually?
And if you find a jamb in the "component", edit it on the site, and then edit it in the assembler (so that the next site doesn't have this jamb)?
And if you need to expand the site, add new "components", what then, copy css and js manually to site files?
It also often happens that, for example, there is a site with 10 pages, I made up half, and then I already need to show something to the customer, then I transfer what I have to WP and finish it on WP.
And something else. The back and front programmers are immediately waiting for the designer, then the back is waiting for the front. It seems like a lot of time wasted waiting. How to organize work so that you can work together with minimal loss of time?
In general, I ask you to tell me how you organize the development, perhaps even starting from the very beginning (drawing up the technical specifications for the designer, etc.).

Answer 1

Do not use VI
Or
Introduce discipline and do not write code through the admin panel at all
Prefixes for browsers are not relevant if you do not need support for IE8 Image
compression can be done regularly by crown
Draw a Gantt chart and understand what to do
PS: git, npm, webpack / gulp , composer, etc., etc. are not discussed because they should be by default
. Just like tests

Answer 2

Everything is in the git, if something needs to be updated, then everything is downloaded from the git, migrations are launched, a build occurs, etc.

Answer 3

Use frameworks prepared for layout and deployment, such as Themosys . My experience based on it: https://github.com/oxboot/oxboot , the difference is in using Laravel Mix to build assets. It will not be difficult to introduce Tars into it. You can do without frameworks and just organize the assembly directly into the theme folder. This is a 5 minute job. Deploying is convenient on Deployer, soon I will prepare an article on deploying sites on WP.