CMS

Many people use self-written CMS. What are their advantages compared to common ones (joomla, drupal, wordpress, etc.)?


Answer 1, authority 100%

Firstly, your own CMS has all the necessary properties.
Secondly, your CMS is easier to expand.
Thirdly, a self-written CMS is unknown to a hacker, so he may not understand where to start breaking.
Fourth (follows from the second), it is unlikely that anyone will agree to support someone else’s CMS, so you can tear money from the customer for this.
Fifth, the phrase “our CMS is already running %n% sites” significantly increases the self-esteem of the programmer/s.

Although, often, a self-written CMS from the inside is such a g-but in terms of meaning, coding style, and in terms of security, that even stand, even fall.
But its own.


Answer 2, authority 83%

I’ve been working on my CMS for two years now. Of the most significant pluses, I can single out the only one that is really important. I gained a lot of experience in development, I began to respect other CMS, I comprehended the details that I had not even paid attention to before. And the further I work in this direction, the more I approach professionalism. Because realizing your own mistakes is the first step to understanding others.


Answer 3, authority 42%

  1. No benefits (certainly over the three listed)

  2. A bunch of bugs and improvements that haven’t been caught yet. (You + your neighbor on the landing are working on your CMS, and on joomla, for example, a whole community – it’s one thing to write an engine, another to keep it up to date and constantly replenish with new extensions)

  3. “A self-written one is more likely to be more secure” that’s only on the condition that it was developed by a very strong programmer and that there will be no source codes for studying holes in the network – although craftsmen will not break it so they will drop it (this is without options) .

  4. “it’s easier to expand your own CMS” – Again, it must be well designed for this,

  5. “Often, a self-written CMS from the inside is such a Mr. and in meaning, and in coding style, and in terms of security, that even stand, even fall.” – GOLDEN WORDS

  6. “hardly anyone will agree to support someone else’s CMS” – As a website development studio, we don’t even undertake to dig into self-made engines, because it’s more expensive for ourselves and customers understand that it’s better to make a site on a popular CMS – there will be many with it in the future problems

  7. “the cost of self-written support may be less” – this is nonsense. many people work with well-known CMS and know them – and it will be more expensive both in time and money to understand an unknown CMS yourself

  8. @Arni“I got a lot of experience in development” – Totally agree this is the REAL (one and only) PLUS of working on your CMS


Answer 4, authority 8%

Firstly, you know your CMS, secondly, it contains only the functions you need, thirdly, it is written in your programming style, which allows you to edit it without any problems.
There are many advantages, the main thing is to know what you are doing.


Answer 5, authority 8%

In the event that a ready-made CMS does not require fine-tuning, it is more profitable than a self-written one. If fine-tuning is required, then the cost of self-written support may be less, because you do not need to 1) learn the CMS language, 2) understand someone else’s code, 3) understand someone else’s environment.


Answer 6, authority 8%

The self-written one is more likely to be more secure. Since the cracker will not know what he is dealing with. And in the common ones, I didn’t have time to go out, as they found a bunch of holes and posted them on the Internet.

Although you can make a self-written one by mistake or unknowingly full of holes


7, Authority 8%

I like the author of Sapopezny Srkipt (CMS) I want to list a couple of advantages:

1) speed of work at times higher (depends on direct hands of the author CMS)
2) Admins, if any, pleases the eye.
3) Easy to write modules
4) the author does not depend on anyone, that is, from the developer’s script update
5) Integration with any existing forum simplifies times in 4.
6) Since CMS is not used in “wide circles”, its source code is unknown, and therefore the chances that it is hacked, falling.

Well, now the minuses:
1-10) No minuses!


8, Authority 8%

The only advantage of its CMS in front of others and common can be considered that it will be more understandable and “native” or something. In its CMS, it is definitely not wanting to quickly melting crutches. For then there may be completely incomprehensible things.

Sooner or later, he wants to write something good, which in the future can be modified and adapted to new conditions. For a self-drawing, this is not such a problem. With common things are different. In view of the fact that sometimes it is necessary to shock all the kernel to understand how and where, the desire cools and writhes a fighter crutch (well, or if the development of the developer raises, it comes to the finish).

To anti-advocations, its CMS can be attributed to the fact that a large number of diverse modules are developed for common CMS. For its own, it is not developed such a large number of modules (and, most likely, these modules will be integrated into the kernel). This is due to the fact that it is simply not for this time, or a fantasy is limited to pressing concerns. As the saying goes: “One head is good, and two – better.”

But the undoubted plus of its CMS is “sharpening” under a certain service. Few people make self-writings universal.