Drupal is a free, open-source content management system written in PHP that competes primarily with Joomla and Plone. The standard release of Drupal, known as Drupal core, contains basic features such as account and menu management, RSS feeds, page layout customization, and system administration.
N/A
HCL Digital Experience
Score 8.6 out of 10
N/A
HCL Digital Experience is based on the former IBM Web Content Manager and IBM WebSphere Portal products, acquired by HCL Technologies from IBM in late 2018. The product allows the user to create, manage and deliver engaging omnichannel digital experiences to audiences with responsive content, targeted offers, seamlessly integrated applications and consistent branding across channels (web, mobile, and hybrid mobile/web applications and more).
Well, I'm definitely biased, I've been working with Drupal for 12+ years, and I can say it's appropriate for any size/scale of a project, whether it's a small catalog website or a huge corporation. If I want to dial it down to a specific use case, Drupal is best what most customers/clients that have high-security standards, and need to have extensive editorial experience and control over their website's architecture. Due to its core design, Drupal can connect with each part of its own and any external third-party resources quite easily. For a less-suited scenario, I might say that if you don't have enough budget to get proper work done, sometimes just using WordPress with a pre-designed theme might sound better to you, but if you have the budget and the time, always go with Drupal
HCL DX does really well at managing and maintaining the site. It allows the business to basically maintain the site while IT spent time developing new and enhanced functions. The main issue I currently have with HCL DX is not directly with the product but it does play a role. It is difficult finding skilled resources to support HCL DX in my experience.
Content Types... these are amazing. Whereas a more simplistic CMS like Wordpress will basically allow you to make posts and build pages, Drupal 8 gives you the ability to define different types of content that behave differently, and are served up differently in different areas of the website.
Extensibility... it scales, ohhhh does it scale. They've really figured out server-side caching, and it makes all the difference. Once a page has been cached, it's available instantly to all users worldwide; and when coupled with AWS, global redundancy and localization mean that no matter where you're accessing the site, it always loads fast and crisp.
Workflows... you have the ability to define very specific roles and/or user-based editorial workflows, allowing for as many touchpoints and reviews between content creation and publication as you'll require.
With Version 8.5, IBM Web Content Manager introduced in place editing capabilities which allow authors to make content edits on sections of the page instead of going to the content itself. This feature allows authors to make changes in context of the page and preview changes within the actual look and feel of a live page.
Projects provide a collaborative atmosphere for the author community so that authors can interact and work as a team to manage inter-dependent content changes under one project and publish all changes at once, instead of working separately on individual content changes. This brings awareness across authors in an organization and easy knowledge share.
IBM Digital Data Connector is a cool feature that allows [users] to integrate external content sources onto the portal using IBM Web Content Manager presentation components. This allows UI/UX designers to present integrated external data in any manner they want, manage UI changes with an underlying approval process and leverage syndication to push changes live immediately.
IBM Web Content Manager offers a targeted content feature that allows business users to deliver personalized content to customers based on customer demographic information, browsing history and other transaction related information. Any rules created follow the publishing process thereby making it just a configurable item resulting in less turn around to turn on the feature on a website.
IBM Web Content Manager offers 'multi lingual solution' out of the box which allows content creation for almost all popular languages.
Syndication feature has improved a lot and it now provides a detailed views comprising of 'failed items', 'items that have syndicated successfully, 'items in queue'. Failed items view provides detailed and clear cut information of what resulted in failure helping IT to troubleshoot problems easily.
Security and new release notifications are a hassle as they happen too often
Allowing them to write PHP modules is a big advantage, but sometimes integrating them is a small challenge due to the version the developer is working on.
IBM Web Content Manager should provide some easily usable connectors through a GUI to connect to bring content from custom data sources including connecting to Salesforce and custom databases.
Should further optimize and enhance creation of rich and responsive content driven UIs on various digital channels.
Should further optimize and enhance content personalization features.
The time and money invested into this platform were too great to discontinue it at this point. I'm sure it will be in use for a while. We have also spent time training many employees how to use it. All of these things add up to quite an investment in the product. Lastly, it basically fulfills what we need our intranet site to do.
IBM products always moves forward to adapt to new requirements and technologies. I have used versions 6, 6.1, 7 and 8 of IBM WCM, and I know IBM is ready to revamp the tool based on emerging needs, and still provide the capabilities to migrate your old system to the newer versions.
It's a great CMS platform and there are a ton of plugins to add some serious functionality, but the security updates are too complex to implement and considering the complexity of the platform, security updates are a must. I don't want my site breached because they make it too difficult to keep it up to date.
Drupal itself does not tend to have bugs that cause sporadic outages. When deployed on a well-configured LAMP stack, deployment and maintenance problems are minimal, and in general no exotic tuning or configuration is required. For highest uptime, putting a caching proxy like Varnish in front of Drupal (or a CDN that supports dynamic applications).
Drupal page loads can be slow, as a great many database calls may be required to generate a page. It is highly recommended to use caching systems, both built-in and external to lessen such database loads and improve performance. I haven't had any problems with behind-the-scenes integrations with external systems.
As noted earlier, the support of the community can be rather variable, with some modules attracting more attraction and action in their issue queues, but overall, the development community for Drupal is second to none. It probably the single greatest aspect of being involved in this open-source project.
I was part of the team that conducted the training. Our training was fine, but we could have been better informed on Drupal before we started providing it. If we did not have answers to tough questions, we had more technical staff we could consult with. We did provide hands-on practice time for the learners, which I would always recommend. That is where the best learning occurred.
The on-line training was not as ideal as the face-to-face training. It was done remotely and only allowed for the trainers to present information to the learners and demonstrate the platform online. There was not a good way to allow for the learners to practice, ask questions and have them answered all in the same session.
Plan ahead as much you can. You really need to know how to build what you want with the modules available to you, or that you might need to code yourself, in order to make the best use of Drupal. I recommend you analyze the most technically difficult workflows and other aspects of your implementation, and try building some test versions of those first. Get feedback from stakeholders early and often, because you can easily find yourself in a situation where your implementation does 90% of what you want, but, due to something you didn't plan for, foresee, or know about, there's no feasible way to get past the last 10%
Drupal is community-backed making it more accessible and growing at a faster rate than Sitefinity which is a proprietary product built on .NET. Drupal is PHP-based using some but not all Symphony codebase. Updates for Drupal are frequent and so are feature adds.
Magento and Prestashop are E-commerce CMS platforms. They are used in a different scale of application than WCM.
Concerning Joomla, it's a useful CMS forsmaller website. Once again this is an other scale of application than WCM Liveray can compete WCM 7 concerning the : ¤ specific development ¤ security ¤ responsive
Drupal is well known to be scalable, although it requires solid knowledge of MySQL best practices, caching mechanisms, and other server-level best practices. I have never personally dealt with an especially large site, so I can speak well to the issues associated with Drupal scaling.
Drupal has allowed us to build up a library of code and base sites we can reuse to save time which has increased our efficiency and thus had a positive financial impact.
Drupal has allowed us to take on projects we otherwise would not have been able to, having a further impact.
Drupal has allowed us to build great solutions for our clients which give them an excellent ROI.