Drupal Previous Solutions
We have used a number of frameworks. However, due to its flexibility and community size, at the moment it is the preferred proof-of-concept platform.
View full review »Between the years 2006-2009, I had used SilverStripe as well as WordPress for CMS solutions.
However, SilverStripe had a much smaller community and didn't scale as well for the enterprise solutions.
WordPress was quick to theme, but a pain for add-ons.
View full review »I tried WordPress but it seems too limited for me.
View full review »We have used many different systems before, ranging from TYPO3, Umbraco, and even a custom CMS. The reasons to change to Drupal were:
- Ease of deployment
- One-sprint releases
- Security
- Out-of-the-box support for a good load-balanced solution
- No stale cache problems
I used WordPress. I switched because I learned how to code in HTML, CSS, JavaScript, and PHP. Drupal made it easier to customize a website by working directly with the API and the code.
View full review »I was a Java developer, developing mostly backend stuff. I switched when the company I was in at the time switched. Drupal was getting some traction in 2007, and it was time for us to try it for building websites.
View full review »I've used many solutions over the years. Some are easier, but they tend to be less scalable. Drupal is a great balance.
View full review »I worked in the past with different CMS solutions. Perhaps Vignette was the most relevant. I believe, at that time, it was the most complete and advanced CMS. However, It faced the same issues as many other solutions. It was heavy, lacking in flexibility, and slow to adopt new tech trends.
Drupal is the opposite, since it is not closed software and it does not rely on only one company.
View full review »MV
Mark Vincent Verallo
Web Developer / Programmer at a tech services company with 1-10 employees
We did not use any other solution before.
View full review »I started my career in Drupal. I didn't use any other solution before.
View full review »I worked with the Joomla!, but the product reached its limits. We switched to Drupal.
View full review »
Yes, several. Moved one site from flat files and homegrown systems, and others from Microsoft CMS 2002, all to enhance our ability to provide new and improved features and to decrease risk. Moved another from a customized (and therefore unmaintainable) version of Xoops. Moved others from hosted services to improve supportability.
View full review »
Yes. One site was built on a home-grown content management system. A second was built on Xoops. Others were built on Microsoft Content Management Server. We switched the first to lower risk and to enhance our ability to provide new functionality. We switched the second because we were unable to continue supporting our forked installation of Xoops. We switched from the others to improve productivity and enable us to provide new functionality.
View full review »
We have used WordPress before, but not for so long, so I can't really compare.
View full review »I’ve used WordPress as well. They are usually compared with each other. However, they are both good at solving different problems. You can achieve similar results, but they are better depending on your project.
WordPress is usually simpler and less expensive. It’s ideal for marketing websites, landing pages, blogs, and small e-commerce sites.
Drupal is better for larger and more enterprise-type sites. It can be expensive, but it provides more security and better scalability than WordPress.
View full review »We switched from TYPO3 to Drupal consulting, as Drupal offers better value to our customers.
View full review »AE
DrupalSo1d7c
Drupal Solutions Architect at a non-tech company
Previously, I have used a variety of solutions, including the custom ones. I switched solutions because Drupal provides all the features that I need.
View full review »I have used multiple PHP Frameworks and CMSs like CakePHP, Laravel, Joomla, Wordpress, Magento etc. Just like the difference between frameworks and CMSs, the differences among the products is mainly the purpose.
Drupal is not really better or worse than the rest. It is all about the context. The question is 'What do you want the product for?'.
Drupal is development oriented. It is a bit heavier to build and maintain than, let's say, Wordpress, but only in the context of websites with little to none specialized functionality.
So, the reason for me choosing Drupal over the rest is mainly the context. The projects that I took up needed specialized functionalities while having all functionalities offered by a CMS so, frameworks were out, CMSs were filtered out due to their, as you mention above, scalability, extensibility, orientation towards development. I might still choose e.g. WordPress for a blog-like site etc., but you get the point.
View full review »We did not have a previous solution.
View full review »Joomla, Wordpress. I typically use Wordpress for smaller websites, with less customization required and Drupal for larger websites that may need to expand in the future.
View full review »I was not using any other product previously. I started web development with Drupal, Version 7.
View full review »To build more powerful apps, we switched to Symfony 3.0.
View full review »I have some experience with Java Spring MVC Framework. Drupal allows us to work much faster but as a counter part, it is slower.
View full review »I didn’t use a different solution before using Drupal.
View full review »Before Drupal, I used static HTML web pages.
View full review »