What do Joomla and Drupal have in common?
For example, Joomla has linux.com, and Drupal has ubuntu.com
Both sites have a huge load. Both have a high level of services. Both work fast.
So what’s the difference? Briefly and clearly, without any chorus or ponzi scheme:
There is no difference in potential capabilities. On the basis of both platforms you can make as powerful a site as you want.
However, each system has a number of advantages.
Drupal is mostly a web 2.0 platform, which from the moment of installation can provide interaction with site visitors through blogging chips, comments, etc. If you are a beginner and the primary purpose of the site is to interact with the community, then the choice is definitely Drupal.
I would compare building a site on Drupal with building a spacious house with transparent walls, everyone can look in and wave goodbye to the owner of the house.
Joomla is a classic. After installing it, you can launch a large-scale portal with many useful services in three clicks. However, that would deploy a community, will have to work with the installation / configuration / customization of several components. If you are a beginner and you need a portal or organization site with a directory and so on – you can choose Joomla.
A site on Joomla is a mansion made of glass and concrete, solid and reliable (if the architect took care of security (smiley)).
1) For beginners I would recommend Jumla. Everything there is more straightforward, logical and understandable. It’s never too late to switch from Joomla to Drupal and back.
2) If you’re just beginning to master the CMS, do not put a lot of different engines at once. Choose one and try to make it your first site. Do not stagger. Do not install modules / components that are not critical to you – it increases the load on the server, making the site more vulnerable and more difficult to service. Updating components and switching from an old version to a newer one – that’s a separate song, and the less third-party components you use, the easier your life will be.
3) Do not modify the engine core unnecessarily. If you migrate to a new version, you will have to do everything all over again. This is especially true for proprietary CMS like Bitrix, where developers are interested in updates and new versions promise to fix critical bugs, improved security and improved services.