Do I need an html template when developing a site?

Question

CMS

Good day.
From the very beginning of my training in html / css, I believed that after creating a PSD layout, it is given to a layout designer / frontender who creates an html template with an attached style file and js and other goodies, and only then does the programmer start to adapt / connect this layout to which -some CMSke.
But as it turned out, not everyone works this way.
I have a friend who takes PSD + terms of reference, then creates the necessary blocks / views / content on Drupal, and after that stylizes it. He motivates this method by the fact that there is no use from the html template, because when creating a dynamic site, it is 90% replaced by php cycles, and in support of his words, he shows me a couple of examples of his work (quite not simple in terms of site functionality) in which really there is practically nothing from the usual html code.
He also says that the same method of work is practiced at Ciklum , only their programmers make a website (on Drupal), and after them the layout designers set styles.
And the real question isIs the html template 100% needed or is post-content styling approach a good practice?
A big request to justify the answers.
Thanks in advance.
PS Topic "What are the stages of site development?" I read, there is no answer to my question.

Answer 1

I'm not a coder, but:
1) What would be something to style - some kind of html markup is still needed. At least from drupal this.
Further, imho can be divided into 2 cases:
a) if we are talking about a person who knows how to make up and code, then this is his personal business in what order and how to do it. I have a familiar coder who doesn't like to copy-paste the same blocks and writes cycles in php
:-) tricky overlays, etc. Since starting from a certain level, customers want something more interesting - this approach accordingly determines their maximum level.
In general, the question of who exactly pulls the layout is somewhat holistic, I know projects where the frontend part is very complicated - as a result, their backend developers simply output data to the template without any layout at all, and the frontend guys hook the layout on top.

Answer 2

Since Drupal is in the tags, I answer about Drupal - you try to pull at least one made-up template on the finished site. You'll understand everything in an hour :) If you're too lazy, I'll answer right away - a made-up template for Drupal is not needed.

Answer 3

Andead Absolutely right.
I recently finished "stretching" the finished HTML template on Drupal, and I can say with confidence that it would be much easier and faster for me to make up from psd.
Wordpress is a little easier.
But for a universal theme for CMS, it must define the standard classes that it generates.

Answer 4

In general, it is better to make an HTML + CSS + JS (Jquery) template, because a programmer (integrator) is often not a coder.
Integrating a template is easier than creating and integrating at the same time.
I myself often did this before, but it’s more convenient to share it.
Plus, it’s convenient to show the layout to the client, if he didn’t like something, it’s not difficult to redo it. But the finished site will be more difficult to remake.
Sometimes people immediately make a site on the engine, without design, template, etc.) then everything turns into a mess.