Creating a blog - creative searches
Which engine to choose for the site?
Modern history of the blog "For Tea".
Once we were invited to another business center for the production of secret works. Nothing to do, let's go. He placed the brigade in its place, marked the scope of work, and he, as befits a brigadier, began to idle.
It was a pity to waste time just like that, without any sense, and I went to create the appearance of vigorous activity, that is, to cut out of paper the design of the future site.
At that moment I was very worried about the question on which platform to transfer the site “Over Tea” , so that it would be comfortable for me and my friends to write in it, and for this to cause as little rejection as possible.
About rejection, I spoke not by chance. The previous engine on which the site was implemented - joomla at the end of its stay caused only an emetic reflex. Crude platform with a bunch of piles. Working with joomla was sheer agony, that's a fact. In this, I wanted something more user friendly, sharpened for an ordinary user.
Began the search engine. For a couple of months I had to sort out: wordpress, drupal, and only after it I turned to livestreet.
Briefly about each of the engines:
1. Joomla
Mostly designed for classic sites, sites - business cards of companies.
')
pros
the ability to create a complex site structure,
seo oriented engine
good support of domestic specialists,
A large number of free and paid themes site design.
low resource consumption
minuses
it takes a lot of time to understand the structure of the engine
Enough raw engine, a lot has to be tightened up.
there are a lot of raw modules for the engine, most of them are made frankly “on the knee”. It is necessary to sweat to make the "assembly" work stably.
The main reason for the lack of development of the engine and modules is its free of charge, and free of charge in everything. It is worth considering that if you do not pay money for the engine itself, then you will compensate for this savings with your time spent reading the support forum. And I assure you that you will kill time essentially with big money!
2. Drupal
This engine is perfect for large portals, in fact, I position it for myself that way. I will give an example, taking the well-known site, habrahabr.ru , as a reference point; the guys were able to achieve similar functionality with regular modules: Shvarabvvr .
I think comments are superfluous.
pros
the possibility of creating a super complex (!) site structure,
seo oriented engine
sufficient support of domestic specialists,
minuses
high resource intensity
site design will have to create their own, ready to manage skins will hardly be able to
it takes a lot of time to understand the structure of the engine
there are a lot of raw modules for the engine, there is a problem of supporting the evolution of the modules, that is, if the module is suitable for version 1.0, then it is not at all the fact that it is also suitable for version 1.1.
it will be extremely difficult for one to raise something serious on this engine.
Summarizing, I will say that the demands on hosting and the ability to work out the structure of the future portal in an extremely detailed way shift this engine from single developer students to the teams of portal developers.
3. Wordpress
The authors of the engine have tried to make it extremely convenient and understandable in the work of even a completely inexperienced user. An example of this is the installation of this CMS in five minutes. At the same time, as is usually the case, you have to sacrifice something, in this case I had to pay performance, this engine categorically did not want to run on my subdomain, immediately demanding about 5 megabytes of memory for me, if I'm not mistaken. And this is even without additional modules.
On this engine it is decent to make only blog-like sites.
In the spring, literally a week and a half or two, he threw up such a portrait: robotage.ru
pros
the system is easy to install even for an absolute beginner
modern stable system
easy to administer
a huge number of various modules and modifications, both domestic and foreign
sufficient support of domestic specialists
minuses
high resource intensity
site design will have to create their own, ready to manage skins will hardly be able to
there are raw modules for the engine, there is a problem of supporting the evolution of the modules, the version supported is always indicated on the site, that is, it is rather difficult to make a mistake
4. LiveStreet
This CMS was chosen by me for the blog “For Tea”. The reasons for this mass. But the most important thing is that this engine supports the community of users, while the community has the ability to actively influence the development of the site and develop independently.
pros
blog social engine
stability
good support of domestic specialists,
minuses
its blog-social orientation is also a minus, that is, this engine has pronounced specificity that is not suitable for everyone and not for any projects.
site design will have to create their own, ready-made skins are still quite small
it will be extremely difficult for one to raise something serious on this engine.
Summary:
website for the company - joomla
portal - drupal
personal blog - wordpress
collective blog - livestreet
PS The following material is likely to be devoted to a social network (vkontakte like) - elgg
Modern history of the blog "For Tea".
Once we were invited to another business center for the production of secret works. Nothing to do, let's go. He placed the brigade in its place, marked the scope of work, and he, as befits a brigadier, began to idle.
It was a pity to waste time just like that, without any sense, and I went to create the appearance of vigorous activity, that is, to cut out of paper the design of the future site.
At that moment I was very worried about the question on which platform to transfer the site “Over Tea” , so that it would be comfortable for me and my friends to write in it, and for this to cause as little rejection as possible.
About rejection, I spoke not by chance. The previous engine on which the site was implemented - joomla at the end of its stay caused only an emetic reflex. Crude platform with a bunch of piles. Working with joomla was sheer agony, that's a fact. In this, I wanted something more user friendly, sharpened for an ordinary user.
Began the search engine. For a couple of months I had to sort out: wordpress, drupal, and only after it I turned to livestreet.
Briefly about each of the engines:
1. Joomla
Mostly designed for classic sites, sites - business cards of companies.
')
pros
the ability to create a complex site structure,
seo oriented engine
good support of domestic specialists,
A large number of free and paid themes site design.
low resource consumption
minuses
it takes a lot of time to understand the structure of the engine
Enough raw engine, a lot has to be tightened up.
there are a lot of raw modules for the engine, most of them are made frankly “on the knee”. It is necessary to sweat to make the "assembly" work stably.
The main reason for the lack of development of the engine and modules is its free of charge, and free of charge in everything. It is worth considering that if you do not pay money for the engine itself, then you will compensate for this savings with your time spent reading the support forum. And I assure you that you will kill time essentially with big money!
2. Drupal
This engine is perfect for large portals, in fact, I position it for myself that way. I will give an example, taking the well-known site, habrahabr.ru , as a reference point; the guys were able to achieve similar functionality with regular modules: Shvarabvvr .
I think comments are superfluous.
pros
the possibility of creating a super complex (!) site structure,
seo oriented engine
sufficient support of domestic specialists,
minuses
high resource intensity
site design will have to create their own, ready to manage skins will hardly be able to
it takes a lot of time to understand the structure of the engine
there are a lot of raw modules for the engine, there is a problem of supporting the evolution of the modules, that is, if the module is suitable for version 1.0, then it is not at all the fact that it is also suitable for version 1.1.
it will be extremely difficult for one to raise something serious on this engine.
Summarizing, I will say that the demands on hosting and the ability to work out the structure of the future portal in an extremely detailed way shift this engine from single developer students to the teams of portal developers.
3. Wordpress
The authors of the engine have tried to make it extremely convenient and understandable in the work of even a completely inexperienced user. An example of this is the installation of this CMS in five minutes. At the same time, as is usually the case, you have to sacrifice something, in this case I had to pay performance, this engine categorically did not want to run on my subdomain, immediately demanding about 5 megabytes of memory for me, if I'm not mistaken. And this is even without additional modules.
On this engine it is decent to make only blog-like sites.
In the spring, literally a week and a half or two, he threw up such a portrait: robotage.ru
pros
the system is easy to install even for an absolute beginner
modern stable system
easy to administer
a huge number of various modules and modifications, both domestic and foreign
sufficient support of domestic specialists
minuses
high resource intensity
site design will have to create their own, ready to manage skins will hardly be able to
there are raw modules for the engine, there is a problem of supporting the evolution of the modules, the version supported is always indicated on the site, that is, it is rather difficult to make a mistake
4. LiveStreet
This CMS was chosen by me for the blog “For Tea”. The reasons for this mass. But the most important thing is that this engine supports the community of users, while the community has the ability to actively influence the development of the site and develop independently.
pros
blog social engine
stability
good support of domestic specialists,
minuses
its blog-social orientation is also a minus, that is, this engine has pronounced specificity that is not suitable for everyone and not for any projects.
site design will have to create their own, ready-made skins are still quite small
it will be extremely difficult for one to raise something serious on this engine.
Summary:
website for the company - joomla
portal - drupal
personal blog - wordpress
collective blog - livestreet
PS The following material is likely to be devoted to a social network (vkontakte like) - elgg
Source: https://habr.com/ru/post/67962/
All Articles