Much has been said and written both about Drupal and Joomla. Their differences and superiority have made the subject of many heated discussions. This piece of writing is not a persistent opinion imposed but a text for those who decided to change Drupal for Joomla, no matter what their reasons are.
If you are still on the fence about the migration and wonder what the difference between them is, be sure to find some clues that would probably help you arrive at a decision in this article.
The two platforms under consideration seem to do the same. The truth is that they do offer almost the same, as you use the service for one purpose, to build your website and make it look and function as good as possible.
Drupal is the heavyweight of CMS comradeship. As a true titan, it is capable of upholding heavy monster websites having 2000+ pages and tens of thousands of articles. It does not forget to help you with the data mass and mess by providing all the necessary options. The sad thing is, Drupal has painful updates. The inconvenience is that there is a need to update each of your modules separately. One more upside is the quality of required skills. The CMS has a steeper learning curve if compared to Joomla. That is why Drupal is perfect for a developer but not for a not-so-skilled user.
Joomla, as it has been already mentioned, is more user-friendly. It may be compared to a strong sprinter, able to run fast while carrying some weight. He runs on a track that might have obstacles and curves, but the course is well-defined. Just so does Joomla overcome the bads itself and make your content management extremely convenient. It also offers multiple extensions that will modify your website from the inside. As to coding skills, you’d better have some of them, and ‘some’ does not mean ‘super’.
To cut it short, the final choice between the two CMSs boils down to the load of your website and complexity of its content management. If you decide to go for migration and do not want to spend hours or days copy-pasting, consider doing this via CMS2CMS Automated Drupal to Joomla Migration extension. It will save your time and money. Surprised why money? Hiring a programmer would cost more. The presentation below will tell you more about the automated migration and explain all the whys and hows of it.
An article that started with promise but eventually follows all the others of this type falling into the regurgitation of samo-samo misconceptions and myths.
Do you think when eBay looked at Drupal and Joomla to provide their back office intranet, decided that they would go for the on CMS that couldn’t do the heavy lifting they would need?
It’s time you SEO foragers to start to sing to a different tune. You treat these CMSs like most human’s treat the people around them…they take a bit of time to get to know them, they then compartmentalise them for personality type and whether or not they like being around them, then and forever more keep them in their internal compartment, no matter how much those people change in front of them.
You guys need to realise that the CMSs that you are writing about with these “WordPress is more user friendly”, “Drupal is harder to learn”, “Drupal is for enterprise” nonsense, are not the CMSs that are in front of you.
Take security for example, the widely held belief is that Drupal is more secure but with a little research at an independent security analyst:
WordPress: http://www.cvedetails.com/vendor/2337/Wordpress.html
Drupal: http://www.cvedetails.com/vendor/1367/Drupal.html
Joomla: http://www.cvedetails.com/vendor/3496/Joomla.html
You can see from the graphs that it is Joomla that is becoming the most secure platform as the “number of exploits is in full decline, Whereas for WordPress and Drupal they are on the rise.
The reason for this could be put at the feet of the Joomla framework. With Joomla providing such an excellent platform for developers to use, safely, the extension developers of today are able to build higher quality, more secure products. It could be argued that Drupal allows for much wider development, allowing for more exploits to be created. This could certainly be said for WordPress. It’s difficult to accurately say what the reason is, especially without further research, so I don’t say the above with any conviction, it’s just a hunch. It is however a great example in that if I say it enough times and no-one bothers to check its validity, it could become another of those regurgitated myths that lazy writers spread…
My request to you Lexy, whatever CMS camp you’re in and I imagine you’re not really in any, please look again at the people around you…do you really know them like you think you do?
Go back, take some more time to find out if they have changed since you first met them (I can assure you they have, no one stays the same)…and if so change your view on who they are for yourself…then apply this same experiment to the commonly held misconceptions about CMS, you might just be surprised. Don’t become a lazy writer Lexy.
By the way it is human nature to do what I describe above, everyone does it, I’m not picking you out specifically…just making a point.