Do you need a CMS for everything?
Posted: Sun Dec 22, 2024 9:13 am
Very often, web design development cannot do without a content management system, this is the reference point when creating a template. For text zones, a certain height must be observed, an upper layer for images must be provided, because the client may at any time require a change in the background. With CMS, we must act conceptually.
cms
Without using a CMS, the approach becomes more individual, you can make an unusual layout, set the location of elements, insert animation, original illustrations, etc. And, by the way, there is a very good chance that you will not need a CMS at all. Before limiting your ideas, ask yourself two questions:
How "rare" is the content of the future site?
Is there any chance of it changing?
If the information is not replicated across the entire site, then this is “rare” content, and usually in this case a CMS is not needed. And the longer the relevance of the text on the site, the more work can be devoted to it. Content such as news or product descriptions in an online store most likely need a CMS because they have a relatively short relevance. They will have to be updated regularly.
Will the cost of website design increase compared to a standard philippine phone number search illustration with text? Yes. Does it look more inspiring? We definitely think so.
Okay. Let's move on.
The Holy Book of Web Design: Do It This Way, Not That Way
Industry representatives (researchers, designers, developers) love to unite in communities and share their invaluable experience and developments with each other. The irony is that this is one of the main stumbling blocks on the path of creativity.
We love giving each other advice on how and what to do, and what – under no circumstances. And wherever possible, there are hints, clues, pointers. Over time, there are more and more of them, and from polite recommendations they turn into almost ultimatum-like demands.
You shouldn't define line height in pixels.
You shall not take the Lord's name in vain.
You must design a mobile website first.
You shouldn't write this important crap here.
You must not worship false idols and so on.
The irony is that other people's expert opinions greatly hinder creativity.
Our rulebook fails for two reasons. First, it's arrogance. We start to think that we have all the answers and that if everyone just follows the "best" advice, we can design a website that's perfect.
Although best practice has always been and remains best practice. Of course, we need some standards and patterns. We need to consider performance and usability and all the other things that make up web design development. The danger is that when too many people follow the same path, it becomes harder to create something alternative.
cms
Without using a CMS, the approach becomes more individual, you can make an unusual layout, set the location of elements, insert animation, original illustrations, etc. And, by the way, there is a very good chance that you will not need a CMS at all. Before limiting your ideas, ask yourself two questions:
How "rare" is the content of the future site?
Is there any chance of it changing?
If the information is not replicated across the entire site, then this is “rare” content, and usually in this case a CMS is not needed. And the longer the relevance of the text on the site, the more work can be devoted to it. Content such as news or product descriptions in an online store most likely need a CMS because they have a relatively short relevance. They will have to be updated regularly.
Will the cost of website design increase compared to a standard philippine phone number search illustration with text? Yes. Does it look more inspiring? We definitely think so.
Okay. Let's move on.
The Holy Book of Web Design: Do It This Way, Not That Way
Industry representatives (researchers, designers, developers) love to unite in communities and share their invaluable experience and developments with each other. The irony is that this is one of the main stumbling blocks on the path of creativity.
We love giving each other advice on how and what to do, and what – under no circumstances. And wherever possible, there are hints, clues, pointers. Over time, there are more and more of them, and from polite recommendations they turn into almost ultimatum-like demands.
You shouldn't define line height in pixels.
You shall not take the Lord's name in vain.
You must design a mobile website first.
You shouldn't write this important crap here.
You must not worship false idols and so on.
The irony is that other people's expert opinions greatly hinder creativity.
Our rulebook fails for two reasons. First, it's arrogance. We start to think that we have all the answers and that if everyone just follows the "best" advice, we can design a website that's perfect.
Although best practice has always been and remains best practice. Of course, we need some standards and patterns. We need to consider performance and usability and all the other things that make up web design development. The danger is that when too many people follow the same path, it becomes harder to create something alternative.