Hosting & Domaining Forum

Hosting & Domaining development => Programming Discussion => Software & Scripts offers & requests => Topic started by: bandwo on Jul 07, 2022, 10:43 AM

Title: Own engine (CMS) - is it worth?
Post by: bandwo on Jul 07, 2022, 10:43 AM

The idea is to combine all existing projects on one engine and create new ones.

Forces of course third-party developers, myself at the initial level.

Given the diversity of projects (billing, info sites, exchangers, stock exchanges, etc.) as well as the diversity in end users (language, host countries), we need an engine that already has multilingualism, multidomain (different functionality on different domains with common base), multilocality (from the country of residence, the functionality in the same modules should also be determined, for example, registration requirements or the availability of payment systems).

So please tell me, is there something ready?

Multilingual-Multidomain. I was told to go to WordPress and Bitrix.

The first - I think it is not suitable for serious projects, and there is doubt about the correctness of the multilingualism of different modules.

The second one is generally evil for me, in my opinion, and besides, it makes no sense to take a paid one, if you still have to invest in writing paid modules.

In my understanding, there is only one thing left, to invest in writing your own engine that meets the following requirements:

Multilingualism - should be incorporated in the core itself and easily picked up on any modules. A simple mechanism for adding local text in the desired language to the engine and modules.

Multi-domain - any composition of modules and their settings for different domains

Deep modularity - the core should be completely empty, only module processing functions, everything else on modules that could be easily replaced / connected / disconnected without any breakdowns, installs, uninstalls (simple initialization).

Deep localization - depending on the country, it should be possible not only to display certain modules or their settings, but also to use data storage in separate databases (observing the requirements of some countries to store confidential information in the local country)

API for interaction between different sites on the same engine.

And of course, the engine must meet all modern requirements, these are: minimal load on hosting, fast work, security, SEO.

In general, I made a decision in principle, I need it, I just can't decide from a blank sheet or take any open source as a basis, since I haven't found 100% suitable open source. But I think not every programmer will be able to competently develop a structure, but in this I am definitely a layman.

So, I'm doing (by proxy) open source and waiting for your advice.
Title: Re: Own engine (CMS) - is it worth?
Post by: arhimed on Jul 07, 2022, 10:46 AM
Went through that stage.
We made own engine for our projects, but it quickly becomes obsolete, and there is no time left for its support and development.

There is always struggle begins, either for its lightness, so that it has only the most minimal set of functionality, but then in each project little depends on the kernel.

Eventually came to that we distinguish for ourselves the types of projects and some are made on ready-made engines (Bitrix, WordPress),
some are made from scratch (but using frameworks)
Title: Re: Own engine (CMS) - is it worth?
Post by: natmir on Sep 05, 2022, 11:46 AM
Self-written solutions
Websites based on "naked" HTML + CSS or their own engine have advantages and disadvantages. We propose to dwell in more detail on both sides of the coin.

The unambiguous advantages should include:

Excellent adaptation for individual web sites with non-standard functionality. For instance, bulletin boards or car dealer sites with the ability to select a complete set.
Less load on the server or web hosting, as there are no additional, useless modules.
Increased work speed. The reason is the same – the lack of additional modules, which are often not disabled in the CMS.
No load on the database (when using "naked" HTML with styles).
A high level of protection with the correct approach to writing your own CMS, since most of the "loopholes" or "Backdoors" in the engines are known to hаckers.
The disadvantages of developing from scratch include:

The problematic nature of developing a new CMS (for instance, increased money spending and the complexity of drafting technical specifications for programmers).
The inability to create new pages or categories in a couple of clicks (in the case of using a web site written only in HTML).
The need to understand the basics of HTML and CSS to update information on the site.
Ready-made CMS
Below we will get acquainted with the frequently used site engines, but for now we suggest focusing on the most interesting pros and cons of engines.

The unambiguous advantages include:

Ease of use. Most engines have convenient admin panels with the division of capabilities into user categories (administrator, moderator, editor, user). Where each group has its own access rights. For instance, the moderator has the ability to edit comments, post articles, and the editor has the ability to write articles and submit them for moderation.
Creating pages, categories, and editing meta-data are extremely simple processes.
A number of CMS have built-in visual editors or the ability to install that module as an add-on, which makes knowledge of PHP, HTML and CMS optional even when editing the skeleton of the web site.
Low load on the server or web hosting with proper optimization of the CMS.
Most of the engine's problems are solved with subsequent updates, including finding ways to hаck by hаckers.
Providing timely technical support (relevant for most paid CMS).

The presence of a huge number of modules that expand the functionality (turning a blogging platform into an online store, connecting extensions for more subtle optimization of pages for further promotion in search engines).
The low cost of a CMS (or the use of a free engine) is more profitable than developing a resource from scratch.
There were also disadvantages here. We suggest you to get acquainted with the disadvantages below:

Installation on web hosting, server is required. The minus is conditional, since most hosting providers offer the installation of a number of free and paid CMS in one click.
You need to understand the engine settings so that there is no additional load on the server.
Some modules that allow you to expand the functionality are paid.