Adobe Business Catalyst vs Drupal

• Probably one of the easiest e-commerce platforms to work in, it does take setup, but compared to a lot of other e-commerce solutions, this is probably the best one that I have seen that can be designed and implemented custom.
• Their template system works very well and allows you to create and re-use templates across Adobe Business Catalyst.
• Their pre-built modules are great, giving people a great way to use common web elements without having to use a plug-in or find some solution, it is simply built in and generally works exactly as you would expect.
• Adobe Business Catalyst is more of an all-around solution, providing elements that most smaller companies would have a hard time figuring out, since it includes the ability to build websites, send and track e-mails, analytics. It really is a powerful tool that would typically require a fair amount of coding knowledge and expertise but with the system already built, it can be easily modified and edited by those with limited or no coding knowledge at all.

Read full review

• You don't need to be a developer to use Drupal. You just need to learn its functions.
• We were able to train people with various non-computer backgrounds to use Drupal. It can be learned by a range of people who are not "technical".
• Drupal sites can include APIs, webforms, slideshows, parent and child pages, and more.

Read full review

• Multi Client Management: The dashboard for managing multiple clients as a reseller is a little difficult to get to. There is also no very easy way for me to manage multiple clients at once. I have to log into and out of individual client accounts to do billing or management.
• Lack of Server support: There are certain server protocols and languages that are not supported using BC. For example I cannot build a custom php database and upload to BC. I am required to use their tools.

Read full review

• VERY steep learning curve for both developers and designers, half jokingly referred to as a learning cliff. If you're going to build something, you need to do a lot of planning and research to ensure that you're following best practices.
• Difficult to set up a system making it easy for non-technical end users to enter complexly styled content. If the content managers are responsible for layout of individual pieces of content, there is an additional steep learning curve. Alternatively, a reasonable amount of training is required to ensure that content managers know how to use the system.
• Written documentation for many modules, including some of the most commonly used ones, is often piss-poor or completely lacking. Some UI aspects can seem completely arcane as a result, adding to the difficulties of learning how to use the system.

Read full review

• Complete reporting connecting dollars spent on marketing to dollars earned as revenue
• Faster turn-around on ideas into market-ready content
• Better service to clients through greater usability in account management

Read full review

• I have had a very negative experience with Drupal. In fact, my client and I decided to switch the site to Joomla because we couldn't get the PDF module to work on the Drupal site. It was a big waste of time and it was unfortunate that I couldn't get the power of Drupal to work for my client because of a bad module that didn't have a good doppelganger. Because their site had been built in Drupal previously, we ended up painting ourselves into a corner, wasting months of time trying to contact developers and get things worked out.
• Since Drupal is inefficient as far as integrating the admin with the frontend of the site in the same page, it makes the work go much slower that with other CMS.
• As the module community for Drupal is so poor, the customer service I end up providing to my client looks poor. If I can't get an answer from a developer of a critical module, it makes me look bad to my client. Be very aware of this issue when investigating Drupal.

Read full review