Layout for CMS or CMS for layout?

Question

CMS

The following question arose: the client chose a specific cms, we work only with it. She has principles by which she works. At the same time, the layout designer does not take them into account, and says that "I do it beautifully, and you bring the system to my layout." Question: should the layout be done in accordance with the principles of the system or is the system brought to the way the layout is done? What do you think? What are the pros and cons?

Answer 1

Layout has nothing to do with CMS.
You are confusing:
There is a layout - "cutting" a PSD layout in HTML/CSS.
And there is a template - here it is made for a specific CMS based on layout.
If there was an agreement with the layout designer to stretch the layout on your CMS - let him do it.
If only the layout (layout) - then you will have to pay extra for the template, because. this is a separate additional work of creating a template from HTML layout for a given CMS.

Answer 2

CMS often adds a lot of classes and tags. Therefore, it is necessary to make up taking into account the features of CMS.

Answer 3

I am always baffled by questions like "how to make up for such and such a CMS" or the requirement "to make up for a CMS".
Guys, if the layout is normal, it will fit on any CMS. If this is not the case, then the point is not that it is under the CMS, but that the layout is crooked.
If the normal layout does not fit the CMS, then throw out this CMS.
They often say - "do you make up Bitrix"?
I've been working with Bitrix for ten years and integrating different layouts - it's still a mystery to me what it means to "layout for Bitrix".
Normal semantic layout stretches over it at any angle. Yes, sometimes it can be done in such a way that you need to somehow break the standard component, since the template "breaks the tags", but firstly, this is solvable, and secondly, this layout is ALWAYS with broken nesting semantics.
For the sake of interest, can you give an example of where the layout is not stretched on some CMS and why?

Answer 4

Don't kick me)))

layout should be carried out in accordance with the principles of the system

( dot ) (bold dot)
Until I achieve the functionality (maybe not the right word) of the system: Lists, Links, main content, not main content. Everything should work correctly.
And based on the data, I build the markup, if I understand correctly - this is what you call layout.
Although if it turns out badly, I go back and change something in the data, but the core remains the same.