Overall Satisfaction with Drupal
Drupal is used to manage our primary website. It is managed by the Marketing department, without any involvement from the IT department. It serves as a quick, effective and relatively inexpensive way to manage over a thousand pages of content. In addition, the direction towards API first has significant savings, allowing us to build a solution that integrates many technologies into one interface for content editors.
- Content Management
- Document and Media Management
- SEO Management
- API Integration
- Easy to manage updates
- User management
- Can be extremely difficult to ramp up to production
- If built poorly, nearly impossible to fix without a full rebuild
- Drupal core updates can be a pain in the butt.
- Has helped us better guide users down predefined funnels
- Easily embeds resources that have a direct monetary amount attached to them
- The site can last for sometime without any significant architecture, extending the lifespan of the product
Joomla is terrible. I would never recommend Joomla over Drupal. Drupal's community is much more active and new product updates come out much more quickly.
WordPress is obviously great and a popular solution, but will struggle with sites that have too much content. WordPress is like a car, great for navigating small streets and getting somewhere nearby. Drupal is like an airplane, great for traveling long distances more efficiently.
SharePoint, another enterprise CMS, can be even more difficult to work with than Drupal. If you don't have a solid SharePoint person in house to help manage updates and content, you could find yourself stuck.